Answer by user195488 for .net: Version numbers for DLL vs EXE?
Simple answer is to increase the version numbers as you make changes. Don't keep the EXE and DLL in sync because there is no reason for them to be. The DLL is intended to be portable - any EXE could...
View ArticleAnswer by Adam for .net: Version numbers for DLL vs EXE?
You have touched on a very large topic, which really can get as complicated as you will allow it.Ultimately, the versioning approach you choose will be dependent on what you need to achieve, and how...
View ArticleAnswer by Daniel Mošmondor for .net: Version numbers for DLL vs EXE?
Look it from the other side - why do you NEED version numbers? For example one answer to that can be to know what is deployed at some clients location.So, if you have application that is deployed as...
View ArticleAnswer by Maxim for .net: Version numbers for DLL vs EXE?
In my opinion you have to manage their versions separate.Because 2 applications(EXE) can use the same DLL.What version the DLL will be ?The DLL's version should be independent of the EXE that runs it.
View ArticleAnswer by JohnD for .net: Version numbers for DLL vs EXE?
You'll probably get multiple opinions, but I would say to keep it simple and have the EXEs and the DLLs version stay in sync. I might change my opinion if you really intend to release versions of the...
View ArticleAnswer by Illuminati for .net: Version numbers for DLL vs EXE?
In my opinion you should have only one assemblyinfo file that is shared across the application. That way it is easy to maintain it. And of course it implies you have a single version for all your...
View Article.net: Version numbers for DLL vs EXE?
I have been recently versioning my product (exe) and increasing the build number each time in assemblyinfo.cs.Works great, my product is currently on version 1.5.x.x so in increase the 4 digit each...
View Article