By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,948 Members | 838 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,948 IT Pros & Developers. It's quick & easy.

Visual Studio .NET 2003 Bug, New Windows Application

P: n/a
Whenever I create a new windows application from Visual Studio .NET
2003 in either C# or VB.NET upon running the compiled code (debugging
or not) I receive a System.NullReferenceException immediately after the
application.run command. I'm not changing any of the code created by
the IDE, I'm simply building the default code.

File -> New Project -> Windows Application
Debug

Changing the color of the form averts the problem, but the same
exception occurs once the form loses and regains focus.

This doesn't happen in Visual Studio 2005 but I don't want to use .NET
2.0. I also have the Feb 2006 DirectX SDK installed and had installed
Visual Studio 2003 after Visual Studio 2005. I saw a post from several
years ago with the same problem and no solution was posted. Is there
some known conflict or bug?

Thanks in advance.

Mar 15 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
> Whenever I create a new windows application from Visual Studio .NET
2003 in either C# or VB.NET upon running the compiled code (debugging
or not) I receive a System.NullReferenceException immediately after the
application.run command.


Was the problem NullReferenceException from an unknown module? If not,
ignore this post. I had the NullReferenceException unknown module problem
over a year ago, and it appeared to me to be a bug in the ide, not in the
app. I could never create the problem by running the app standalone (outside
the ide), and I could create it intermittently under the ide. I suggest you
try this too to see if the ide is to blame or not.

I haven't had the problem for over a year now, and I attributed that to
installing FW SP 1.1. Our configs are different. I have xp 5.1 with all
latest SPs and .net 2003 FW SP 1.1. I presume you have 2003 and 2005 on
installed on the same machine (I dont). I am running a Dell Dimension 4550
with Intel Pentium 4 at 2.4 GHz. Yours?

Sorry, no answers, just trying to pin down symptoms.
Mar 15 '06 #2

P: n/a
follow up:
uninstalling VS 2005, VS 2003, and .NET 1.1 SDK, and reinstalling did
NOT solve problem. I can't write any programs with this package and it
used to work fine. I'm completely stuck, and with a deadline.PLEASE
help.

Mar 16 '06 #3

P: n/a
follow up:
uninstalling VS 2005, VS 2003, and .NET 1.1 SDK, and reinstalling did
NOT solve problem. I can't write any programs with this package and it
used to work fine. I'm completely stuck, and with a deadline.PLEASE
help.

Mar 16 '06 #4

P: n/a
follow up:
uninstalling VS 2005, VS 2003, and .NET 1.1 SDK, and reinstalling did
NOT solve problem. I can't write any programs with this package and it
used to work fine. I'm completely stuck, and with a deadline.PLEASE
help.

Mar 16 '06 #5

P: n/a
follow up:
uninstalling VS 2005, VS 2003, and .NET 1.1 SDK, and reinstalling did
NOT solve problem. I can't write any programs with this package and it
used to work fine. I'm completely stuck, and with a deadline.PLEASE
help.

Mar 16 '06 #6

P: n/a
FIXED. Sort of....what a weird bug! First off I don't know why my
last reply got posted 4 times. I only hit Post once. Blame Google
Groups I guess.

Secondly, apparently there's a VS 2003 (my academic version anyways)
limitation on nested folders. The projects were created in the default
C:\Documents and Settings\Administrator\My Documents\Visual Studio
Projects\Project_Name folder. Moving the Visual Studio Projects folder
to the root c:\ drive solved the problem entirely. Go figure. Too bad
I figured it out after I spent a good 5 hours manually removing any
shred of .NET from my computer and then reinstalling all of it. The
reinstall did nothing. Any one else ever experience this issue before?

Mar 16 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.