Skip to main content

Newsflash: Visual Studio Lab Management Announcement

Microsoft announced today that the final release of the Lab Management functionality in Visual Studio 2010 will be available at the end of August. Important to notice is that Lab Management no longer requires a separate license. Instead Lab Management will be available for existing or new Visual Studio 2010 Ultimate with MSDN and Visual Studio Test Professional 2010 with MSDN customers. Because of this change, Lab Management will no longer require a per-processor license. These two subscriptions include all pre-requisite software for Lab Management – including Team Foundation Server 2010 (purchase of a separate Windows Server license is required), System Center Virtual Machine Manager (SCVMM) 2008 R2, and Visual Studio Agents 2010 and Microsoft Test Manager 2010. Of these products, Agents and Test Manager can be installed from either 2010 Ultimate or Test Professional 2010.

I hope that this big change in licensing will help customers adopting this product. If you want to try it, just have a look at all information here and download a trial of Lab Management here.

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