Hi guys..I have a question. Is it a good practice to set the Assembly Version of a DLL (set it in AssembyInfo.cs) ...?? Because actually it resolved the referencing issue that I encountered for days, but I'm not quite sure abouts its DRAWBACK.....What could be the future effects if I manually set the assembly version number? Say, 1.0.0.2, not 1.0.*....Thanks ..
-
-
Version numbers can be quite important. If you had an assembly at v 1.0.0.1
then you made changes to its methods with the next release of your application but didn't update the version number of the assembly then your installer doesn't think it needs to replace the one already on the HDD.
Its thinking is... "v1.0.0.1 is already here, I don't need to write it again", only the new 1.0.0.1 has new features or better ways of working existing features. -
This is what happens. I have a project for the DLL, I'll call it ProjectDLL.. Then, in my solution, I have lots of projects which reference the ProjectDLL. What I did was set the Copy Local into "FALSE" in all ProjectDLL references, and set the AssemblyVersion of the ProjectDLL's AssemblyInfo into 2.0.0.1..When I modify the class under the ProjectDLL and build that project and rebuild the entire solution, all the Projects that reference the ProjectDLL.dll also get the updated version of that DLL, based on the changes that I modified in the class...That's what's happening. Do you think there will be future errors?Comment
-
It sounds like you are not updating the version of the DLL when you make updates. Or am I wrong?Comment
Comment