Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Oct 08, 2010 01:38 PM by maxstell
Apr 29, 2008 05:07 PM|LINK
Whenever I debug an ASP.NET page in VS2008 (no matter how simple the page is), it hangs for at least 90 seconds. The "build started > build succeeded" bit only takes three or four seconds...then it hangs for what seems like an eternity. Periodically, "Loading
symbols xxxxxxxxxxx" will flash at the bottom, and finally after about 90 seconds, it'll hit the Page_Load event.
Any idea as to what's going on?
Thanks in advance.
Apr 29, 2008 08:35 PM|LINK
Have you tried to apply the fix mentioned on:
Apr 29, 2008 08:54 PM|LINK
Thanks for the quick response. You're responding faster than VS is debugging [;)]
I did try the hotfix - it fixed some other problems I was having (slow performance in the designer and code windows, etc.), but it didn't stop the debug issues. I just timed it twice - it's over two minutes between the time that VS says "build succeeded"
and the Page_Load event. The build and the Page_Load events only take about 4 seconds each respectively.
Any other ideas?
Apr 30, 2008 09:10 AM|LINK
May 01, 2008 12:14 PM|LINK
Thanks for the response. The dialog under Tools > Options > Debugging > Symbols is empty. Any other ideas?
Would you like me to send any details to the address you mentioned above? I'm happy to do anything to contribute to a resolution.
Aug 08, 2008 09:03 PM|LINK
We have this problem as well. Using asp.net 2.0 with vb.net on VS 2008, win xp. Our project is taking a minute to start the debugger and get going. It's worse on another one of our projects. After the browser loads, it just sits there waiting for it
to finish loading the symbols as seen in the Output window. The project compiles within about 10 seconds but takes a minute to start up after that. Productivity has gone south.
I have tried most things I can find on other blogs for solutions but no luck. The Tools-Options-Debugger-Symbols settings is empty so it doesn't point to a bad path. Should be okay there. There isn't an environment variable _NT_SYMBOL_PATH so okay there.
Turned on Debugger Exceptions but nothing seems to be slowing it down on startup.
It appears that it just takes forever to load symbols. Tried to use the Microsoft symbol server to create a local symbol cache but it prompted me for the location of a couple of things and the blog wasn't much help there.
If I don't make any code changes, it starts up pretty fast. A one line code change causes it revert back to molasses. If I create a brank new web site project, it starts up the debugger pretty fast.
Has anybody come up with a solution to this?
I see that VS 2008 SP1 might be available next week (8/11/08) per the MSDN subscriptions home page. Hopefully that will help.
Aug 13, 2008 09:37 AM|LINK
I had the same problem and made all of the adjustments as mentioned in this forum but it didn't help. I began to suspect that the slow loading time of the dlls had to do with security settings. It appears that access to the dlls goes through security checking
that is part of the operating system and not part of VIsual Studio. The dlls are located in a directory for your application under:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\
In order to speed up the security checking, you need to remove all of the security settings on the root folder of your application in the above mentioned directory, or on the directory "Temporary ASP.NET Files" if you want to have it apply to all web applications
You right mouse click the folder and select Properties -> Security
Remove all users and groups. Some will not be allowed to be removed because they inherit their permissions from their parent folder. You must first remove the inheritance by clicking on the Advanced button and then uncheck the "Inherit from parent..." checkbox.
Then remove the user or group. There must not be any users or groups where the checkboxes for their permissions are greyed out. If they are greyed out, it means that you didn't remove the inheritance from their parent.
After you have removed all users and groups from the folder, you then need to add the following users and groups:
Give each of these accounts full permission. Click on the Advanced button again and check off the "Replace permission entries on all child objects..."
Aug 13, 2008 06:02 PM|LINK
Thank you so much for your reply. I have applied your changes but no luck. We are still at a 30 second start up time minimum. it builds in about 2 seconds and then takes 25 seconds to load all the symbols and get going. The slowest symbols to load are
from this folder:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root
We have installed .Net 35 SP1 and VS 2008 SP1.
We turned off our anti-virus to make sure it wasn't slowing things down. No help.
Our project is not that big but we are using user controls. Watching the output window, it loads files from the GAC fast but is slow on the above Temporary ASP.Net\root folder.
Anyway, if anybody else has any ideas, please let me know. I'm assuming we should be able to start up faster than 30 seconds the build only takes 2-3 seconds.
Aug 21, 2008 10:39 AM|LINK
Aug 21, 2008 04:40 PM|LINK
THanks. I don't have that variable so good to go there. We have a case opened with Microsoft. Will post the results soon.