Someone is locking the file!!1!!

Posted on:March 21 2006

Linking...LINK : fatal error LNK1104: cannot open file 'C:\Development\somelongpath\Irrlicht.NET.dll'

Yeah, dear VisualStudio, because you are locking that file yourself, you stupid **CENSORED**, argl. Currently, I'm getting this after every recompile of any file in the project. This seems to be a known bug, lots of people on the web are having the same problem: VisualStudio locks a compiled managed .dll after the first compile, and trying to compile it a second time will fail because the IDE cannot write to the file because it still locks it. Only restarting the whole IDE helps. Looks like I'm going to change the project setup, I think this a lot better then having to restart VisualStudio every two minutes..
update: Helped as expected. If anybody has this problem: Simply make visual studio copy the .dll automaticly to another directory and use that for running your application.

Comments:

Just try 'Clean Solution' before your re-compile...

...should solve your Problem, so you don't have to re-start VS :-)

HTH,
Duncan

Duncan Mac Leod

Quote
2006-03-22 11:59:00

yep, thx. But restarting is a lot faster than recompiling that huge project. :)

niko

Quote
2006-03-22 17:03:00

This would not have happened if you use VIM for developing, like real mean do.

Quote
2006-03-23 15:33:00

My only gripe so far with VS 2005 is when you cancel a build, using either Ctrl+Break or with the menu, it can corrupt the .obj of the file it was compiling, and you either have to rebuild the project or solution, or find the file( which sucks in large projects ) and right click it in the Solution Explorer and compile the single file, then all is well.

spintz

Quote
2006-03-24 04:23:00

Could you post a download link with a new version soon?

Jonathon

Quote
2006-03-24 14:33:00

Could you please set up a download link, or at least email me at( jonathon.mcintyre@yahoo.com)?

Jonathon

Quote
2006-03-26 13:45:00