I'm working on ASP.NET MVC2 project.
everything was OK in the last months, today suddenly, the time to load the first page raised from 5 seconds to 1:30 min !
I check the output view and I see many lines like this one:
WebDev.WebServer40.EXE' (Managed (v4.0.30319)):
Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.DurableInstancing\v4.0_4.0.0.0__31bf3856ad364e35\System.Runtime.DurableInstancing.dll',
Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
some of them are totally irrelevant to my project like this one:
'WebDev.WebServer40.EXE' (Managed (v4.0.30319)):
Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\System.Data.OracleClient\v4.0_4.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll',
Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
What happened ? I've tried to change in option not to load symbols, doesn't help, moved to release, same thing.
Any ideas what happened to my development environment ?
This is a Win7 X64 machine, VS2010 SP1.
Deleting all breakpoints solved this issue !
Related
I have recently bought new laptop:Hp specter x360 i7-6500 with 8gb RAM.
I have installed Visual Studios 2015 Community in an offline mode, later I updated it.I am currently working in c# window forms.
The point is when I press the button 'Start Debugging', VS build the program in normal speed, but it takes like 10-15 sec to show the output, even for the small programs. This whole thing is for first time debugging after code editing, if I close it and run it again without changing the code, it shows the output on the spot.
And if I run the same program in my old laptop, which has lower specs and same VS, that laptop show the result much quicker.
Based on your screenshot, I see that VS tries to download PDB symbols for system assemblies, which are used by your application. Loading the debug symbols provides simplify debugging of an application but it also slows down the application loading.
You can change symbols loading settings, in the Tools-Options-Debugging-Symbols menu of Visual Studio. Here you can disable symbol loading (if you would use this option you need to load symbols manually using the Debugging-Windows-Modules interface). Or exclude system modules which usually are not necessary to debug a common application.
Check this blog post which provides a great description about how VS uses debug symbols.
This seemingly simple problem has been driving me nuts for two hours. I want to attach a debugger to an app but VS 2012 refuses to load symbols from its PDB file. It works without a problem in VS 2010. The PDB is of the same name as the .EXE and located in the same folder.
This is a screenshot from VS2012:
And this is a screenshot from VS2010:
As you can see everything looks OK on both screens. However, this is another screenshot from 2012:
And this one is from 2010:
It's an exact same process.
It took me an hour of googling, searching and banging my head against a wall to try in VS 2010 and to find out that everything works well there. At first I was convinced I was doing something wrong.
Binary was not built with debug information.
Huh?? There is a PDB file, what other debug information it needs? It was obviously built with debug information since 2010 doesn't complain at all and I've debugged what I wanted just fine.
The app being debugged is compiled in VB6 (as in classic, legacy VB, not VB.NET).
Any hint, comment or question is welcome...
I have a PowerPoint add-in developed with .NET Framework 4.0/C#/VSTO.
The add-in loads fine when I manually launch PowerPoint, but when I press F5 in Visual Studio, the PowerPoint splash screen shows for a short period and then PowerPoint closes.
The Visual Studio output window shows only the following lines:
'powerpnt.exe' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The program '[6016] powerpnt.exe: Program Trace' has exited with code 0 (0x0).
The program '[6016] powerpnt.exe' has exited with code -2146233082 (0x80131506).
I've tried the following:
HDD scan
reinstalled VSTO
Do you have other suggestions to fix this issue?
I've uninstalled EMET 4.1 and, after a few reboots of the system, I've been able to debug again. Now I cannot say for sure that EMET was the culprit, since I've been able to debug before with EMET installed. I'll install EMET back when possible.
I have a sporadic issue whereby occasionally when I boot my computer, open a solution and start the debugger for a project set to run under IISExpress, that IE opens and shows a diagnose connection problem message. The Output window only shows:
'iisexpress.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The program '[4556] iisexpress.exe: Managed (v4.0.30319)' has exited with code 0 (0x0).
The program '[4556] iisexpress.exe: Program Trace' has exited with code 0 (0x0).
I am running IISExpress w/ Studio 2010 SP1 with MVC3 on Windows 7 (32-bit). Most days my system will start up and everything works fine. Occasionally after a reboot or cold start, the above happens. Typically when I am wireless only (but it has been a while since I've been hardwired). I've tried turning off the wireless card and re-enabling it and that does not change things either.
Typically the only thing I can do is switch back to the studio dev server for a while. Later when I go back to IISExpress it is fine again. (however just toggling the setting does not immediately fix the issue).
I am at a loss on how to debug what is happening. I have looked at my appplicationhost.config and it hasn't changed in a while.
Have you added any custom bindings to the applicationhost.config file at all? How does your machine get its ip address? is it DHCP? I found issues with my iis when my machine was assigned a new ip address which had been previously hardcoded in the config file. Do you normally laucnh VS in administration mode? This can also affect the avialability of the ports.
It hangs on for 10 seconds in different situations, in cs files, in aspx, chtml files, when opening solution explorer and so on...
Cumputer: i7, 8Gb RAM, SSD
Project is using SVN
No antivirus
No files on network resources
Tried on 2 different MVC3 Projects
What I have tried:
Disabling all extensions
Uninstaling resharper
Performing Clean Install
Uninstalling Web Authoring Component
Changing Editor for ASPX/CHTML files
Performing "ngen /delete System.Web.Mvc" etc, "ngen update"
Uninstalling SP1
Moving project from HDD to SSD
Uninstalling Visual SVN
Removing all bin/obj directories
Removing .suo file
Reinstalling MVC3
Is there any way to analyze logs or dumps to figure out what causing hangs?
UPDATE1:
Debugging visual studio the output window shows messages like these:
'devenv.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.ApplicationServices\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.ApplicationServices.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'devenv.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Abstractions\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Abstractions.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'devenv.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Routing\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Routing.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'devenv.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.DataVisualization\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.DataVisualization.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The thread '<No Name>' (0xffc) has exited with code 0 (0x0).
The thread '<No Name>' (0x17a0) has exited with code 0 (0x0).
The thread '<No Name>' (0x554) has exited with code 0 (0x0).
The thread '<No Name>' (0x11f0) has exited with code 0 (0x0).
etc
I found the reason why VS hangs:
my notebook has 2 video-adapters: integrated and discrete.
NVIDIA driver allows user to choose which adapter to use for a particular application.
I have an option set to: Use discrete for all applications.
So when VS uses my discrete video adapter - hangs are back.