I have a solution with several projects, including a web project front-end. The web project references the "businessrules" project which in turn references the "settings" project. I am using project references and not assembly references. Anyway, lately when
I try to recompile, I often get errors. If I wait a few minutes and try again it works. But this is highly irritating. It seems to be related to when I go to the web page. Is it possible IIS is locking .PDB files? My compilation output starts with the settings
project, which often has output like the output below. The output below is what I get just when I try compiling the web project. If I try compiling the full solution i will get several errors like the ones below. Has anyone experienced this before? As I said,
if I wait a short while it goes away, but it does greatly interfere with the flow of development.
------ Build started: Project: Settings, Configuration: Debug .NET ------
Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Satellite assemblies could not be built because the main project output is missing.
------ Build started: Project: BusinessRules, Configuration: Debug .NET ------
Preparing resources...
Updating references...
Performing main compilation...
vbc : error BC31019: Unable to write to output file 'C:\MCI\Settings\obj\Debug\MCI.Settings.pdb': Access is denied.
Building satellite assemblies...
Satellite assemblies could not be built because the main project output is missing.
------ Build started: Project: mci_ui, Configuration: Debug .NET ------
Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
---------------------- Done ----------------------
Build: 1 succeeded, 2 failed, 0 skipped
I had this very same problem, how ever it would not go away. I did a reinstall of VisualStudio.Net, and was able to complile fine. But now when I go to test my app, I recieve a popup message stating: "Security hasn't been setup correctly for SQL debugging on
server MAIN\VSdotNET. SQL Debugging terminated." and the error message : "Unable to communicate with debugger on MAIN\VSdotNET (Error = 0x80004005). Debugging disabled for connection 52." Everything was working fine, I have been developing for 2 months with
out a problem, now all of this. For the life of me I can not solve this problem. Has anyone else experianced this, or have any Ideas ??
Hi guys, I also am having this problem. Don't have the solution yet but 2 little work-arrounds. You browse with windows explorer to your solutions directory. Open the relevant project and delete the OBJ directory. You check everything in this project in at
SourceSafe and compile the project. When i have the solution to this problem I'll post it right here. Greetz ThaYoung1!
This works but I'd prefer a neater solution. I thought my virus scanner was interfering but this does not seem to be the case. Maybe someone from the VS.NET development team could look into this? Note: I never had this problem until I migrated to VS.NET 2003.
Andre
I found out that ASP.Net needs access to several different folders. Here is a list of where it needs access: 317012 INFO: Process and Request Identity in ASP.NET http://support.microsoft.com/?id=317012
This a really good point. The error message is definitely caused by not having the correct permissions to perform the compile. I have found the error can generally be resolved by setting the ASPNET user, or depending on OS the IIS_WPG (IIS Worker Process
Group user), modify permission with the additional ability to delete subfolders and files set to propagate through the entire application folder. Or in this instance the entire solution folder.
Stephen Vaki...
Contributor
2540 Points
508 Posts
vbc : error BC31019: Unable to write to output file '{...}.pdb': Access is denied.
May 20, 2003 04:33 PM|LINK
------ Build started: Project: Settings, Configuration: Debug .NET ------ Preparing resources... Updating references... Performing main compilation... Building satellite assemblies... Satellite assemblies could not be built because the main project output is missing. ------ Build started: Project: BusinessRules, Configuration: Debug .NET ------ Preparing resources... Updating references... Performing main compilation... vbc : error BC31019: Unable to write to output file 'C:\MCI\Settings\obj\Debug\MCI.Settings.pdb': Access is denied. Building satellite assemblies... Satellite assemblies could not be built because the main project output is missing. ------ Build started: Project: mci_ui, Configuration: Debug .NET ------ Preparing resources... Updating references... Performing main compilation... Building satellite assemblies... ---------------------- Done ---------------------- Build: 1 succeeded, 2 failed, 0 skippedFunkFlii
Member
5 Points
1 Post
Re: vbc : error BC31019: Unable to write to output file '{...}.pdb': Access is denied.
May 26, 2003 08:32 PM|LINK
ThaYoung1!
Member
339 Points
91 Posts
Re: vbc : error BC31019: Unable to write to output file '{...}.pdb': Access is denied.
Jul 04, 2003 07:34 AM|LINK
ThaYoung1!
avc4u
Member
20 Points
4 Posts
Re: vbc : error BC31019: Unable to write to output file '{...}.pdb': Access is denied.
Aug 13, 2003 07:47 AM|LINK
geraldbauer
Member
20 Points
4 Posts
Re: vbc : error BC31019: Unable to write to output file '{...}.pdb': Access is denied.
Oct 27, 2003 02:22 PM|LINK
br00t
Member
4 Points
2 Posts
Re: vbc : error BC31019: Unable to write to output file '{...}.pdb': Access is denied.
Jul 19, 2007 05:05 PM|LINK
You can also check out:
http://zen-turkey.com/blog/default.aspx?id=34&t=Visual-Studio-2005-VBC-Error-BC31019-Un
For a list of possible workarounds.
LBarber
Member
2 Points
1 Post
Re: vbc : error BC31019: Unable to write to output file '{...}.pdb': Access is denied.
Feb 21, 2008 05:22 PM|LINK
This a really good point. The error message is definitely caused by not having the correct permissions to perform the compile. I have found the error can generally be resolved by setting the ASPNET user, or depending on OS the IIS_WPG (IIS Worker Process Group user), modify permission with the additional ability to delete subfolders and files set to propagate through the entire application folder. Or in this instance the entire solution folder.