#visual studio 2005

[getint0pc-blog]

Visual Studio 2005 Free Download

Visual Studio 2005 Free Download Professional Edition with MSDN. Develop code in 2005 version of VB, C#, C++ and J#. All extension and tools fully included. Get Into PC, getintopc, getintopc safe, getintopc review (more…)

View On WordPress

[ntcoder]

[Debugging] Application crash after migration from Visual Studio 2005 to 2008

Had a customer whose application was crashing after migration from Visual Studio 2005 to Visual Studio 2008. He had the crash dumps as well. The crash call stack had some CRT string format functions like vsprintf. This gave to us a fair inkling that…

View Post

[lessonslearnedfordevs]

Error with Visual Studio 2005 and Jenkins

While trying to build C++ code from Jenkins slave node using Visual Studio 2005, I kept getting this error:

Fatal Error C1902: Program database manager mismatch; please check your installation.

Googling that error code, Microsoft will tell you to check the version of your pdb files. In this case, the cause of this error does not actually relate your pdb files. This error is the result of a known issue of trying to build code as the Local System User (which is what Jenkins is running as). Microsoft offers a hotfix solution for the issue here:

http://support.microsoft.com/kb/920770

[mithunz-blog]

White Screen of Darn – WSoD

If you have used the Windows Form Designer in Visual Studio 2005 enough, changes are you may occasionally seen a big frightening white error screen with the following title in red, and a big X near it.

When the Visual Studio Designer views forms, it runs the constructor of your code. However, the code may behave in an unexpected way when run out of the application context. This may result in some exceptions thrown. 

Its Very difficult to solve the issue by only reviewing the code. However, an eassy solution exists. By taking the following steps you may find the exact location of the code causing the exception, thus you can make nessasary changes.

Tools ->  Attach to Process 

Attach the Visual studio Process(devenv.exe)

Close the problematic form, and reopen it.

This should result in an exception caught inside your code in the second instance of Visual Studio!

  Thanks 

Mithun M

Software Developer