I am not that lucky. I have to reboot to continue. Today I experienced something really interesting. VS was giving me a parser error about a COM wrapper class that I removed from the project weeks ago. I could not imagine how it would remember this COM object that I was no longer using no less raise an error about it. However, when I looked into my /bin directory a found the dll of the wrapper class. I deleted the dll because I no longer need it. I will let you know if I get the error again.

Keep in touch,
Neil

>>Sometimes, in the middle of an editing session of my code, vs.net starts to throw a parser error and indicates that access to a module is denied. If a re-boot the error goes away. Today I found that if I delete the temp files that vs.net creates for my project, the error also disapears. Does anyone know what is going on?
>>
>
>I suspect this is where the product (VS.NET) shows that it is, after all, still version 1.x. I've run into weird behaviors with the IDE as well. In my case just closing VS.NET and launching it again takes care of the problem.