This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: ISDEV : fatal error -6652
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 09, 2007
06:11 AM
ISDEV : fatal error -6652
Hello
anytime a new relaese is present, nothing works!! Have you got an Q&A Team?
OK, when you set a .NET Assembly '.NET Installer class= yes' you get an error: "ISDEV : fatal error -6652: The file _isconfig.xml can not created to use with InstallUtilLib.dll."
Yes, the Installer class will run correctly with installutil.exe.
Yes, the RunInstaller Attribute is set to 'true'
Resolve this Error shortly.
anytime a new relaese is present, nothing works!! Have you got an Q&A Team?
OK, when you set a .NET Assembly '.NET Installer class= yes' you get an error: "ISDEV : fatal error -6652: The file _isconfig.xml can not created to use with InstallUtilLib.dll."
Yes, the Installer class will run correctly with installutil.exe.
Yes, the RunInstaller Attribute is set to 'true'
Resolve this Error shortly.
2 Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 10, 2007
10:37 AM
We've started to see a couple reports of this, but haven't been able to fully diagnose it yet. Are you building in a folder that's controlled by source control, or otherwise have a read-only project folder? If there's already an _isconfig.xml file in that folder, could you rename it and if so does that resolve the behavior?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 10, 2007
11:51 AM
While it's useful to resolve this problem, you might want to also consider not using Installer class custom actions and instead use the CoCreateObjectDotNet() InstallScript function to consume a ComVisible(true) class. This pattern is much more reliable and provides a much more meaningful way of passing data to and from the custom action.
