Printable View
Greetings,
When I run the the PDW, it insists that the executable must be named "programDebug.exe", rather than just "program.exe".
"programDebug.exe" was something I made after an install, for the purpose of debbugging an issue; but now the PDW insisits that my exe be named that, whenever I try to package the vbp.
Can someone please help me get around this. I need it to just be called "program.exe".
I really appreciate it.
Thank you,
Jim
the PDW is the most horrible deployment tool ever
I would rather copy and register files manually than use that thing
what I recommend is you download and use INNO setup, as its the best installation software I have used (any others will probably tell you the same) and its free
but as far as your PDW problem, couldn't you just make the package over again? or is it a ton of custom files and stuff?
That's the thing. I try to, and then it gives me a message that there must be an exe named "programDebug.exe", for some crazy reason.Quote:
Originally posted by kleinma
...but as far as your PDW problem, couldn't you just make the package over again? or is it a ton of custom files and stuff? [/B]
Any clues at all. I don't know what more I can do. I've deleted the programDebug.exe. I make the vbp as program.exe; and then I freshly try to package the vbp.
I have no idea why its doing that to me.
Jim
make sure the last time you compiled the exe it was called what you want it. if needed recompile the exe. then go to PDW and click browse (dont select your project from the list if its there)
Thanks kleinma. What worked for some reason, was when I said "Yes" to save the project, after I compiled and made the exe.
By the way, I downloaded INNO, since everyone here recommends it. For the next project I do, I'll start out using that for the install.
For this project, I'm too immmersed in it to experiment. :-)
I'm actually looking very forward to testing out INNO, though. I want to see what all the fuss is about. :-)
Have a great weekend.
Jim