469,929 Members | 1,430 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,929 developers. It's quick & easy.

Restarting IIS to build...

I have a development unit running XP Pro and I cannot get it to build a web
project without restarting IIS.

There errors in the task list are....

! Could not copy temporary files to the output directory
! The file'bin\project1.dll' cannot be copied to the run directory. The
process cannot access the file because it is being used by another process.
! The file'bin\project1.pdb' cannot be copied to the run directory. The
process cannot access the file because it is being used by another process.

The only difference between this unit and the other two running identical
installations is that I set the IIS default home directory to f:\wwwroot
instead of going along with the default c:\intepub\wwwroot folder.

This is not a permissions problem because it writes fine once IIS has been
restarted. I compared all other IIS properties and came up with nothing.

From my best diagnosis so far... I would say this is an issue with the GAC?

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access
Nov 18 '05 #1
3 1734
This is really a very annoying problem.

Probably you have a Web Application that has a reference to the
project1.dll, both of them are loaded in the same solution.
So, the ASP.NET worker process locks the files they have references, and
when Visual Studio.NET tries to overwrite the project1.dll, it cannot be
done because aspnet_wp.exe is already locking it.

Try building project1.dll on another separate solution

Sds

Daniel

"Jerry Boone" <je***@antech.biz.killspam> wrote in message
news:MZ*****************@newssvr11.news.prodigy.co m...
I have a development unit running XP Pro and I cannot get it to build a web project without restarting IIS.

There errors in the task list are....

! Could not copy temporary files to the output directory
! The file'bin\project1.dll' cannot be copied to the run directory. The
process cannot access the file because it is being used by another process. ! The file'bin\project1.pdb' cannot be copied to the run directory. The
process cannot access the file because it is being used by another process.
The only difference between this unit and the other two running identical
installations is that I set the IIS default home directory to f:\wwwroot
instead of going along with the default c:\intepub\wwwroot folder.

This is not a permissions problem because it writes fine once IIS has been
restarted. I compared all other IIS properties and came up with nothing.

From my best diagnosis so far... I would say this is an issue with the GAC?
--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access

Nov 18 '05 #2
Hmm... Maybe I am missing something or didn't say something... how would I
build one solution using a separate solution?

The project is a vb asp.net web application and the output is the dll -- I
will explain some steps to duplicate...

I start a new vb asp.net web app, drop a label on a page, set the code
behind load event to change the text property to "hello" and build the
project.

Build... works great...
Change some code behind & build... works great...
Run the web app from within the IDE... works great...
Stop the app and make more changes & build or run.... works great...

However... start the browser and browse to the page
Change some code and build...
The errors show up in the task list and the build is not successful.
Restarting IIS releases the hold on the bin directory files and then the
build works.

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access
"Daniel Melo" <da****@realtelecom.com.br> wrote in message
news:Oe**************@TK2MSFTNGP10.phx.gbl...
This is really a very annoying problem.

Probably you have a Web Application that has a reference to the
project1.dll, both of them are loaded in the same solution.
So, the ASP.NET worker process locks the files they have references, and
when Visual Studio.NET tries to overwrite the project1.dll, it cannot be
done because aspnet_wp.exe is already locking it.

Try building project1.dll on another separate solution

Sds

Daniel

"Jerry Boone" <je***@antech.biz.killspam> wrote in message
news:MZ*****************@newssvr11.news.prodigy.co m...
I have a development unit running XP Pro and I cannot get it to build a

web
project without restarting IIS.

There errors in the task list are....

! Could not copy temporary files to the output directory
! The file'bin\project1.dll' cannot be copied to the run directory. The
process cannot access the file because it is being used by another

process.
! The file'bin\project1.pdb' cannot be copied to the run directory. The
process cannot access the file because it is being used by another

process.

The only difference between this unit and the other two running identical installations is that I set the IIS default home directory to f:\wwwroot
instead of going along with the default c:\intepub\wwwroot folder.

This is not a permissions problem because it writes fine once IIS has been restarted. I compared all other IIS properties and came up with nothing.
From my best diagnosis so far... I would say this is an issue with the

GAC?

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and Access


Nov 18 '05 #3
Jerry,

I has a very similiar problem but mine was related to the Indexing Service
running on my W2K machine, which I had to disable. I was then able to
compile and run my .NET web application without restarting IIS every time.

Aiax

"Jerry Boone" <je***@antech.biz.killspam> wrote in message
news:MZ*****************@newssvr11.news.prodigy.co m...
I have a development unit running XP Pro and I cannot get it to build a web project without restarting IIS.

There errors in the task list are....

! Could not copy temporary files to the output directory
! The file'bin\project1.dll' cannot be copied to the run directory. The
process cannot access the file because it is being used by another process. ! The file'bin\project1.pdb' cannot be copied to the run directory. The
process cannot access the file because it is being used by another process.
The only difference between this unit and the other two running identical
installations is that I set the IIS default home directory to f:\wwwroot
instead of going along with the default c:\intepub\wwwroot folder.

This is not a permissions problem because it writes fine once IIS has been
restarted. I compared all other IIS properties and came up with nothing.

From my best diagnosis so far... I would say this is an issue with the GAC?
--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access

Nov 18 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Phil S | last post: by
1 post views Thread by Scott Lezberg | last post: by
7 posts views Thread by GTi | last post: by
9 posts views Thread by woolley.dean | last post: by
9 posts views Thread by walterbyrd | last post: by
4 posts views Thread by =?Utf-8?B?TWFyaw==?= | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.