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: Migrating a Limited Edition 2013 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
‎Sep 01, 2015
08:48 PM
Migrating a Limited Edition 2013 project?
I had a limited edition setup project which executed from my solution in Visual Studio 2013.
I've upgraded to Visual Studio 2013, and installed Installshield Express 2015.
I can create an Express 2015 setup project from within my Visual Studio 2013 project.
But what I want it to use the existing installshield 2013 limited edition install project, migrated as necessary.
Visual Studio 2015 says the project is incompatible.
What to do?
I've upgraded to Visual Studio 2013, and installed Installshield Express 2015.
I can create an Express 2015 setup project from within my Visual Studio 2013 project.
But what I want it to use the existing installshield 2013 limited edition install project, migrated as necessary.
Visual Studio 2015 says the project is incompatible.
What to do?
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 01, 2015
09:08 PM
I did migrate the .lsl file to a .lse file, using the InstallShield standalone UI, and that worked (according to InstallShield messages)
But VS 2015 still says the project is incompatible.
But VS 2015 still says the project is incompatible.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 01, 2015
11:17 PM
I got a Installshield project based on my existing project recognised by VS 2015, by creating a new one, then copying my migrated .ise file into it.
Installshield gives a cryptic error (see further below) when running it though.
At least I have my .ise running in the standalone Installshield product.
To get this working, I had to change usages of "Content Files" and "Primary Output" to explicit references to relevant files.
Then I had to replace usages of with a hardcoded path (since there's no way to define what that means to the standalone Installshield product?).
What a pain. But at least I can now create an installer!
Building the Installshield project in VS still fails with the cryptic and decidedly unhelpful Installshield error:
ISEXP : error : -6213: Internal build error
Express\SingleImage - 1 error(s), 0 warning(s)
Installshield gives a cryptic error (see further below) when running it though.
At least I have my .ise running in the standalone Installshield product.
To get this working, I had to change usages of "Content Files" and "Primary Output" to explicit references to relevant files.
Then I had to replace usages of
What a pain. But at least I can now create an installer!
Building the Installshield project in VS still fails with the cryptic and decidedly unhelpful Installshield error:
ISEXP : error : -6213: Internal build error
Express\SingleImage - 1 error(s), 0 warning(s)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 30, 2015
07:13 AM
jharrop wrote:
I had a limited edition setup project which executed from my solution in Visual Studio 2013.
I've upgraded to Visual Studio 2013, and installed Installshield Express 2015.
I can create an Express 2015 setup project from within my Visual Studio 2013 project.
But what I want it to use the existing installshield 2013 limited edition install project, migrated as necessary.
Visual Studio 2015 says the project is incompatible.
What to do?
The only way I was able to get around this was by removing the old Setup project and creating a new one from scratch. Take screenshots of all of your settings if you are able to or use a previous version of InstallShield that is compatible so you can get the screenshots. I happen to have 2 PCs and my other PC had the older version on it so I was able to take screenshots and then create a new InstallShield project from scratch and it worked.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)