Incorrect command line parameter specified /m=...Single File

[ClintG]

Hi

We've just upgraded to Studio X3 from 2012

I've built a project file that was created with the previous version and all works fine if I build an uncompressed debug build.

If I build a "Single File" and run it the installer goes through the initial (decompression ?) stage and then I receive the error



Incorrect <MyProgram> command line parameter specified '/m=...'

I have gone through settings searching for what might be passing these erroneous parameters but am unable to find the correct setting.

Any ideas ?

Regards
Clint.

[FrancescoT]

Dear Clint,

did you check if any "old DLL" has been left in your project folder from the previous compiler version?

Regards

[ClintG]

OK. A little embarrassed. The dialog is from our own product and because I didn't code it and I had never seen it I didn't recognize it. You were probably mystified at why I was showing you a screen shot of our product.

Anyway...there is, or was, a problem which was caused by some unfortunate project naming.

We named our Installaware project with the same name as our product, in this case Jim2 (.mpr or .dproj)

We rename the single compressed exe from Jim2.exe to Setup.exe as part of our build process.

When this is extracted it looks like it is launching the wrong Jim2.exe. I think it is extracting our Setup.exe and looking to launch Jim2.exe (the setup program's original name) and is in fact launching Jim2.exe (our product)

This appears to be a bug with Installaware X3 and the behaviour has changed since Installaware 2012

As a workaround, I renamed the Installaware project, amended the build process and now all is good with world again so it's not a show stopper

Regards
Clint.

[FrancescoT]

I'm happy you solved.

regards