Re: URGENT | Framework version problem
- From: "Frans Bouma [C# MVP]" <perseus.usenetNOSPAM@xxxxxxxxx>
- Date: Wed, 02 Nov 2005 02:04:21 -0800
Nick wrote:
>
> We currently have 2 versions of the 1.1 framework being used in our
> project. The problem that comes up is really complex. We have
> certain controls that behave in contrasting fashions if run on
> different machines (having different versions of the f/w). Not only
> that, at times i even end up getting certain build errors like:
>
> Error: The dependency 'Managers, Version=1.0.2130.17591,
> Culture=neutral' in project 'PresentationValidators' cannot be copied
> to the run directory because it would conflict with dependency
> 'Managers, Version=1.0.2125.39306, Culture=neutral'.
>
> Moreover, this problem also creeps up very randomly, so we can't even
> reproduce it if wanted, at will. The versions we currently have are:
> 1.1.4322.573 and 1.1.4322.2032
those are the same version, with different file versions. THe assembly
versions are the same, 1.0.5000.0
The problem you're running into is with your own code, signed
assemblies. If possible, use a different buildnumber scheme, like
1.0.0.0, and manually increase that number when necessary and use
assemblyfileversion to crank up the fileversion number with each build.
This way your users can store a single version in the gac, the latest
fileversion, and be happy.
FB
--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
.
- Prev by Date: Linker Errors Porting from .NET 1.1 to 2.0
- Next by Date: Re: Digitally Signing Email in C#
- Previous by thread: Linker Errors Porting from .NET 1.1 to 2.0
- Next by thread: Re: Digitally Signing Email in C#
- Index(es):
Relevant Pages
|
