September 2008 - Posts
Workaround ========== If you have "APPTYPE" In the Registry Key it would Give Error If you remove that value from Registry location the issue would be fixed HKCU\Software\Classes\Software\Microsoft\Windows\CurrentVersion\Deployment\SideBySide\2.0\PacakgeMetadata\{2ec93463-b0c3-45e1-8364-327e96aea856}_{3f471841-eef2-47d6-89c0-d028f03a4ad5}\imat..tion_3e64e3b4b5cafdd9_e70ba27c30f97a67\
Read More...
MSI Log ================= Action 15:16:33: FindRelatedProducts. Searching for related applications Action start 15:16:33: FindRelatedProducts. FindRelatedProducts: Found application: {7F0093FD-CC7D-4464-98FE-CD0EFDF55D97} MSI (c) (80:DC) [15:16:33:579]:
Read More...
If ClickOnce Store gets Corrupted we get Error of "Value doesn't Fall within the Expected Range" Workaround Remove Package Metadata registry Keys *HKEY_USERS\S-1-5-21-2146773085-903363285-719344707-241793_Classes(Sid Would be machine specific)\Software\Microsoft\Windows\CurrentVersion\Deployment\SideBySide\2.0\PackageMetadata\{2ec93463-b0c3-45e1-8364-327e96aea856}_{3f471841-eef2-47d6-89c0-d028f03a4ad5}
Read More...
WiX Installer consists of Actions that require elevation.The CustomActions are not designed to run under SystemContext. WiX does not generate a bootrapper setup.exe that can be used with an embedded manifest to say RequestedExecutionLevel = "RequireAdministrator".
Read More...
Windows vista wont Allow ATL control on the machine. We have Data Execution Prevention to stop Executing ATL control on Vista. Workaround Add This Post Build Event call "$(DevEnvDir)..\tools\vsvars32.bat" editbin.exe /NXCOMPAT:NO $(TargetPath) However
Read More...
Patch on that product which was installed through XCOPY and it was installing in 39 second. migrate to MSI and When they install the Patch on MSI.Patch takes 5 to 10 min during installation this is not acceptable. Workaround to this issue is Elimination
Read More...
A workaround to this problem is to go to the publish properties and then on the publish tab, select Application files and set the SEWOP_1_1_6_5/SEWOP.XmlSerializers.dll to exclude. Please add this to SGen Task <SGen BuildAssemblyName="$(TargetFileName)"
Read More...
If you create custom action through Visual studio 2005 which targets x64, You would see the Error During Build " Entry point 'xxxxxx' not found in module 'xxxxxx' for custom action 'Primary Output from xxxx'" If you are using VS 2008 It will build the
Read More...
The Windows platform has never had an integrated software-installation system. Instead, software developers have been responsible for creating their own installation routines or Scripts To copying data (Simple File Copy) To add registry Entries To register
Read More...
