Huseyin Tufekcilerli wrote:
> and after an update it may become "FooBar-1.1.456-setup.msi" which can
> be installed alone or on top of the first version. But as far as I can
> see, there are some issues about changing the name of .msi file. In my
> opinion, as far as we change our Package ID's, it
I want to know what is the naming convention you are using for your
.msi files. For example I want to organize my setup packages like
this:
ProductName-Major.Minor.Build-setup.msi (like "FooBar-1.0.123-setup.msi")
and after an update it may become "FooBar-1.1.456-setup.msi" which can
be installed
2 matches
Mail list logo
