Build errors - Access denied on my own project

[Guest]

I have a VS2003 solution with about 8 projects (class libraries, controls,
asp.net, etc..)

When I try to build. I get Access Denied on my own dll's.
For instance I'm trying to start the ASP.NET project, I get access denied on
the dll that holds the form's code.

Other times I get access denied on the dll that holds the interface that I
use to remote.

I am going so crazy because it seems like a bug and I am trying to debug it
with reasoning and logic. I check all of my references in all of my projects,
but how can I lose access to the dll for the asp.net project ????

(Thanks so much in advance)

 

[Dino Chiesa [Microsoft]]

systematically turn off the Read Only bit for the files that fail.

you can do it in explorer.exe or from cmd line with attrib -R <filename>

 

[Guest]

I just got the error again, so I checked for the dll it claimed AccessDenied
to (in all of the project directories) and none of them were ReadOnly. It
seems to be an intermittent problem VS.

 

[Guest]

When are you getting the access denied error? When compiling or when running
your asp.net application? If it is the latter, it may have to do with
Indexing Services. Indexing Services sometime locks newly deployed dlls for
asp.net applications in the temporary asp.net files directory.

Check out this link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;329065

HTH, Jakob.

 

[Guest]

I just found the same information FINALLY after digging through google,but
thank you very much still.
That seemed to fix it. It was really draining my productivity. I would have
to close and keep restarting VS and sometimes even the PC.
Well I hope this is the end of that. If not, I'll be back.

Thanks