Re: dll version conflict
- From: "Peter Kirk" <pk@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Jun 2005 11:06:22 +0200
"Peter Kirk" <pk@xxxxxxxxxxxxxxxxxx> skrev i en meddelelse
news:OJqT35XcFHA.132@xxxxxxxxxxxxxxxxxxxxxxx
> Error: The dependency 'Alpha.Portal.Logging, Version=1.0.1944.20770,
> Culture=neutral' in project 'Alpha.Documents.Verification.WindowsService'
> cannot be copied to the run directory because it would conflict with
> dependency 'Alpha.Portal.Logging, Version=1.0.1747.23851,
> Culture=neutral'.
>
> Error: The dependency 'Alpha.Portal.Logging, Version=1.0.1747.23851,
> Culture=neutral' in project Alpha.Documents.Verification.WindowsService'
> cannot be copied to the run directory because it would conflict with
> dependency 'Alpha.Portal.Logging, Version=1.0.1944.20770,
> Culture=neutral'.
>
> Can someone explain what it means, and how I avoid it? Obviously there is
> some sort of conflict in versions of 'Alpha.Portal.Logging'. And I have
> just replaced the 'Alpha.Portal.Logging' dll with an updated version - but
> why does Visual Studio not just use the new version, and claim there is a
> conflict with the old version?
Well I found a couple of ways to "fix" the problem:
(1) go through all the references and change "copy local" to false. This is
tedious, and then seems to require that after a compilation I have to
manually copy all the necessary dlls to the run directory.
(2) go through all the references, remove them, and add them again. This is
also tedious, but at least I can compile again and don't need to manually
copy things when I want to run my app.
Anyone have some better solutions?
Peter
.
- References:
- dll version conflict
- From: Peter Kirk
- dll version conflict
- Prev by Date: Re: Buying VS.Net question
- Next by Date: Microsoft copies BlueJ
- Previous by thread: dll version conflict
- Next by thread: Microsoft copies BlueJ
- Index(es):
Relevant Pages
|
