Hi.
I'm working, doing a dll project wich i want to have versioning.
I know i can change the version number by making changes on assemblyinfo.cs (is there any other way?)
I modify the output folder for dll to a specific one - my ideia was that i could keep all diferent dll versions.. as i'm doing now i allways replace the previous dll version. is there any way to keep all dlls?
Yes. You can have the same assembly/dll of different versions in .NET Framework. In fact, this side-by-side execution of multiple versions of the same component is a sin-qua-non feature in .NET since beginning.
If your assembly is a private assembly (not registered in GAC), then it will have to be copied to the folder where your application (that uses this assembly) resides. When the application is executed, it will refer to this private assembly found on its path
regardless of the version! Thus if you have two applications of different version (foo1.exe & foo2.exe), then you can have them refer to two separate versions of dll by copying foo1.dll to foo1.exe's folder, and similarly foo2.dll to foo2.dll's folder.
There are two ways to change an assembly's version - one, as you mentioned through the assemblyinfo.cs and two, from the project->properties option.
net
Warm Regards.
If my post provides any insight, please mark it as answer.
Marked as answer by Dino He - MSFT on Feb 24, 2012 07:03 AM
dr.Xis
Member
79 Points
84 Posts
versionning a dll project
Feb 18, 2012 07:01 PM|LINK
Hi.
I'm working, doing a dll project wich i want to have versioning.
I know i can change the version number by making changes on assemblyinfo.cs (is there any other way?)
I modify the output folder for dll to a specific one - my ideia was that i could keep all diferent dll versions.. as i'm doing now i allways replace the previous dll version. is there any way to keep all dlls?
thanks
prahladyeri
Member
224 Points
43 Posts
Re: versionning a dll project
Feb 19, 2012 04:39 AM|LINK
Yes. You can have the same assembly/dll of different versions in .NET Framework. In fact, this side-by-side execution of multiple versions of the same component is a sin-qua-non feature in .NET since beginning.
If your assembly is a private assembly (not registered in GAC), then it will have to be copied to the folder where your application (that uses this assembly) resides. When the application is executed, it will refer to this private assembly found on its path regardless of the version! Thus if you have two applications of different version (foo1.exe & foo2.exe), then you can have them refer to two separate versions of dll by copying foo1.dll to foo1.exe's folder, and similarly foo2.dll to foo2.dll's folder.
There are two ways to change an assembly's version - one, as you mentioned through the assemblyinfo.cs and two, from the project->properties option.
net
If my post provides any insight, please mark it as answer.
prahladyeri
Member
224 Points
43 Posts
Re: versionning a dll project
Feb 19, 2012 04:41 AM|LINK
Yes. You can have the same assembly/dll of different versions in .NET Framework. In fact, this side-by-side execution of multiple versi
If my post provides any insight, please mark it as answer.