Geek Answers Handbook

Visual Studio 2008 - the program immediately exited with F5 (start of debugging)

I had a strange problem with Visual Studio, where if I start debugging, it will exit immediately. It started after changing the assembly name in the project properties. If I change the assembly name to the previous name, the program will work fine. How can i fix this?

Here is the result when starting after changing the assembly name:

'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities\9.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities.Sync\9.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.Debugger.Runtime\9.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Debugger.Runtime.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\DEV\SerialDeviceMaintenanceUtility\SerialDeviceMaintenanceUtility\bin\Release\SerialDeviceMaintenanceUtility.vshost.exe', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Core\3.5.0.0__b77a5c561934e089\System.Core.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml.Linq\3.5.0.0__b77a5c561934e089\System.Xml.Linq.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Data.DataSetExtensions\3.5.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\WindowsBase\3.0.0.0__31bf3856ad364e35\WindowsBase.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\PresentationCore.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\PresentationFramework\3.0.0.0__31bf3856ad364e35\PresentationFramework.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\WindowsFormsIntegration\3.0.0.0__31bf3856ad364e35\WindowsFormsIntegration.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. The thread 0xd80 has exited with code 0 (0x0). The thread 0x174 has exited with code 0 (0x0). 'SerialDeviceMaintenanceUtility.vshost.exe' (Managed): Loaded 'C:\DEV\SerialDeviceMaintenanceUtility\SerialDeviceMaintenanceUtility\bin\Release\SerialDeviceMaintenanceUtility.exe', Symbols loaded. The program '[1632] SerialDeviceMaintenanceUtility.vshost.exe: Managed' has exited with code -1073741819 (0xc0000005).

Note. The path names given above are abbreviated to hide the assignment to a specific organization.

+6
c # visual-studio-2008 wpf
source share
4 answers

I would restore your decision after changing the assembly name (clean and build).

0
source share

I tried my best to disable this "turbo-exit" VS2008 function for several months. This seems to be related to the XML files in my project. At some point, I fixed it, but then I got a new machine from IT, and the problem was introduced again.

Check out Microsoft KB957912.

0
source share

Have you tried to configure the launch object in the application settings?

Also, did you try to set a breakpoint at the earliest available location (in a WPF application, this will be your App.xaml.cs)? Sometimes you just don't understand when things like InitializeComponent () fail ...

Last but not least, do you use reflection in conjunction with the old assembly name (as a string)? Try a project search

I just guess it's hard to say, given just the little information you provide :(

0
source share

More articles:


All Articles