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
- :
- internal build error -6213 when adding .NET components
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
‎Jun 01, 2008
08:26 PM
internal build error -6213 when adding .NET components
Has anyone encountered this error? I can add native dlls to the Files view and the setup compiles fine, but as soon as I add a .NET assembly I get an internal build error.
So far, searching the support site has not been fruitful. I found a reference to this error occurring in version 10.5, and there is a patch available for that version, but so far haven't seen this issue documented for 2008 Professional.
The workaround in 10.5 is to disable .NET dependency scanning, but this workaround doesn't seem to be applicable to 2008.
Any help would be appreciated.
Bill
So far, searching the support site has not been fruitful. I found a reference to this error occurring in version 10.5, and there is a patch available for that version, but so far haven't seen this issue documented for 2008 Professional.
The workaround in 10.5 is to disable .NET dependency scanning, but this workaround doesn't seem to be applicable to 2008.
Any help would be appreciated.
Bill
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 03, 2008
04:12 PM
I was having the same problem, and had to change the ".NET Scan at Build" property of each of my .NET Components to Properties only from the Default "Dependencies and Properties"
Bill Campbell wrote:
Has anyone encountered this error? I can add native dlls to the Files view and the setup compiles fine, but as soon as I add a .NET assembly I get an internal build error.
So far, searching the support site has not been fruitful. I found a reference to this error occurring in version 10.5, and there is a patch available for that version, but so far haven't seen this issue documented for 2008 Professional.
The workaround in 10.5 is to disable .NET dependency scanning, but this workaround doesn't seem to be applicable to 2008.
Any help would be appreciated.
Bill
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 04, 2008
09:50 AM
Thanks,
Kevin, I guess changing the global setitng only applies the default to newly added components. Makes sense.
Bill
Kevin, I guess changing the global setitng only applies the default to newly added components. Makes sense.
Bill