TFS SDL 2010 & 2013 but what about 2012? - sdlc

I see there is a TFS template incorporating SDL (security development lifecycle) for 2013 (http://www.microsoft.com/en-us/download/details.aspx?id=42517) but it does not mention anything about TFS2012.
Does anyone know if it is compatible with TFS2012 or if there is an SDL template for 2012? (I don't want to install the 2013 version, only for it to break our TFS2012!)

I downloaded the MSI and took a quick look with Orca. From what I saw, the installer checks explicitly for TFS 2013 and and install an additional Web Service, that, I suppose interacts server-side and, therefore, is version specific.
So your only chance is to upgrade, which, from my experience is not that hard, if you do your homework.

Related

Installer creation tool - is this still a thing?

I'm not asking a technical question, but a request for advice.
Over time, I have always used installshield as the primary tool in installer development, and this tool has always been the king of them.
Lately, everything has gone to the web and Windows Forms have lost their charm. However, these still exist, and there are needs about them.
But you don't see anyone talking about the latest technologies about Windows Forms, installers...
Do you think Installshield is still the main tool for build installers? Why isn't any extension available in the VSTS/TFS vNext market?
Even in Jenkins, the last time the plugin was updated ... was in 2014. And we remember that Microsoft used Installshield Limited edition for one Visual Studio Version, but dropped to bring back Visual Studio Installer.

Where can I find additional TFS 2010 Process Guidance templates?

Does anyone know where I can find any process guidance templates for TFS 2010 other than the two provided by default?
The Project creation wizard also has a link to download more Microsoft certified process templates, link which points to this page: http://msdn.microsoft.com/en-us/vstudio/aa718795.aspx. Make sure you keep an eye on that site as new templates will be posted there.
Thanks, Ladislau
Version 3 of the Scrum for Team System template (currenlty a release candidate at time of writing) is available. Info and download locations are available at http://scrumforteamsystem.com/cs/forums/14/ShowForum.aspx
I'm not sure where some of the older 2008 templates on codeplex are up to in terms of providing 2010 versions. I'd suggest going to codeplex and searching for TFS and template and seeing what you find.

Spark view engine - why there is no VS integration in version 1.1?

I downloaded Spark 1.1 release from http://sparkviewengine.codeplex.com/releases/view/27601 and cannot find the msi package for Visual Studio integration promised in docs.
Can anyone explain why?
For VS2008 support, I'm not sure why it's not included in the latest downloads on codeplex, but you can still get the .msi from the download on spark downloads page.
For VS2010, the answer is a little bit more complicated. The short version though is that the visual studio editor changed drastically in VS2010 and the way the old plug-in was providing intellisence is no longer appropriate.
I was able to get the msi installed and working from 1.0.39935.0 with 1.1. I had to close and re-open VS and a few pages.

Extend Visual Studio Team System 2010 SSC

I'm looking to extend the source control of Visual Studio 2010 Team System. I need to halt the check-in process and pop-up a little GUI to do some things. I've found this; http://msdn.microsoft.com/en-us/library/ms182075(VS.100).aspx, does anybody have any good tutorials or similar lying around i'd appreciate it.
Your best bet is a check-in policy. If you download and install the latest VS 2008 SDK, you can re-compile the check-in sample in VS 2010 after fixing up the assembly references. We'll be publishing update SDK samples when Beta 2 is released.

Basic Team Explorer usage questions

We are setting up a new TFS 2008 implementation as our first usage of TFS for source control. We have several projects in Visual Studio 2003, 2005 and 2008, as well as other script/non-Visual Studio based projects.
My question is, for the Visual Studio 2003 and 2005 projects do we have to install Team Explorer 2003/2005 and make use of them to add projects to source control and to check out/in files, or, can we just use Team Explorer 2008 to add projects and check in/out files? The thought being that the developer could use 2008 to check out any thing and then open the appropriate visual studio version to work on their local instance of the project before then checking it back in using team explorer 2008 within their local visual studio 2008 application.
The concern is that by using team explorer 2008, that visual studio 2008 might impose changes on the older systems solutions dll or control details.
Thanks for any guidance.
This is possible. I have colleagues who are using Team Explorer for non-code files (Word documents, help files, etc.) and use it like they would VSS or any other SCC.
As an added bonus, I'm pretty sure that TFS Server 2008 is backwards compatible to at least 2005 (haven't run against 2003 in awhile). IIRC, I've run VSTS 2005 For Developers against a 2008 TFS Server.
I would double-check for you, but I've recently recently re-imaged my dev machine and haven't re-installed 2005 (working on new stuff!).
As an aside, I've found TFS to be a huge timesaver as far as the whole dev process. The IDE integration is top notch, and the linked bug/task tracking and changesets, with alerts, notes, built-in queries and reports had me wondering how I ever got along w/o it.
HTH.
The Team Foundation Client for VS 2005 and VS 2008 can be installed side by side so there's no issue there (there isn't one for VS 2003, but you could probably use the MSSCCI provider).
You can however, if you want to, do all of your source control operations in VS 2008 (or the Windows Explorer extensions in the latest power tools) but work on the projects from VS 2003/2005 without any issues. You just need to make sure you don't accidentally open the project files from within VS 2008 because that will upgrade the project format.

Resources