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
- :
- Not SP1
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
‎Sep 08, 2011
03:26 PM
.NET Runtime version 2.0.50727.5446 - Fatal Execution Engine Error
Ok.... I am kinda new to Visual Studio and your product "InstallShield 2011 limited Edition for Visual Studio 2010." I am getting the following error: " Microsoft Visual Studio has encountered and error and needs to close." When I go to the Windows event viewer i find the following error:
.NET Runtime version 2.0.50727.5446 - Fatal Execution Engine Error (5F47AECA) (0)
Here are the steps that I am taking to get there.
1. Create a simple Windows Forms application and save (.NET Framework 3.5). Don't have to add anything to the form.
2. File / Add / New project
Other Project types / Setup and Deployment / InstallShield LE
3. Follow the Project Assistant through the steps.
4. Build / Build Solution
5. Close and reload / select Form1.vb [Design] tab / Double-click on form
6. Crash.
7. Re-open project / Right-click on "Setup1" in Solution Explorer window and select remove.
8 now I can open form and view VB code.
I am expecting to be able to access and edit the code with the Installshield part of the project remains installed. Do I have to remove this everytime in roder to continue editing my application? Am I doing something wrong?
Thanks for your help and advice....
dc
UPDATE: I tried the HOTFIX listed in this forum, but still have the problem. Looks like many other people have this problem and have not found a solution.
dc
.NET Runtime version 2.0.50727.5446 - Fatal Execution Engine Error (5F47AECA) (0)
Here are the steps that I am taking to get there.
1. Create a simple Windows Forms application and save (.NET Framework 3.5). Don't have to add anything to the form.
2. File / Add / New project
Other Project types / Setup and Deployment / InstallShield LE
3. Follow the Project Assistant through the steps.
4. Build / Build Solution
5. Close and reload / select Form1.vb [Design] tab / Double-click on form
6. Crash.
7. Re-open project / Right-click on "Setup1" in Solution Explorer window and select remove.
8 now I can open form and view VB code.
I am expecting to be able to access and edit the code with the Installshield part of the project remains installed. Do I have to remove this everytime in roder to continue editing my application? Am I doing something wrong?
Thanks for your help and advice....
dc
UPDATE: I tried the HOTFIX listed in this forum, but still have the problem. Looks like many other people have this problem and have not found a solution.
dc
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 12, 2011
08:26 AM
Hello DCoulson,
I tried replicating the issue in-house but was unsuccessful.
Could you kindly let me know whether you have installed Microsoft Visual Studio 2010 SP1?
Thanks,
Bharath
I tried replicating the issue in-house but was unsuccessful.
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
‎Sep 12, 2011
10:21 AM
I don't think that the version that I have has SP1 installed.
dave
dave
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 13, 2011
11:01 AM
Hello Dave,
Could you kindly install Microsoft Visual Studio 2010 SP1 and check if the behavior persists?
Thanks,
Bharath
Could you kindly install Microsoft Visual Studio 2010 SP1 and check if the behavior persists?
Thanks,
Bharath
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 15, 2011
09:10 AM
Thank you for the note to install sp1. That seem to have fixed the problem.
Dave
Dave