Skip to main content

TFS Project Server Integration Pack Licensing

Together with Visual Studio 2010 SP1 and Team Foundation Server 2010 SP1 Microsoft also released the TFS Project Server Integration Feature Pack(what a name!). You can download the feature pack from the MSDN subscribers site.

This feature pack enables teams to work together more effectively by:

  • Providing up to date insight into portfolio execution, alignment with strategic objectives, and resource utilization of software development projects by leveraging the quantitative data stored in different systems.
  • Automating the exchange and sharing of project information across teams and improving coordination between teams using disparate methodologies, like waterfall and agile, via common data and agreed upon metrics.
  • Enabling development and project management teams to use familiar tools to collaborate and communicate project timeline and progress such as Microsoft Visual Studio, Project, and SharePoint.

As I got some questions about the licensing aspect, here is what you need to know if you want to introduce this pack in your environment:

TheFeature Pack will only be available to Visual Studio 2010 Ultimate with MSDN subscribers (go to your MSDN download center, you should find the Visual Studio Team Foundation Server 2010 and Project Server Integration Feature Pack as an available download). An organization must own at least one license of Visual Studio 2010 Ultimate with MSDN. With that one license, the software can be downloaded and installed and then all users with access to either the Project Server or the Team Foundation Server products that are integrated can benefit.

So buy one VS2010 Ultimate license with MSDN and you are good to go!

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more