Re: Dotnet Assembly Versioning
- From: "Scott M." <s-mar@xxxxxxxxxxxxx>
- Date: Mon, 26 Mar 2007 14:44:15 -0400
The reason you have to recompile is that when you compile, you are going and
getting a copy of the .dll and bringing it locally into your application.
This only happens when you compile so, if you want the newer assembly, you
have to recompile.
Now, if the assembly were to become a shared assembly that is registered
into the GAC, then all you'd need to do is update the GAC with the new
assembly and your application would continue to run without any work needed.
-Scott
"Ben" <bendicht.haenni@xxxxxxxxx> wrote in message
news:1174922300.277810.275610@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi all,
First i have to state this is my first entry ever in a forum. So
please be forgiving...
I am a newbe to dotnet versioning...
The Situation is the following: Our application is using an external
managed .dll. Whos version is changing from time to time. The
interface is not changing at all. As i have included this dll in my
project i have to rebuild my application everytime the version number
is augmenting : 1.0.x.y. The major and minor build version do not
change.
using .net compact framework 1.1
Isnt it possible to state a policy that if x and y are changing the
clr still accepts these version numbers without recompiling my
application?
For any help thanks in advance
Ben
.
- Follow-Ups:
- Re: Dotnet Assembly Versioning
- From: Rad [Visual C# MVP]
- Re: Dotnet Assembly Versioning
- References:
- Dotnet Assembly Versioning
- From: Ben
- Dotnet Assembly Versioning
- Prev by Date: Re: hiding exe file as image
- Next by Date: Re: Width/Length of Data Column
- Previous by thread: Dotnet Assembly Versioning
- Next by thread: Re: Dotnet Assembly Versioning
- Index(es):
Relevant Pages
|