Try our conversational search powered by Generative AI!
AI OnAI Off
noname
Do you have optimizeCompilations="true" in web.config? Try to change it false.
May 19, 2015 8:00
I was waiting to see if this worked before replying then forgot to reply. It did work, thanks! Any idea why? It also seems when running out of Visual Studio, the app restarts a lot. My session state is continuously expiring when debugging between pages even though the timeout is set to 60 minutes.
Oct 13, 2015 0:47
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
I'm intermittently receiving an error while debugging EPiServer sites through Visual Studio 2013.
CS0042: Unexpected error creating debug information file 'c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\990f7591\932224d\App_Code.PDB' -- 'c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\990f7591\932224d\App_Code.pdb: The process cannot access the file because it is being used by another process.
I can cause this error to be created purposefully by editing one of my .cshtml views and saving while debugging. However, I'm getting the error when I'm not making any changes to the source files. Sometimes it will come up immediately after building and running the site, sometimes after a couple requests, sometimes not at all. Something seems to be triggering a rebuild of a dynamically built assembly and then it fails because it can't access the .pdb (presumably because the debugger is using it), but it doesn't seem to be anything I'm doing. I've gotten it in my own site, and the Alloy site and the other developers on my team experience it too. Is there something running in the background of the EPiServer site that causes this?