0

What i need is the user to be able pick not only the installation path, but also a path where they want to put configuration files for my program.

At the moment i have a setup project in the same solution as the actual program (the program is an outlook 2010 add-in, but dont think that matters). I tried to work with custom actions using a class library but that doesnt seem to work out. I have tried using different project types as Installer Class for the custom action, but none of them worked. I have a Windows Form with a button on it that should open a FolderBrowserDialog and put whatever folder the user chooses into a textbox. but whenever i try to do folderBrowserDialog.ShowDialog() the form freezes completely. The FolderBrowserDialog never shows at all.

Any help much appreciated :)

greets

Jojo
  • 1,875
  • 3
  • 29
  • 29
user2837747
  • 1
  • Now you are opening that windows from installer class ? but you dnt see folderbrowse dialog ? – Kurubaran Oct 02 '13 at 08:35
  • its not only not visible, also stops the whole form from doing anything. it goes (Not Responding) and just disappears after a few seconds. – user2837747 Oct 02 '13 at 09:11
  • There is a recommended way to get user input during application deployment, check my post here http://stackoverflow.com/questions/19087423/c-sharp-custom-action-windows-form-focused-issue/19089125#19089125 – Kurubaran Oct 02 '13 at 09:14
  • that seems pretty risky, editing the standard installer files. Also, will this work on a PC without the edited files? – user2837747 Oct 02 '13 at 10:39

1 Answers1

-1

Since you said "any help" would be appreciated:

You're using a tool that is horrible. Microsoft removed it from VS2012 and there are 5K+ votes on user voice saying to bring it back because it "worked just fine". Frankly, that represents 5K developers who hardly know anything about Windows Installer.

The tool abstracts and seals away so much Windows Installer technology that it fails to expose, besides a great many other things, the ability to customize the Installation User Interface Sequence in the way that you need and would be otherwise possible.

So instead you are forced to use InstallUtil custom actions to present UI in the InstallExecuteSequence where no UI is supposed to be shown. This violates several tenants of Windows Installer design and if this was an application you were talking about you'd likely never consider doing it.

If you want to do it right you only have 2 choices. Postbuild manipulate the MSI to inject what Setup and Deployment cannot (like manipulating IL in a built DLL because C# doesn't support something that the CLS does) or switch to a tool such as Windows Installer XML or InstallShield Professional that handles it properly in the first place.

I'm sure I will now be downvoted by a percentage of those 5K developers but I don't care. I've been developing installers for 17 years and I'm the top contributor on installer related tags and I know what I speak isn't merely opinion.

Christopher Painter
  • 54,556
  • 6
  • 63
  • 100