Skip to main content

Team Explorer Everywhere 2010 SP1 Beta available

If you are a non-.NET developer and you are using Team Explorer Everywhere today or you are still hesitating to start using it, don’t wait any longer. With the upcoming release of Team Explorer Everywhere SP1, a long list of new features and improvements are added.

If you can not wait, just go the following link and download the latest bits: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=4449babd-1dc8-40e3-9e27-2b743a4a173c&displaylang=en. If you first want to learn about these new features, continue reading.

Gated Check-in Support

With SP1 Eclipse developers finally get the full experience of gated check-ins. When you check-in code affected by a gated build definition you get a prompt as to what you would like to do. Assuming you request a gated build, the changes will be shelved and a build submitted on your behalf.  When the build completes you will be notified right inside of Eclipse.

Private / Buddy Builds

Another new feature in the build space is the ability to create private builds from Eclipse.    If you want to perform a build on the build server then you can manually queue a build passing in a shelveset. That way you can validate your changes work on the build server before checking them in.

Rich Editing of Work Item Descriptions

In the new process templates that ship with TFS 2010 you can use HTML fields to provide a rich text field to enter information about that work item.  These are used extensively by the Microsoft Test Manager tool to help a tester create a bug with a nicely formatted repro steps.  In SP1 a rich HTML editing control for editing work items in Eclipse 3.5 is available. For developers using older versions of Eclipse we fall back to the HTML editing control that we shipped in original version.

Work Item Custom Controls

TFS has custom control support for work items both for Visual Studio and the web access. With Team Explorer Everywhere SP1 an improved experience is given to create custom controls for Eclipse. 

Internal Merge Support in Eclipse

In previous version of the Eclipse plug-in you were required to use an external tool to resolve merge conflicts.  Microsoft fixed this to properly support the internal merge tool if available in Eclipse including support for 3-way merging. 

And I even forgot to mention a lot of other new features, like localization, improved build results, and so on.

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