Dear Customers :
I have a very important reason for the [assembly: AssemblyVersion("4.0.0.0")] , for why we always compile it into 4.0.0.0 ,
If we use the [assembly: AssemblyVersion("4.0.*")] , the version would be changed every time . The benefit of that is you could compair the version .
But , the disadvantage is , when you just update the dll to the product server , for example , we update the CuteEditor.dll to this forums , it would throws
FileLoadException : " The located assembly's mainfest definition
with name 'CuteEditor' does not match the assembly reference "
When the version is 4.0.* , the developers would get more trouble while they deploy the CuteEditor.dll , they must re-compile the application , and copy all dlls to the product server .
We could provide another solution :
1.We update the assemblyinfo.cs as [assembly: AssemblyTitle("CuteEditor 4.0 build 2004-12-15")] very time we compile the CuteEditor.dll , so everyone could know the last build time when they view the file dialog .
2.We provide a log file into the downloadable zip file . To let the user known the last build time and the version logs .
Is That OK ?
Regards , Terry .