Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 27, 2010 02:32 PM by efess
Jul 18, 2007 03:11 PM|LINK
I have recently experienced this issue as well. So far, I have tried the following solutions:
I am about to install the hotfix, but I wanted to ask a question first. In my case, this error seems to be accompanied by three events in the server's application log. They are as follows:
I have not heard anyone else mention these events. Is anyone else getting these in conjunction with this issue?
Thanks in advance,
Jul 19, 2007 01:02 AM|LINK
cool, thank you i fixed my problem.
Jul 20, 2007 12:18 PM|LINK
Hey so...what was the answer then?
I was of the understanding that the hotfix is for another problem
Nov 06, 2007 03:39 PM|LINK
I had this problem in two different applications. I've fixed this error twice by including the following int he web.config file.
<trace enabled="false" localOnly="true" />
<compilation debug="true" strict="false" explicit="true" batch="false" />
Of course you can change the debug back to false when you deploy your application to production.
Dec 19, 2007 07:33 PM|LINK
I am still having this problem. I generally bypass it by forcing the website to recompile via the command line when I change a control. But I don't always get to it when someone else makes a change. When the website goes down this way, it's a hard "fatal"
until the website is recompiled and/or all the temp assemblies are deleted. Very nasty.
Can someone confirm if the temporary patch worked? If so, are we going to get an official update via a service pack?
Dec 19, 2007 07:43 PM|LINK
Try the hotfix:
We have not experienced this problem in production since installing.
Jan 07, 2008 03:59 PM|LINK
This worked for me
VS 2005 - Tools..Options...Projects and Solutions...Build And Run - set maximum number of parallel project builds to 1 to force the solution to build your project dependencies serially.
I had multiple projects in the solution and the implementation is a mess.
Jan 18, 2008 04:40 PM|LINK
hey hikingnerd...just looking back at your posts, have to criticize your methods...why would you post that you have a solution and not make it available to others? why not publish it somewhere?
Sep 21, 2008 04:47 PM|LINK
It's been long time since the last post in this thread was written - but there does not seem to be found THE final solution. Or am I wrong? I'm asking because I am having the same problem with my class library DLL included in a website project, even now
running the .NET 2.0 Framework with SP1, which in terms of Microsoft already includes the mentioned Hotfix Patch.
Also, all of the fixes and workarounds posted here didn't help in my case. Only pre-compiling and deploying the entire website seems to help, but is no considerable option in this project, since I should be able to use the dynamic compilation of ASP.NET
here. And the numRecompilesBeforeAppRestart attribute setting to 50 or whatever just delays the application crashing.
What is somehow special in my case, differing from most of the scenarios described before:
- Unlike most others, I'm not using any user control (or nested user controls) in the project that runs in the error, but simply a class library project compiled to a DLL/assembly for re-using purposes.
- The problem doesn't occur "randomly", but each time the application restarts after a dynamic compilation. This is what I found out by setting the numRecompilesBeforeAppRestart to the value 1.
- The problem occurs in a windows vista environment with .NET 2.0 SP1, therefore installing the hotfix is not neccessary nor possible.
- The problem only occours with any "self made" assembly, not with official ones from Microsoft (like Ajax.Net) or third parties. I'm using very common project settings in my own assemblies and have tested several variations / combinations with no success.
Could anyone provide some help here, or has anyone found the "ultimate" solution in the mean time?
Or is nobody having this problem anymore???
Nov 15, 2008 12:48 AM|LINK
Everyone on my development team is now running into this issue on our new project. We are also running Windows Vista SP1 with Visual Studio 2008 SP1 ASP.Net 3.5 SP1. This issue happens on a very simple project and is making development almost impossible
as it appears on every few compiles for three seperate developers. This project is NOT using any user controls or master pages. It is using WCF in a very simple service configuration.
I need some help to not abandon the project.