Love the repackager. Used it to generate two MSIs from IE ActiveX control installations so far.

Suggestion 1: Don't require the user to select a setup.exe to launch. In my case, I want to do everything manually (i.e. click a link in IE, click yes to install an ActiveX control). I get around this by picking an EXE and then just saying "Don't run" it.

Suggestion 2: Could there be a "Launch Regedit at this location" for the registry keys, or their current value displayed in the UI? I can't make a decision based on just a classid GUID key name as to if it's related to my application. I had to go back and forward between Repackager and regedit a lot.

Otherwise, I'm really impressed. One happy "how-to" blog post coming up!

Regards
Craig
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Thank you for the kind words and excellent suggestions. I've added them to the master feature request list and hopefully we can get these enhancements worked in before too long. Note that v1.1 is out now with a handful of fixes included.

Remember: if you create a package, please share your recipe!
Answered 01/09/2009 by: bkelly
Red Belt

Please log in to comment
0
The moment I create one that I'm allowed to share outside my employer, I'd love to. :)
Answered 01/09/2009 by: crb
Yellow Belt

Please log in to comment
0
Understood. Maybe next time [;)]
Answered 01/09/2009 by: bkelly
Red Belt

Please log in to comment
0
Like crb, I also want to run nothing, no SETUP.EXE, at launch. I just have files and registry settings to put in place.

Which brings me to another feature request: Right now, as a workaround, I want to launch some simple text file reader (like NotePad.exe or list.exe) with a text file that describes what is happening. Both the text file reader utility (if I include one) and this text file itself are temporary, to be discarded when the installation is complete.

Therefore, they could stay in the temporary folder where the MSI extracts its files. But how do I reference that temporary folder? Is it the current folder? Sande
Answered 02/06/2009 by: snissen
Fourth Degree Green Belt

Please log in to comment
0
This is just for package creation purposes-- the OP was not suggesting the specified file was temporarily installed. While not impossible, such a thing would not be done with the AppDeploy Repackager.
Answered 02/09/2009 by: bkelly
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity