.Net dll name and version conventions
Posted on 2011-03-25
I have a .Net component, which is a DLL file, that support .Net 1.1, 2.0, 3.0, 3.5 and 4.0.
Right now all DLL has the same name, and I differentiate the .Net version in the DLL version.
So, my dll for .Net 1.1 version is: MyComponent.DLL and if you look inside it's version is 220.127.116.11
The dll for .Net 2.0 is the same MyComponent.DLL and if you look inside it's version is 18.104.22.168 and so on.
As you notices, I put the .Net version inside the product version.
But I don't like it. I was told to do so from my contractor, but I'm not sure this is the correct way, I don't feel it is.
I'd be more comfortable to name it like MyComponent.v1.1.dll and then us the version number to put the MyComponent version number.
What do you think?
What's the correct convention in this case?