Here is an approaches to create self-extractable exe:
- Create a .zip:
- 7zip. Examples are here.
- WinZip (A valid license is needed to use the command line version)
- Windows Server 2003 Resource Kit Tools
- Create the self-extractable exe:
Here is an approaches to create self-extractable exe:
Domain Controller Machine
Other Machine
Related Articles
1. In IIS 7.0, click the Sites node, then get the ID for AgilePoint site.
2. Click on the AgilePoint node under Sites, then click on Logging icon.
3. Get the value for Directory:
4. Navigate to the location and select the subfolder with AgilePoint site ID. The IIS log file(s) is under that folder.
In the Setup project of VS.NET, you can write a InstallerClass and attach that to the Custom Action of the Setup project to do some custom steps like checking certain services, copying special files etc.
To debug this InstallerClass, just insert below line of code at the location you wish to set the break point.
System.Diagnostics.Debugger.Break();
When running your installer, Windows Installer will understand that’s a user defined breakpoint and let you chose to debug the program. See screen shots below.
After that, you can just press F10 to step through your code.
1. In AgilePoint Server Manager, check what is the web site associate with Enterprise Manager. In this case, the web site is call AgilePoint. Take note of the value of virtual directory. In this case, it is EM4.
2. Go to IIS Manager, right click on ‘AgilePoint’ site > Manage Web Site > Advance Setting, check the value for Physical Path. In this case, it is C:\Program Files\AgilePoint. So, the physical path for Enterprise Manager virtual directory is C:\Program Files\AgilePoint\EM4
Use msi2xml. For example, the file you want to replace is Test.dll and your MSI is TestMSI.MSI.
This command extracts the MSI files:
Open OutputDir and modify the file.
The extracted file names are some random numbers with no file extension, e.g. _132667984196873216. To identify the file you want to replace, open the TestMSI.xml generated by above command, then search for Test.dll and find the matching random number file name.
You may replace the file using the same random number file name. Modify the file size in TestMSI.xml too.
To pack the files back to MSI:
xml2msi.exe -m TestMSI.xml
You need the -m to ignore the 'MD5 checksum test' that fails when an MSIs file(s) are modified.
From my observation, the file size of MSI reduces after running xml2msi, but all the contents are correct.