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

debug problem

P: n/a
I have had the following happen to me for the third time in several months
on my laptop but never on my desktop computer while working with a VB.et
project in Visual Studio 2005.

I was working with a Windows project and debugging fine. I only made a few
minutes worth of changes (and did nothing to the VS setup as far as I know).
Then all of a sudden, when I clicked on Debug | Start Debugging, the project
build succeeded, the startup window of the application appeared and
disappeared in a flash. A second try produced the same thing. I checked the
output folders (ProjectName/bin and ProjectName/obj/Release) and found the
application exe there and double-clicked on it. The hour glass appeared and
disappeared a couple of times, but nothing else.

Then I got an idea and moved the exe to another folder on the computer. The
exe ran fine from there and exhibited the changes I had made to it before I
tried to run it in debug mode. This is very strange in that it appears that
from within these folders, the application exe can not be run. Other exes
like notepad.exe will run fine from there.

Finally, this is the situation for all projects including new ones I make.

Turning off the computer and turning it back on does not solve the
problem--unless I wait quite a few hours. In general, the problem somehow
mysteriously fixes itself within 24 hours.

Any suggestions would be appreciated.

Jan 20 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
hmmm...

Have you tried to install Visual Studio 2005 Service Pack 1:
http://msdn2.microsoft.com/en-us/vstudio/aa718695.aspx

"William LaMartin" wrote:
I have had the following happen to me for the third time in several months
on my laptop but never on my desktop computer while working with a VB.et
project in Visual Studio 2005.

I was working with a Windows project and debugging fine. I only made a few
minutes worth of changes (and did nothing to the VS setup as far as I know).
Then all of a sudden, when I clicked on Debug | Start Debugging, the project
build succeeded, the startup window of the application appeared and
disappeared in a flash. A second try produced the same thing. I checked the
output folders (ProjectName/bin and ProjectName/obj/Release) and found the
application exe there and double-clicked on it. The hour glass appeared and
disappeared a couple of times, but nothing else.

Then I got an idea and moved the exe to another folder on the computer. The
exe ran fine from there and exhibited the changes I had made to it before I
tried to run it in debug mode. This is very strange in that it appears that
from within these folders, the application exe can not be run. Other exes
like notepad.exe will run fine from there.

Finally, this is the situation for all projects including new ones I make.

Turning off the computer and turning it back on does not solve the
problem--unless I wait quite a few hours. In general, the problem somehow
mysteriously fixes itself within 24 hours.

Any suggestions would be appreciated.

Jan 20 '07 #2

P: n/a
I have VS 2005 on two computers and have installed Service Pack 1 Beta
sometime back on both so as to be able to work with the SQL compact
databases (formerly called SQL Mobile).

I do not have this problem on my desktop computer--only on the laptop.

Not being able to run the executable created in the project folder but being
able to run it from anywhere else on the computer is one of the strangest
things I have ever run into. And how it seems to self correct within 24
hours is another mystery.
"Joshua Morgan, Developer" <Jo*******************@discussions.microsoft.com >
wrote in message news:09**********************************@microsof t.com...
hmmm...

Have you tried to install Visual Studio 2005 Service Pack 1:
http://msdn2.microsoft.com/en-us/vstudio/aa718695.aspx

"William LaMartin" wrote:
>I have had the following happen to me for the third time in several
months
on my laptop but never on my desktop computer while working with a VB.et
project in Visual Studio 2005.

I was working with a Windows project and debugging fine. I only made a
few
minutes worth of changes (and did nothing to the VS setup as far as I
know).
Then all of a sudden, when I clicked on Debug | Start Debugging, the
project
build succeeded, the startup window of the application appeared and
disappeared in a flash. A second try produced the same thing. I checked
the
output folders (ProjectName/bin and ProjectName/obj/Release) and found
the
application exe there and double-clicked on it. The hour glass appeared
and
disappeared a couple of times, but nothing else.

Then I got an idea and moved the exe to another folder on the computer.
The
exe ran fine from there and exhibited the changes I had made to it
before I
tried to run it in debug mode. This is very strange in that it appears
that
from within these folders, the application exe can not be run. Other exes
like notepad.exe will run fine from there.

Finally, this is the situation for all projects including new ones I
make.

Turning off the computer and turning it back on does not solve the
problem--unless I wait quite a few hours. In general, the problem
somehow
mysteriously fixes itself within 24 hours.

Any suggestions would be appreciated.


Jan 20 '07 #3

P: n/a

"William LaMartin" <la******@tampabay.rr.comwrote in message
news:uz**************@TK2MSFTNGP02.phx.gbl...
>I have VS 2005 on two computers and have installed Service Pack 1 Beta
sometime back on both so as to be able to work with the SQL compact
databases (formerly called SQL Mobile).

I do not have this problem on my desktop computer--only on the laptop.

Not being able to run the executable created in the project folder but
being able to run it from anywhere else on the computer is one of the
strangest things I have ever run into. And how it seems to self correct
within 24 hours is another mystery.

A memory fluke. Try a memory scan but that might not catch it either.

Richard

Feb 20 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.