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: issue opening a project in InstalliShield
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
‎Apr 16, 2013
04:53 PM
issue opening a project in InstalliShield
Hi,
Sorry if this has already been asked, but I cant find an answer to this anywhere.
I have 2 development computers (VS 2012), I added setup.isl and Setup.isproj to version control(svn), the files are under the setup project for the solution,
When I open the project in the machine where I originally did the development everything works fine, when I need to open the same project in the new machine (that doesnt contain any other files from install) I get an error saying: InstallShield cannot open %FILE%.isl. Please contact Flexera Software technical support". the file is there it just cant be opened.
I cannot figure out what the difference is, so to the questions are:
1.- what files do I need to add to svn to ensure that the development project works across both my development enviroments.
2.- How can I fix this on the second development machine?
Thanks,
Sorry if this has already been asked, but I cant find an answer to this anywhere.
I have 2 development computers (VS 2012), I added setup.isl and Setup.isproj to version control(svn), the files are under the setup project for the solution,
When I open the project in the machine where I originally did the development everything works fine, when I need to open the same project in the new machine (that doesnt contain any other files from install) I get an error saying: InstallShield cannot open %FILE%.isl. Please contact Flexera Software technical support". the file is there it just cant be opened.
I cannot figure out what the difference is, so to the questions are:
1.- what files do I need to add to svn to ensure that the development project works across both my development enviroments.
2.- How can I fix this on the second development machine?
Thanks,
- Tags:
- installshield
- vs 2012
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 18, 2013
09:36 AM
Hello,
Here are the answers for the questions posted:
1>
You can add the following files to Visual Studio source control:
* Solution files (*.sln).
* Project files, for example, *.csproj, *.vbproj files.
* Application configuration files, based on XML, used to control run-time behavior of a Visual Studio project.
Files that you cannot add to source control include the following:
* Solution user option files (*.suo).
* Project user option files, for example, *.csproj.user, *.vbproj.user files.
* Web information files, for example, *.csproj.webinfo, *.vbproj.webinfo, that control the virtual root location of a Web project.
* Build output files, for example, *.dll and *.exe files.
2> Please refer the below community link to fix the issue:
http://community.flexerasoftware.com/showthread.php?190268-Project-file-corrupted!
Thanks,
Chiranjeevi
Here are the answers for the questions posted:
1>
You can add the following files to Visual Studio source control:
* Solution files (*.sln).
* Project files, for example, *.csproj, *.vbproj files.
* Application configuration files, based on XML, used to control run-time behavior of a Visual Studio project.
Files that you cannot add to source control include the following:
* Solution user option files (*.suo).
* Project user option files, for example, *.csproj.user, *.vbproj.user files.
* Web information files, for example, *.csproj.webinfo, *.vbproj.webinfo, that control the virtual root location of a Web project.
* Build output files, for example, *.dll and *.exe files.
2> Please refer the below community link to fix the issue:
http://community.flexerasoftware.com/showthread.php?190268-Project-file-corrupted!
Thanks,
Chiranjeevi
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 18, 2013
04:49 PM
chiranjeevi wrote:
Hello,
Here are the answers for the questions posted:
1>
You can add the following files to Visual Studio source control:
* Solution files (*.sln).
* Project files, for example, *.csproj, *.vbproj files.
* Application configuration files, based on XML, used to control run-time behavior of a Visual Studio project.
Files that you cannot add to source control include the following:
* Solution user option files (*.suo).
* Project user option files, for example, *.csproj.user, *.vbproj.user files.
* Web information files, for example, *.csproj.webinfo, *.vbproj.webinfo, that control the virtual root location of a Web project.
* Build output files, for example, *.dll and *.exe files.
2> Please refer the below community link to fix the issue:
http://community.flexerasoftware.com/showthread.php?190268-Project-file-corrupted!
Thanks,
Chiranjeevi
Hi Chiranjeevi,
Thanks for the response, I tried the link to the solution you shared and I get a different message saying "Class not registered" instead of the unsupported type described on the post.
Any ideas? I have copied the original and working file from my other computer and pasted the contents on the new one with no luck, any other suggestions?
Thanks,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 22, 2013
02:25 AM
Hello,
Could you please try renaming .isl file to .ism or .ise to open using Installshield Authoring Tool.
Thanks,
Chiranjeevi
Could you please try renaming .isl file to .ism or .ise to open using Installshield Authoring Tool.
Thanks,
Chiranjeevi
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 01, 2013
11:05 PM
chiranjeevi wrote:
Hello,
Could you please try renaming .isl file to .ism or .ise to open using Installshield Authoring Tool.
Thanks,
Chiranjeevi
Hi Chiranjeevi,
I tried this with no luck, I got another system and everything works fine in there. So it looks like InstallShield was not installed correctly, I will remove and reinstall to get this working.
Thanks for your help,