Skip to main content

Adding reports and dashboards to upgraded Team Projects

So you are done upgrading your Team Foundation Server from 2005 or 2008 to 2010. Now what?

Maybe it’s a good idea to start provisioning your upgraded team projects by using the new dashboards and reports that are provided with version 5.0 of the Microsoft Solutions Framework (MSF) process templates. You can also add dashboards or reports to an existing team project when resources for SharePoint Products or SQL Server Reporting Services become available.

To provision your upgraded team project , you can create a batch file and run it from the Visual Studio command window. The batch file command provisions features in the same way that the New Team Project Wizard provisions features. When you run the batch file to add dashboards and Excel reports, the command uploads all documents that are provided with the process template that you specify and provisions the dashboards and Excel reports. The command also activates the SharePoint site and dashboard features that are specified in the process template.

Of course you don’t have to create this batch file yourself,  on the MSDN site a very good description is available about how to configure and run this batch script:

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