InstallShield 2010 .isproj files have incorrect target import path

[jasonmorse]

When I create new InstallShield 2010 setup projects from within Visual Studio (File -> New -> Project) the resulting project's .isproj file has target import path for InstallShield 2009 instead of 2010. This prevents building these projects through MSBuild.

I manually worked around this problem by hand modifying the generated file.

Incorrect:

	...
	

Correct:

	...
	

I was using Visual Studio 2008 (Team System Development Edition) with InstallShield 2010 Premier Edition with Virtualization Pack.

[MichaelU]

Thanks, for mentioning this; we are aware of it. If you create a lot of new projects and want to work around this more permanently, you can edit the template at \Support\0409\msbuild.xml to apply the same change there.

[jasonmorse]

Somewhat related, the InstallShield 2010 Standalone install puts the InstallShield.targets file in 2009 directory instead of 2010.

C:\Program Files (x86)\MSBuild\InstallShield\2009\InstallShield.targets
C:\Program Files (x86)\MSBuild\InstallShield\2010\InstallShield.Tasks.dll