13

I have a VS 2008 C# web app with a bunch of project references to custom dlls. These are all at a relative path from the web project. Recently I've noticed that Clean Solution removes some, but not all, of the dlls from the web app's bin\debug folder. For example:

<Reference Include="TowerCo.Utilities, Version=1.0.0.0, Culture=neutral, processorArchitecture=MSIL"> <SpecificVersion>False</SpecificVersion> <HintPath>..\..\Components\TowerCo.Utilities\bin\Debug\TowerCo.Utilities.dll</HintPath> </Reference> <Reference Include="TowerCo.WebControls, Version=1.0.0.0, Culture=neutral, processorArchitecture=MSIL"> <SpecificVersion>False</SpecificVersion> <HintPath>..\..\Components\TowerCo.WebControls\bin\Debug\TowerCo.WebControls.dll</HintPath> </Reference>

The first one works normally (clean cleans it, new versions copied to web project on rebuild) but the second does not. A side effect is that I don't automatically pick up changes to the dependency.

Thanks for any help.

Improve this question
6
  • Is the second DLL possibly in the GAC where the first one is not? Commented Oct 25, 2010 at 16:36
  • Good idea, but no, I don't have any of my dlls in the GAC. In general we use project references and deploy separate copies of components with each app. Commented Oct 27, 2010 at 14:47
  • I'm having this same problem. There seems to be a related issue in that the build server doesn't want to deploy this same assembly that doesn't get cleaned. It works on all other dev machines when compiling Commented Nov 8, 2010 at 18:49
  • Is it possible the dll not being removed is in use (or being held onto ) by the system when it is to be deleted? Commented Jan 17, 2011 at 17:59
  • try build/re build your solution. Commented Feb 11, 2011 at 23:25

2 Answers 2

Reset to default
4

It only seems to delete files it 'knows about'.

For instance old library files, and old references after having renamed projects are still there. Very strange. I always assumed 'Clean' was just a straightforward delete - and I don't quite understand why it isn't. Go in and check each folder by hand if in doubt.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

2

Sometime VS doesn't pick the latest dll if the version is same. Try changing your version in AssemblyInfo.cs and it should work.

In past, I faced the same issue when I was relying on size/timestamp but I later realized that by changing the version, Studio removes the older DLLs and copies the new DLLs.

Improve this answer

1 Comment

I can confirm this issue still occurs when you have modified the AssemblyInfo.cs version number by the smallest revision number.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.