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: Error 6212 On Build of Imported VS 2010 project
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
Dec 18, 2013
02:25 PM
Error 6212 On Build of Imported VS 2010 project
We've recently decided to look into a move to VS 2013 from VS 2010 and have discovered the missing Setup & Deployment Projects within VS. So we went about attempting to import one of our existing Setup projects from VS 2010. Although we were able to import the project, we ran into a few issues.
First, the build indicated an error with a prerequisite of .Net 2.0 and an inability to find the necessary files. The error text stated we should remove the reference from the project, yet the only reference we could find was in the project file. When we removed that reference manually, then rebuilt the setup project, that error disappeared but we then received an error "Internal build error 6212".
Since that time, we've been unable to resolve the error and our setup project will not build and I can find no resolution on the web.
Help!
- Jim
First, the build indicated an error with a prerequisite of .Net 2.0 and an inability to find the necessary files. The error text stated we should remove the reference from the project, yet the only reference we could find was in the project file. When we removed that reference manually, then rebuilt the setup project, that error disappeared but we then received an error "Internal build error 6212".
Since that time, we've been unable to resolve the error and our setup project will not build and I can find no resolution on the web.
Help!
- Jim
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 20, 2013
08:23 AM
Hi Jim,
There might be some dependencies missing after the setup project was upgraded to newer version.
Kindly right-click the solution, open project dependencies dialog and check all that which is missing from the current setup.
Please let me know if this did not help.
Thanks,
Chaitra
There might be some dependencies missing after the setup project was upgraded to newer version.
Kindly right-click the solution, open project dependencies dialog and check all that which is missing from the current setup.
Please let me know if this did not help.
Thanks,
Chaitra