My son and I have written a mechanical engineering app in VB 2008. I'm a mechanical engineer; my son's a programmer. We hope to eventually market the app.
We paid no attention to the issue of deployment until very late in the game. My son finally came up with a deployment scheme that doesn't require much user intervention, but takes a lot of time - about 20 minutes.
I've installed a lot of software much more powerful and complicated than ours (MS Office, AutoCad, SolidWorks), that seems to install much more gracefully than ours. If I purchased a program and its install procedure went like ours, I might well abort the installation before it finished, and put it off until I really felt like suffering. My impression is that this is inherent in apps created in VB. Is that correct? Should we be considering porting our program over to C++ or Delphi?
We paid no attention to the issue of deployment until very late in the game. My son finally came up with a deployment scheme that doesn't require much user intervention, but takes a lot of time - about 20 minutes.
I've installed a lot of software much more powerful and complicated than ours (MS Office, AutoCad, SolidWorks), that seems to install much more gracefully than ours. If I purchased a program and its install procedure went like ours, I might well abort the installation before it finished, and put it off until I really felt like suffering. My impression is that this is inherent in apps created in VB. Is that correct? Should we be considering porting our program over to C++ or Delphi?