tag:blogger.com,1999:blog-6579772240267288367.post1370818976642813765..comments2023-06-05T08:45:12.716-04:00Comments on kwblog: Two Versions of the Same Shared AssemblyKevin Berridgehttp://www.blogger.com/profile/13759114853595462455noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6579772240267288367.post-34974387296145694692008-11-07T12:44:00.000-05:002008-11-07T12:44:00.000-05:00@jonathan oliver: I never looked into updating the...@jonathan oliver: I never looked into updating the assembly name automatically during the Build. I was just doing it by hand.<BR/><BR/>But in the end, I abandoned the approach due to problems with the Visual Studio designer.Kevin Berridgehttps://www.blogger.com/profile/13759114853595462455noreply@blogger.comtag:blogger.com,1999:blog-6579772240267288367.post-24764023816274176432008-11-07T12:34:00.000-05:002008-11-07T12:34:00.000-05:00How did you go about getting the version into the ...How did you go about getting the version into the assembly name during the build? I was kicking MSBuild around and the "Version" and "AssemblyVersion" properties don't exist until a little too late.Jonathan Oliverhttps://www.blogger.com/profile/06779892180335556784noreply@blogger.comtag:blogger.com,1999:blog-6579772240267288367.post-85837832961277917022008-01-03T15:15:00.000-05:002008-01-03T15:15:00.000-05:00Very nice summary of this complicated subject.I ag...Very nice summary of this complicated subject.<BR/><BR/>I agree with your conclustion of using version number to change the assembly name (despite what I have writen in my first part on this subject... I will write the third part and explain why ILMerge can't be used in complicated scenarios)<BR/><BR/>as a reader, I would glad to hear from you again on this subject after implementing this in real life.Yonatan Leonovhttps://www.blogger.com/profile/05548493668397391438noreply@blogger.com