Assembly Version Numbers - Reset or change in project

[Matt Retzer]

Hello all -

This seems to be a sticky issue. I've read all the articles I could find on
dotnet assemblies and versioning - and the concensus seems to be to manually
version your assemblies. The question I have is - is there a way to change
the version number of an already referenced assembly in a project.

An example would be when I created a project, I referenced version 1.0.1 of
assembly A - then someone changed assembly A and the new version number is
1.0.2 - but my project still referenaces version 1.0.1 and gives me a
warning about copying the asembly to the run directory. Somehow my project
knows the version number of the assembly it was using, and is not letting it
go (even after deleing all references and rebuilding the project)

Any ideas?????

Thank you,

Matt

 

[Cowboy \(Gregory A. Beamer\)]

I do not have the info in front of me, but you can specify to use newer
versions in your config file. As long as you have not changed the interface
(public methods, properties, et al), you will be fine.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****