issue with: "common language runtime detected an invalid program"

[Richy]

I'm getting the message:

common language runtime detected an invalid program

all too frequently in VB 2008 Express. I use edit-and-continue a lot
and it usually happens after making a minor change, even if I undo the
change. It didn't used to happen, it is getting more and more frequent
and it is really frustrating now.

Does anybody know how to stop this from happening?

Richy

 

[Lloyd Sheen]

I'm getting the message:

common language runtime detected an invalid program

all too frequently in VB 2008 Express. I use edit-and-continue a lot
and it usually happens after making a minor change, even if I undo the
change. It didn't used to happen, it is getting more and more frequent
and it is really frustrating now.

Does anybody know how to stop this from happening?

Richy

Are you using Linq? It is not only VS 2008 Express (I use Pro) and have
same problem. It has been reported to Connect and they say they can't
reproduce it, so who knows what will happen. On occasion VS 2005 used
to fail on an edit and continue but 2008 does this way too much.

Another thing I have noticed may be the time factor. If you take a
while to make the change it seems to fail more than if you don't.

A work around if you can is to make sure that the class that you are
making a change to has no instantiated objects. That seems to fail less
times.

LS

 

[Richy]

Yeah, I have been using Linq quite a bit these last few months. I get
the same issue at work with VB 2008 Express where I believe I am NOT
using Linq though (I will have to confirm this when I go back to work
on Tuesday). With the work I am doing at home, I am using a lot of
collections of classes and I thought Linq would be the fastest way to
extract what I need from those collections.

I will keep an eye on the time factor and see if that has any bearing
on what I am doing.

Thanks,

Richy