Hi,
I'd like to modify (obfuscate) my assemblies before they are packaged in the MSI by the Visual Studio Setup Project. However, it looks like it always builds before it packages the files. Is there a way to force it to take the already existing files from the primary output and use those for packaging without rebuilding them
Thanks,
Tom
Modify assemblies before MSI packaging
Hot Topic
- How do I use set focus to next "tab-able" control
- Clear Clipboard
- Problem with textbox and databinding
- Format phone number
- Creating custom border
- usercontrol, collection of class and persistence
- Calling an event within another event in C#
- Welcome back Ken
- Language attribute at application’s exe/dll files.
- Which control has focus?
Windows Forms
- Sample Code: DataGridView progress bar column
- Nesting Datagrids
- How to make an application containg WinForms designer ?
- datetime help
- ComboBox DroppedDown
- Drag&drop at run time
- multiple comboboxes selecteditem problem
- Hide the Last row in DataGrid
- Newbie : How to add the Xpander controls ?
- how to write my own Winforms control and use it in IE
Modify assemblies before MSI packaging
Mohit6032
AdmSteck
Mervyn
Another approach is more manual, but can be done, and probably even scripted with a batch file or so.
Pre Step: Build your setup project so that it does NOT use built outputs, point it to include assemblies from disk. The best solution is to pick them up from a sub directory of the solution the Setup project is in.
Step 1: Build your application. You can use MSBuild or DevEnv /Build
Step 2: Copy the built binaries/files to a sub dir where the setup project is going to pick them up from.
Step 3: Obfuscate your binaries
Step 4: Build the Setup project. If the setup project is in another solution, it's easier ot use DevEnv /Build, or you can specify the Setup project name.
Hope this helps.
Kevin Currier