question on shared assemblies

  • Thread starter Thread starter Tim Kohler
  • Start date Start date
T

Tim Kohler

I'm having a problem with shared assemblies > 2^16 bytes in size.

My assembly is in a solution along with a console app that references the
assembly. The app is set up to reference the assembly (the reference path
is pointed to the assemblies output directory). When I do a build, the
assembly is failing to build because the .dll is loaded.

I'm getting the following output from the build:
The file 'Test_Library.dll' cannot be copied to the run directory. The
process cannot access the file because it is being used by another process.

Could not copy temporary files to the output directory.


I've created a few other shared assemblies with no problems. This is the
first time I've seen this exact problem and in trying to run it down I've
discovered that if the .dll's size is < 65536 bytes (as all my other ones
are), this doesn't happen. It looks like VS is loading the .dll when I add
the reference for the console app. If I delete the console app's reference
to the assembly, I am able to build the library.


I hope one of you has run across this before.

thanks for any help,
Tim
 
I've confirmed through other sources that this is believed to be a bug. I
certainly hope MS fixes this as it really hampers developing a library of
any size or use with VS .NET. <sigh>
 
Back
Top