Hi,
We are working with InstallShield and Visual Studio 2010 and have InstallShield licences for 2 developers and 2 standalone build servers.
There will be more developers working on the project but will not be concerned with setup projects.
At the moment any developer who does not have InstallShield installed and opens a solution in Visual Studio containing a setup project will receive an error and the InstallShield project will not load and will be shown as unavailable.
Is this something other development teams have encountered and resolved?
How can we organise our solution to accommodate this without purchasing extra InstallShield licences for developers who are not involved in the development of setup projects?
Simply leaving the project as unavailable in Visual Studio does not feel like the right thing to do.
Regards
Matt
We are working with InstallShield and Visual Studio 2010 and have InstallShield licences for 2 developers and 2 standalone build servers.
There will be more developers working on the project but will not be concerned with setup projects.
At the moment any developer who does not have InstallShield installed and opens a solution in Visual Studio containing a setup project will receive an error and the InstallShield project will not load and will be shown as unavailable.
Is this something other development teams have encountered and resolved?
How can we organise our solution to accommodate this without purchasing extra InstallShield licences for developers who are not involved in the development of setup projects?
Simply leaving the project as unavailable in Visual Studio does not feel like the right thing to do.
Regards
Matt