Visual-studio – My visual studio 2005 solution sometimes does not open the entire projects

visual-studio-2005

My visual studio 2005 solution sometimes does not open the entire projects. To clarify what I mean by the “Entire projects”, my application is consisting of different layers such as DAO, Domain, Service, Utility and finally Web.App that contains all of my .aspx, .asxc and code behind files. Each layer consists of large amount of .CS and .VB classes. So, when I open the solution file (.sln), it only opens the Web.App project without opening the others.

Has anybody encountered this kind of issue in VS2005 and if you have had what you did to fix it, please let me know. So, basically when I open the project .sln, it only shows the Web.App project not the other projects. This does not happen all the time, but happens once in a while.

Is it because Visual Studio 2005 was not installed correctly or missing some updates? Any ideas or suggestions are highly appreciated. Thank you so much

Best Answer

Have you tried creating a new solution and adding all the relevant projects to see if perhaps your current .sln is corrupt?

Signing Third-Party Assemblies

The basic principle to sign a thirp-party is to

Disassemble the assembly using ildasm.exe and save the intermediate language (IL):
```
ildasm /all /out=thirdPartyLib.il thirdPartyLib.dll 
```

Rebuild and sign the assembly:

ilasm /dll /key=myKey.snk thirdPartyLib.il

Fixing Additional References

The above steps work fine unless your third-party assembly (A.dll) references another library (B.dll) which also has to be signed. You can disassemble, rebuild and sign both A.dll and B.dll using the commands above, but at runtime, loading of B.dll will fail because A.dll was originally built with a reference to the unsigned version of B.dll.

The fix to this issue is to patch the IL file generated in step 1 above. You will need to add the public key token of B.dll to the reference. You get this token by calling

sn -Tp B.dll

which will give you the following output:

Microsoft (R) .NET Framework Strong Name Utility  Version 4.0.30319.33440
Copyright (c) Microsoft Corporation.  All rights reserved.

Public key (hash algorithm: sha1):
002400000480000094000000060200000024000052534131000400000100010093d86f6656eed3
b62780466e6ba30fd15d69a3918e4bbd75d3e9ca8baa5641955c86251ce1e5a83857c7f49288eb
4a0093b20aa9c7faae5184770108d9515905ddd82222514921fa81fff2ea565ae0e98cf66d3758
cb8b22c8efd729821518a76427b7ca1c979caa2d78404da3d44592badc194d05bfdd29b9b8120c
78effe92

Public key token is a8a7ed7203d87bc9

The last line contains the public key token. You then have to search the IL of A.dll for the reference to B.dll and add the token as follows:

.assembly extern /*23000003*/ MyAssemblyName
{
  .publickeytoken = (A8 A7 ED 72 03 D8 7B C9 )                         
  .ver 10:0:0:0
}

Best Answer

Related Solutions

Visual-studio – Visual Studio setup problem – ‘A problem has been encountered while loading the setup components. Canceling setup.’

C# – How to fix “Referenced assembly does not have a strong name” error

Signing Third-Party Assemblies

Fixing Additional References

Related Topic