G
Guest
We have built an ADO.NET data provider which is causing a problem in aspnet applications, in the VS.NET development environment only
The first time the aspnet application is run, everything works fine. However, when the browser is closed (ie. the application is ended) in order to make changes and rebuild the application, there is a problem
Whenever the aspnet application is run after making changes, it causes the aspnet_wp.exe to consume 100% of th
CPUs time and the machine hangs.
I think that the problem is related to the ASP.NET dynamic update. VS.NET hangs when deploying the new version of the web app. The VS.NET fails to copy the provider dll because it's locked by aspnet_wp.exe (by the previous run of the application)
We have found a couple of workarounds
1) Killing aspnet_wp.exe after exiting the app. will allow the app to be changed and redeployed/run
2) Changing the idelTimeout value in the machine.config file from infinity to 1 second also resolves the problem, but causes some other problems (you lose application state, the interactive debugger fails, and caching configuration information in a Singleton no longer works
Does anyone know how this problem can be resolved?
Is there a setting which must be made in the provider to cause it to be unloaded when the applicaiton ends?
Is there a less intrusive workaround than the one mentioned above
Or, is this a problem in asp.net that needs to be resolved from the MS end
Thanks
Jason Hinsperge
iAnywhere Solutions
The first time the aspnet application is run, everything works fine. However, when the browser is closed (ie. the application is ended) in order to make changes and rebuild the application, there is a problem
Whenever the aspnet application is run after making changes, it causes the aspnet_wp.exe to consume 100% of th
CPUs time and the machine hangs.
I think that the problem is related to the ASP.NET dynamic update. VS.NET hangs when deploying the new version of the web app. The VS.NET fails to copy the provider dll because it's locked by aspnet_wp.exe (by the previous run of the application)
We have found a couple of workarounds
1) Killing aspnet_wp.exe after exiting the app. will allow the app to be changed and redeployed/run
2) Changing the idelTimeout value in the machine.config file from infinity to 1 second also resolves the problem, but causes some other problems (you lose application state, the interactive debugger fails, and caching configuration information in a Singleton no longer works
Does anyone know how this problem can be resolved?
Is there a setting which must be made in the provider to cause it to be unloaded when the applicaiton ends?
Is there a less intrusive workaround than the one mentioned above
Or, is this a problem in asp.net that needs to be resolved from the MS end
Thanks
Jason Hinsperge
iAnywhere Solutions