views:

1208

answers:

7

I have been using Visual Studio 2008 quite long but lately I am getting this message when I am developing an application in C#:

Common language runtime detected an invalid program

This happens when I try to enter to the properties of a component (text masked box properties, tool box property etc..). But it really became a problem when I tried to launch an other solution that I downloaded from the Developer's 5 star program of Microsoft and it didn't allowed me to launch at all and just got the same problem...

I looked for the answer at google but just got some clues about people having the same vague error but in different situations like in ASP.NET

I would appreciate any help with this issue... :( I do not want to reinstall VS, that will be my last resource...

Thanks.

+1  A: 

Can you reproduce the problem in a new solution without referencing any extra assemblies? If so, I think reinstalling would be your best bet. Sorry!

GraemeF
I tried the following:1) Reinstalled the 3.5 .Net Framework // Didn't work2) Reinstalled the Visual Studio 2008 Standard edition // Didn't work:( ... still having the same ugly message: "Common Language Runtime detected an invalid program" the problem is that there is no extra info that could give me a clue about the problem... Thx for the time
Jimmy
btw, I am getting this on Vista 32 bits SP 2 in a Core Quad... I do not know if this could help
Jimmy
A: 

I never figured out what the problem was... so turning around... I installed a virtual machine with Windows XP on it, there I only have Visual Studio and Netbeans.. Damm! it is really fast :)

Thx for the time

Jimmy
A: 

A colleague of mine had a problem where his toolbox ended up corrupt. Try opening the toolbox, right-click, and choose 'Reset Toolbox'. You never know.

Steve Cooper
A: 

I never did find a solution for this issue online. But what fixed it for me, was to use the 'Clean Solution' option in Visual Studio.

Seems VS had gotten a little 'dirty', somehow.

Daniel
A: 

Clean Solution worked for me too. I'd definitely try this before going through Microsoft's troubleshooting guide.

Alan
+1  A: 

Thx guys, the "Clean Solution" did it for me!!! Cheers.

A: 

Clean solution does not work for me :(

cemregoksu