Last post Feb 03, 2009 01:04 AM by HIt
Jun 22, 2006 05:44 PM|ina_don|LINK
Jun 24, 2006 09:34 PM|omar_k|LINK
Do you get this error all the time? I've not seen it before, but if you are always seeing it, I would recommend trying to re-install Visual Studio. If it still persists, let me know and I'll get you in touch with a support person.
Jul 31, 2006 11:50 AM|wortho|LINK
Oh we are a small team of 3 using VS2005 MSDN version and we all get this error several times a day during debugging.
Workaround 1: Check if there is still a webserver running in your taskbar from a pervious debug, close it.
Workaround 2: Clean Solution and sometimes you have to do a full Rebuild.
If you have a fix we are all ears!
Aug 30, 2006 09:39 AM|cheintz|LINK
Aug 30, 2006 09:08 PM|Peter Ritchie|LINK
I just started to use this add-in yesterday and the "The application domain in which the thread was running has been unloaded" error is one of the many problems I've encountered as well.
This occurs me, repeatedly, when I load VS2005, load my solution and try to debug (F5). Pressing F5 again seems to work.
Aug 30, 2006 09:13 PM|vivek_iit|LINK
My two cents:
Each application has its own App Domain inside the aspnet worker process. And there can be multiple instances of an Application object inside a particular App Domain each catering to a different request.
ASP.NET creates a separate thread for each such application instance inside an App Domain and CLR manages the thread pool. After some time, when there are no requests to service and a specific timeout period, the Application object kills itself and the app
And if somehow when ASP.NET tries to unload the application and an exception occurs, we get this message. Another case I have seen this error coming is when you are running your project on low memory.
Oct 30, 2006 09:35 AM|net4developers|LINK
I was getting the same error which i had posted at
But i just closed to VS.net2005 and again started the application and it worked fine?
Oct 25, 2007 08:06 AM|deepak.vasudevan|LINK
Is there any fix for this? I have been facing this issue since yesterday Every 'Build Solution' gets this message and when I try the second time it works fine.
Nov 15, 2007 06:23 AM|Shalini85_prec|LINK
yes you are correct. It worked out well.
Feb 24, 2008 09:38 AM|The Tornado|LINK
I get this error a lot these days while working on my website using C#
any way I know there's nothing for C# to do with this error but when I close the solution and reopen it, every thing works fine
can we report this as a bug in VS 2005 ? [:D]
Jan 23, 2009 09:38 AM|rajuls|LINK
I have also encountered this problem, and what I did is that I have clean all the Asp.net temporary files and than rebuild the application.
The path is <root directory>(in my case is c) C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files
The application build successfully.
Feb 03, 2009 01:04 AM|HIt|LINK