ansaurus

Question

Visual Studio 2008 - Program exits immediately with F5 (start debugging)

Answer 1

A:

I would rebuild your solution after the assembly name change (clean and build).

Ted 2010-09-22 18:58:33

That doesn't resolve it. I've tried that a number of times.

Taylor Leese 2010-09-22 18:59:49

Answer 2

A:

I've struggled to disable this 'turbo-exit' feature of VS2008 for months. It seems related to the XML files in my project. I had it fixed at one point, but then I got a new machine from IT and the problem was introduced again.

Check out Microsoft KB957912.

gap 2010-09-22 19:24:27

I installed the KB you mentioned and I still have the same issue.

Taylor Leese 2010-09-22 19:37:21

Answer 3

A:

Have you tried setting the startup object in the application settings?

Also, have you tried to set a Breakpoint at the earlymost available location (In a WPF Application, that would be your App.xaml.cs)? Sometimes you just don't realize when stuff like InitializeComponent() fails...

Last but not least, do you use Reflection in combination with the old Assembly Name (as a string)? Try searching your project for anything

I'm just guessing, this is kind of hard to tell given only the little information you provide :(

Sebastian Edelmeier 2010-09-23 08:10:26

Yes, I tried setting the startup object. It didn't solve the problem. I can also do "step into" and get into my MainWindow.xaml.cs and past InitializeComponent(). I'm not using reflection by name. Just so it's clear, my program runs fine if you execute it outside of the IDE. It only has a problem when you try to debug in the IDE. In my comments I mentioned that the error is resolved by creating an assembly name <= 22 characters which I know doesn't really make any sense, but that is the behavior I see.

Taylor Leese 2010-09-23 15:10:30

Answer 4

+2 A:

Hope this helps: http://social.msdn.microsoft.com/forums/en-US/vsdebug/thread/e3619f20-f97d-4128-b274-94b1e3cdd211/

Sorax 2010-09-23 17:26:29

Turns out this was exactly it -- the only difference being that if the vshost.exe is 127 for me it still fails (<= 126 characters works fine). Here is another related issue: http://social.msdn.microsoft.com/forums/en-US/csharpide/thread/c9ead6da-5e30-4c1d-9187-74361ae5b37a/

Taylor Leese 2010-09-23 17:32:33

I opened a MSFT connect ticket here: https://connect.microsoft.com/VisualStudio/feedback/details/604075/visual-studio-2008-why-does-the-vshost-exe-have-a-full-path-limit-of-126-characters

Taylor Leese 2010-09-23 18:09:33

ansaurus

tags:

views:

answers:

Visual Studio 2008 - Program exits immediately with F5 (start debugging)

related questions