Compile error in VS.NET 2008 (VB.NET) that I can't get rid of!!

Question

I can't shake this error when compiling my Visual Studio.NET 2008 solution. The project that's generating the error is a VB.NET Web Application in a 12 project solution (mixed types and languages).

I've tried all the tricks I can find on google, and the obvious of removing the directoy and folder manually.

I'm running Vista Business 32 with VS.NET 2008 SP1. This just started happening out of the blue today and I've rebooted a bunch and even re-applied SP1 for VS.NET.

Any ideas or has anybody seen this?

vbc : error BC31019: Unable to write to output file 'G:\Projects\TCA.NET\TcaNet\WebUI\obj\Debug\TcaNet.WebUI.pdb': Unspecified error

Update:

After thinking about this and not finding any solutions from answers or via the Internet, I went ahead and moved my entire solution to my C:\ drive vs. my G:\ drive (both are local). Doing this fixed my compile problem for some reason.

Answer 1

hi,

I have found a list of thing to try to fix your problem :

Zen-turkey Fix list

Hope this help!

Answer 2

maybe it is a dependency problem. check the build order of all the projects..

sysinternals tools should be of help here. using process explorer, are you able to find out if any process is locking this file? another useful tool is process monitor. after applying a filter for the pdb file, capture a trace of all file access activity..

Answer 3

Restart IIS on local.

If that's not the issue then, install Unlocker and try to delete that pdb file when you get the error, Unlocker will tell you which process is holding an open handle to that file.

Answer 4

I had the same error a few weeks ago when I was compiling on my server from my laptop. Turns out that if G: is a network drive, this could fail. Microsoft have said that fixing this is not a priority, and that there's much better ways of doing things (such as source control). For a one-man project though, it's a pain.

Answer 5

After thinking about this and not finding any solutions from answers or via the Internet, I went ahead and moved my entire solution to my C:\ drive vs. my G:\ drive (both are local). Doing this fixed my compile problem for some reason.

Answer 6

I had this in Visual Studio 2005 except it was Error 1. I restarted my machine and it fixed the problem.