CandiceJones wrote:The binary would seem to be the tough nut to crack?
But why crack the nut when you are big enough to swallow it whole?
I fiddled around with IS 10.5 for an hour (total usage) and finally found their "save as XML" option.
Someone more experienced with IS (your target customer) would presumably have found this too, or would be able to perform this extra step. The XML format is much more preferable when dealing with version control systems.
Keep It Simple... no?
A simple "we can only import .ism projects saved as XML" notice will suffice.
I am currently evaluating IA now, and although .ism import would be helpful, I think I am better off rewriting our install project from scratch. My predecessor was ambitious and a lot of the stuff he did simply doesn't work very well. Time to implement this thing from scratch.
So I think I can manage without IS import. Personally, I would like to see SQL Anywhere support before IS-import...
(running SQL-Anywhere scripts is one of the areas my predecessor didn't manage 100%
)