NullReferenceException after SP1(?)

  • Thread starter Thread starter Dan
  • Start date Start date
D

Dan

I'm experiencing a very strange problem with vsnet2003 and the latest dotnet
1.1 sp1. I have a C# winforms project using Crystal Reports for .NET and
accessing a database which worked fine before upgrading dotnet 1.1 to sp1;
now when I launch its debug version with F5 from the IDE I *immediately* get
the error:

An unhandled exception of type 'System.NullReferenceException' occurred in
Unknown Module.
Additional information: Object reference not set to an instance of an
object.

if I click the Continue button the application starts up and works normally
(or at least it seems so). If I launch the release version with F5 from the
IDE no such error occurs. If I launch the debug version from windows without
using the IDE no exception is thrown. All this happens for this project only
(maybe it is related to Crystal reports? but other projects using it do not
show any problem) and has never happened before I installed the SP1 for
dotNet 1.1, this is why I was thinking that the problem might be somehow
related to this upgrade.

Does anybody have similar problems or any hint about solving them?
Thanks guys!
 
Dan,

All three VB developers at my company have this problem. The only fix we
have found is to reinstall the 1.1 framework without SP1. Unfortunately, our
corporate IS department forces Windows updates (which inlcude SP1) upon us,
so we are forced to periodically reinstall 1.1. This works but is, of
course, very inconvenient. We could sure use a more practical fix. Anybody?

Christopher N.
 
Back
Top