First step: check if the assembly is really in the bin folder. It’s there but you still get the error? There might be few reasons for the framework to fail when trying to load your assembly. To find the real one you can use nice tool from MS, called “ Fuslogvw.exe ” which is assembly binding log viewer you can use for your .NET application (it’s auto installed with VS). After opening this tool, start your application and wait for the exception to be thrown. go back to the tool, hit the refresh to...
Recently I encountered an exception while trying to connect to SQL Server named instance. We have a main server with SQL Server 2005 installed on as the default instance and another SQL Server 2008 installed as a named instance. The connection string I used was: " Data Source=ServerName\InstanceName,1433;network library=dbmssocn;Initial Catalog=MyDataBaseName;Integrated security=SSPI " We are using TCP/IP as the underlying connection method in order to connect to SQL Server. This can be...