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
- :
- Crashing VS2010
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
‎Nov 02, 2011
12:29 PM
Crashing VS2010
I have VS2010 SP1 and the "InstallShield 2011 Limited Edition". I created a default winforms project and tried adding it's primary output to the setup project. Subsequent attempts to build the setup project cause VS2010 to crash.
After spending some time debugging, I see this:
Unhandled exception at 0x00200073 in devenv.exe: 0xC0000005: Access violation.
Is anyone else having problems with InstallShield making VS2010 unstable?
What do I need to do to troubleshoot?
Thanks
After spending some time debugging, I see this:
Unhandled exception at 0x00200073 in devenv.exe: 0xC0000005: Access violation.
Is anyone else having problems with InstallShield making VS2010 unstable?
What do I need to do to troubleshoot?
Thanks
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 03, 2011
10:38 AM
Hello Dbeavon,
Could you kindly let me know whether you have installed Microsoft Visual Studio 2010 SP1?
Thanks,
Bharath
Could you kindly let me know whether you have installed Microsoft Visual Studio 2010 SP1?
Thanks,
Bharath
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 03, 2011
12:43 PM
I have SP 1. It seems like this stuff crashes quite reliably. It seems like the default error handling mechanism. Is there an output log that I can look at to get the related details for these crashes?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 03, 2011
03:02 PM
Somehow reordering the project lists seems to fix my crashing. Move the primary output project to the top of the sln:
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") ...
EndProject
Now I get another error instead
"ISEXP : error : -6213: Internal build error"
I'll be amazed if I ever get this stuff working.
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") ...
EndProject
Now I get another error instead
"ISEXP : error : -6213: Internal build error"
I'll be amazed if I ever get this stuff working.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 04, 2011
10:50 AM
Hello Dbeavon,
Build time Error 6213 is related to .NET Dependency Scanning. Could you kindly navigate to InstallShield LE Menu –> Options –> .NET ta and change the value of Define .NET Scan At Build Time Setting –> None.
Thanks,
Bharath
Build time Error 6213 is related to .NET Dependency Scanning. Could you kindly navigate to InstallShield LE Menu –> Options –> .NET ta and change the value of Define .NET Scan At Build Time Setting –> None.
Thanks,
Bharath