>Of course that causes trouble -- if your CLSID changes with every build, your COM clients will have a hard time keeping ><up!
I have a fixed version number so the CLSID does not change for every build, I bump up the FileVersion instead (it's a QA thing).... regarding the "latest-is-greatest versioning model", having a fixed GUID means I must deal with proper versioning, but then again it allows you to bump up that version number pr. build. I was looking for some best pratics here and as you say: it depends on your versioning strategy. I just wanted to hear what others do ... and I must say I about to go with the latest-is-greatest hits, I don't know how many times other developers have changed the versionnumber and broken every running client :( so yes latest greatest. thanks for your input here, @llan =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with C# November 29 - December 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
