So apparently this is not a new problem with the dotnet framework. The "workarounds' that have been suggested to me are to delete the assemblies created in the .net temp folder but this requires a stopping of the iis server and of course, downtime for my site.
Oh, the microsoft "hotfix" for this problem also did not work for me.
I also have read arguments pro and con for turing off the "batch" attribute in the web.config file-makes sense you wouldn't want to mess with debug attributes in a production environment but it would also reduce the full site compilations to individual pages.
Has anyone come up with a better solution to prevent this corruption of the binaries/circular reference problem that occurs just "out of the blue"???
How about the new 3.0 framework? Does anyone think that might help with stability of assemblies?
thanks for any other possible workarounds.
I'm just surprised this instability hasnt' caused an uproar among the community? Or maybe I'm simply missing some 'best practice" in the deployment of our server and asp.net applications running on our box.?
regards,
brandon
Oh, the microsoft "hotfix" for this problem also did not work for me.
I also have read arguments pro and con for turing off the "batch" attribute in the web.config file-makes sense you wouldn't want to mess with debug attributes in a production environment but it would also reduce the full site compilations to individual pages.
Has anyone come up with a better solution to prevent this corruption of the binaries/circular reference problem that occurs just "out of the blue"???
How about the new 3.0 framework? Does anyone think that might help with stability of assemblies?
thanks for any other possible workarounds.
I'm just surprised this instability hasnt' caused an uproar among the community? Or maybe I'm simply missing some 'best practice" in the deployment of our server and asp.net applications running on our box.?
regards,
brandon