Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider. Azure Databases. Autonomous Systems. Education Sector. Microsoft Localization. Microsoft PnP. Healthcare and Life Sciences. Internet of Things IoT. Enabling Remote Work. Small and Medium Business. Humans of IT. Green Tech. MVP Award Program.
Video Hub Azure. If you open your MSI file there sould be calls of the type in 3. The obvious question is: How do you know it's not being called? I've never known Debugger breaks to work from custom actions either. Also, in a VS setup, custom actions run with the localsystem account, so the CurrentUser registry key for the system account is going to be odd.
I suspect you're looking at installer class code as if it's just boring application code but it's not. You're running as a plug-in on an msiexec.
You don't need an Installer class to save the install directory. If you want to avoid having installstate files being kept around, don't use installer classes.
Most setups that see this as an issue have some mechanism such as a global event or mutex that the app checks for and the uninstall sets.
In other cases this is not seen as a problem because Windows has probably marked the exe for removal at the next reboot, and the fact that it's sitting somewhere on disk until then isn't a problem.
Thanks again for all your help Phil. I am sorry it has spanned a few days before this reply. I am guessing this would mean that it is deeming the condition of the Uninstall custom action to be false and therefore not ensuing a call to the Uninstall method.
Is this a correct assumption? I have not set conditions for any of the custom actions and remembering that the Install method is called I ask is it different for Uninstall? Does the Uninstall method possibly require a condition that evaluates to true? I may have had my main executable marked as Permanent at one time but I set it back to "False". I have read some of your other posts, and I'm paraphrasing, "Once an item is marked Permanent it is always Permanent.
However, I had a project output executable that I was trying to call from Uninstall at first and set its Permanent properties to True. When I uninstalled the product the next time the executable lingered. When I set the property to false it was removed on the next uninstall. These have been clean installs and uninstalls every time, i. I don't believe this to be an upgrade issue.
I don't have much experience using Orca but is it possible that the GUID is the cause of it certain methods not being called? There is actually no such thaing as an "uninstall custom action". There are just custom actions that have conditions. In Visual Studio setups, a common uninstall condition is that the custom action will be called if the component is being uninstalled.
Or use the trac-wiki - orca. And use Firefox v3 or higher for administration tasks Thanks for the help before. I didn't dream that the default installation would be looking in the wrong freaking folder. I figured it out.
Then I went back to Firefox and tried to compile here again, but now got the error: "language files compilation have been failed'. And after that I also got the fatal error page in Firefox I have the same problem but i can't even compile it.
I even get an error using this forum. XML read failure there was a problem receiving the xml data:. I reckon its a far more comprehensive forum set up than orca and if I could use it with Dolphin then it may be easier. The password encryption on 7. X makes it impossible to carry over any current Dolphin members to phpBB. If you installed them both from scratch it's possible with heavy modifications. Also the Edit, Delete andf folder options are not doing anything which means I can't create any forums.
First of all I want to thank everyone for providing such good information on fixing the lanuage problem, It was a very simple fix. However, All of the wording is in white text and the description bars that should be behind them is not there. I saw that this was mentioned in the thread earlier, but I never saw a fix posted. Anyone have another simple fix for this one also?
Thanks in advance, Mike. After the software has been fully uninstalled, restart your PC and reinstall Microsoft Visual Studio Ultimate software. When the first two steps haven't solved your issue, it might be a good idea to run Windows Update.
Many Orca. Msi error messages that are encountered can be contributed to an outdated Windows Operating System. To run Windows Update, please follow these easy steps:. If Windows Update failed to resolve the Orca. Msi error message, please proceed to next step. Please note that this final step is recommended for advanced PC users only.
If none of the previous three troubleshooting steps have resolved your issue, you can try a more aggressive approach Note: Not recommended for amateur PC users by downloading and replacing your appropriate Orca. Msi file version. Msi files for every applicable version of Microsoft Visual Studio Ultimate. Please follow the steps below to download and properly replace you file:.
If this final step has failed and you're still encountering the error, you're only remaining option is to do a clean installation of Windows Msi problems. To avoid data loss, you must be sure that you have backed-up all of your important documents, pictures, software installers, and other personal data before beginning the process. If you are not currently backing up your data, you need to do so immediately.
Msi to your appropriate Windows system directory. Microsoft typically does not release Microsoft Visual Studio Ultimate MSI files for download because they are bundled together inside of a software installer. The installer's task is to ensure that all correct verifications have been made before installing and placing Orca. An incorrectly installed MSI file may create system instability and could cause your program or operating system to stop functioning altogether.
0コメント