View Complete Post
I have connection strings info in web.config. I thought that if this were the case, machine.config would be ignored. But, everytime the connection string in web.con is different than the connection string in maching.con, I get error......
The connection name 'aspnetdbConnectionString' was not found in the applications configuration or the connection string is empty.Is there something I can check or change to get the app to ignore the machine.config when web.config connection string is listed.
It accesses a database using a connection string in machine.config.
On my Windows XP Pro 32bit (SP3) machine, it works correctly.
On my new Windows 7 Pro 64bit machine, it throws "object not set to an instance of an object" when it gets to the line where it's trying use the connection string.
This is the 'object' which is not set in Windows 7:
The machine.config has the same connection string set up on both machines.
A .Net 2 website transferred to the Windows 7 machine has no problem accessing the same connection string.
Does anyone know what's going on here? Many thanks.
One of my NUnit tests has to read in some values from config files. In my main application this process works perfectly well, however when I run the unit test, the code that reads in the values from the config files doesnt read anything in. Ive tried putting app.config in my unit test project (I even tried web.config) but nothing seems to work. Are there any special steps involved when reading from config files in an nunit test ?
Ive created an NUnit test project in my solution and have added 3 tests. They all fail with the same error
SetUp : System.TypeInitializationException : The type initializer for 'Systems.Utils.ConstantHelpers' threw an exception.
----> System.NullReferenceException : Object reference not set to an instance of an object.
heres the test method
public void CreateDataContext_ConnectionString_ReturnsDataCon
Im trying to create a Web Deployment Project, the built in setup and deployment is very good in Visual Studio, i need to able to add an additional step in the setup to change the connection string in the Web config file. Ive seen a lot of articles on how to do this and in particular this http://weblogs.asp.net/scottgu/archive/2007/06/15/tip-trick-creating-packaged-asp-net-setup-programs-with-vs-2005.aspx#7162670 I am however stuck on the final part of this tutorial, im using the code Scott provided but have two errors, heres part of my code where the errors are
void ConfigureDatabase(string targetSite, string targetVDir, string connectionString)
// Retrieve "Friendly Site Name" from IIS for TargetSite
DirectoryEntry entry = new DirectoryEntry("IIS://LocalHost/" + targetSit
I have a web application that is actually installed as a component of a third party site. In some configurations, I need to remove certain connection strings and re-add them. I'm replacing this web.config section with a xml file that includes the following:
<connectionStrings> <remove name="MyOverridenConnection"/> <add connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=MyDb;Data Source=MyServer" name="MyOverridenConnection" providerName="System.Data.SqlClient"/> </connectionStrings>
For some reason the remove tag is left out during the substitution and I end up with the following in the installed config:
<connectionStrings> <add connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=MyDb;Data Source=MyServer" name="MyOverridenConnection" providerName="System.Data.SqlClient"/> </connectionStrings>
Is there any way to issue removes in replaced sec
Vikram Dendi looks at how machine translation is poised to change the world and why it is so important to deliver information in multiple languages.
MSDN Magazine January 2009
In a settlement agreement reached in January 2001 to resolve a dispute over the Microsoft distribution of its Java implementation, Sun Microsystems and Microsoft agreed to limit the duration of the time Microsoft would use Sun's source code and compatibility test suites to support the MicrosoftÃÂ® Java Virtual Machine (MSJVM).
MSDN Magazine October 2004
The Express Editions of Visual Basic and SQL Server 2005 have lots of the features of the full-sized versions, but with a lot less of the overhead. Professional developer features such as full IntelliSense support, local debugger, Add Web Reference, and the improved Visual Data Tools will all be available in the Express products, so you don't have to leave your favorite features behind. In this article the author introduces you to these express editions and builds a sample app to get you started.
Brian A. Randell
MSDN Magazine September 2004
Even though you've been using ASP. NET for a while, how much do you really know about ASP. NET configuration files? While you've probably touched the Web. config file from time to time, there are some nuances involved in configuring ASP.
Efficient testing can require many different machine and server configurations but the effort needed to manage these test environments can take a toll. Microsoft Virtual Server 2005 simplifies the provisioning and management of testing environments. This article demonstrates how the extensive Virtual Server COM API can be used to create an automated application testing environment to make your testing chores a whole lot easier.
MSDN Magazine August 2004
Developers who use the Microsoft virtual machine (VM) will need to transition away from its use by January 2004. To comply with a court settlement with Sun Microsystems, Microsoft will not be able to update the Microsoft VM, even to repair critical security vulnerabilities.
MSDN Magazine September 2003