Hello everybody,
I'm working on a small Microstation .NET addin and the time has come to package it up and get it out to the people who need it. However I am faced with a dilemma. While building an MSI for the project is very simple I am curious if there was a recommended way of handling compatibility for multiple versions. The addin can be used for both Microstation as well as AecoSIM so there are two Program folders this could land in. It also could be run from the Workspace (provided it is local) as I understand so that is two (minimum) more possible spots. Any recommendations would be greatly appreciated.
-Tim
Unknown said:I'm working on a small Microstation .NET addin and the time has come to package it up and get it out to the people who need it
Are those internal to your organisation, or are you licensing a product to third parties unknown?
Unknown said:I am curious if there was a recommended way of handling compatibility for multiple versions. The addin can be used for both Microstation as well as AecoSIM so there are two Program folders this could land in
Things rapidly get out of hand when you have to cater for multiple versions, different target apps., etc. I recommend that you invest in an installer that will take care of that stuff.
There are a few installers available commercially. My current favourite is Lindersoft's SetupBuilder. Why? Because it makes it easy to find out thing about MicroStation such as its version and install location. In other words, it has useful macros to interrogate the Windows Register and assign those values to installation variables.
Regards, Jon Summers LA Solutions