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: Integrating with Team Foundation Server?
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
‎Feb 13, 2009
11:52 AM
Integrating with Team Foundation Server?
I have Microsoft Visual Studio 2005 installed on my machine, connecting to Team Foundation Server on another machine. I have Installshield 2009 Professional installed on my machine and I would like to use TFS as my source control. In the options window all of the options on the Source Control tab are greyed out.
How do I get Installshield to connect to my TFS? Is it possible?
Thanks
Paul
How do I get Installshield to connect to my TFS? Is it possible?
Thanks
Paul
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 14, 2009
09:08 PM
While InstallShield has really nice MSBUILD support ( Teambuild with InstallShield rocks ), InstallShield's SCC integration is buggy and sucks.
What I suggest is create the .sln and .isproj files to get the msbuild integration but don't use SCC integration. Use Team Explorer to check the ISM out and then switch over to windows explorer ( Team Explorer 2008 SP1 makes it easy with a hyperlink to your workspace directory ) and open the ISM up in InstallShield directly. When done switch back to team explorer and check the file in then kick off your build definition.
BTW, you'll find IS/TFS related content on my blog.
What I suggest is create the .sln and .isproj files to get the msbuild integration but don't use SCC integration. Use Team Explorer to check the ISM out and then switch over to windows explorer ( Team Explorer 2008 SP1 makes it easy with a hyperlink to your workspace directory ) and open the ISM up in InstallShield directly. When done switch back to team explorer and check the file in then kick off your build definition.
BTW, you'll find IS/TFS related content on my blog.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 28, 2010
08:30 AM
Sorry to revive an old thread but I'm curious if your suggestion still holds true today with the newest versions of Installshield and TFS?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 28, 2010
09:01 AM
I haven't tried it recently but I doubt it's any better knowing InstallShield's track record for fixing bugs.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 29, 2010
11:38 AM
I use VisualStudio 2008 and InstallShield 2009 and continue using Source Control Explorer to perform checkin/checkout operations for my .ism files.
I've gotten used to it and works quite well.
Regards,
Juan Carlos
I've gotten used to it and works quite well.
Regards,
Juan Carlos