"Exception" no longer recognized

  • Thread starter Thread starter Gary
  • Start date Start date
G

Gary

the last time I did a build, Exception was no longer recognized in any of my
modules. To make it recognized, I need to explicitly type system.exception.
The only thing I have changed is that I applied a Crystal Reports Service
pack 1. I have never had to have Import statements for system.exception.

What could have stopped recognition of Exception?
Thanks,
Gary
 
Hi Gary,

That's a strange one. You might want to check in Visual Studio's project
settings (Common Properties > Imports) whether the System namespace is still
included. I can't imagine that much would work without it.
 
Hi Gary,

Thanks for posting. If we create a new VB.Net project, do we have the
problem? This may help to isolate the problem.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
No it works fine on a new project. It just doesn't recognize "Exception" in
my existing Project.

My exsiting poject contains a class, that I wrote, called "Exceptions" (with
an s) but that shouldn't be a problem.

Gary
 
Hi Gary,

Thanks for your followup. As for the "Exceptions" class you've defined ,I
think you can try comment it or isolate it from the project to see whether
the problem will go away. Also, I think you can create a clean project an
move the files into that project, since it is likely that some
configuration or setting infos of the project be corrupted.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
 
Back
Top