Debugging Problems on Windows Vista

[TheDude5B]

Hi,

I have just installed Visual Studio 2005 on my windows Vista machine,
and everything seems to work well after installing the service pack
and then the vista upgrades.

However, when I try to debug an application, the debugger starts,
launches the project in explorer, but then stops debugging. It pops up
with an error saying:

-----
the following module was built either with optimizations enabled or
without debug information:

C:\Users\myname\AppData\Local\Temp\Temporary ASP.NET Files\root
\assembly....\projectname

To debug this module, change its project build configuration to Debug
Mode.
To suppress this message, disable the "Warn if no user code on launch"
debugger option.
-----

The project build succeeds but I am just not able to debug. Is this a
windows Vista problem?

Please help.

 

[Mark Rae [MVP]]

The project build succeeds but I am just not able to debug. Is this a
windows Vista problem?

No, it just means that you're trying to debug in Release mode... Switch the
probject into Debug mode, hit Rebuild and then F5...

 

[Guest]

Aside from what Mark mentions, I have run into this several times. As the
error dialog indicates, you can override this in Options. However, I
remembere always being able to jump right over this and continue debugging
successfully.
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com

 

[TheDude5B]

No, it just means that you're trying to debug in Release mode... Switch the
probject into Debug mode, hit Rebuild and then F5...

What do you mean by this? Do you mean set the <compilation
debug="true"> in the web.config file or something else?
I have <compilation debug="true"> in the web.config, but the error
still appears. I have had a look around to see if there are any other
settings which i can change, but still the same problem.

 

[TheDude5B]

Found the problem. It is down to the Vista User security settings. If
I run Vista "As Administrator" the problem goes away.

 

[Mark Rae [MVP]]

Found the problem. It is down to the Vista User security settings. If
I run Vista "As Administrator" the problem goes away.

Ah yes...

Presumably, though, you mean that you need to run VS.NET 2005 as
administrator...?

 

[TheDude5B]

Ah yes...

Presumably, though, you mean that you need to run VS.NET 2005 as
administrator...?

yes exactly. Have not got used to this feature of Vista yet so keep
coming across problems like this when trying to run different
programs. First thing I will try in the future is to run everything as
administrator.

 

[Mark Rae [MVP]]

yes exactly. Have not got used to this feature of Vista yet so keep
coming across problems like this when trying to run different
programs.

1) Right-click on the item on the Start menu which launches Visual
Studio.NET 2005

2) Select Properties

3) Click Advanced

4) Check Run as administrator

5) Click OK

6) Click OK

7) Launch Visual Studio.NET 2005

First thing I will try in the future is to run everything as
administrator.

I strongly advise you *NOT* to do that! Visual Studio.NET 2005 is very much
an exception - hardly any applications need to be run as administrator...