Windows 10: Announcing General Availability of New Build Editor in Visual Studio

Brink · May 10, 2017

Today we are excited to announce the general availability of a new build definition editor in Visual Studio Team Services. The new editor is also available in Team Foundation Server 2017 Update 2.

We started this exercise of refreshing the entire build editor a few months back. Besides the need to modernize our user experience, we addressed various customer pain-points in the new editor. The new editor features a more intuitive getting started experience through introduction of new features such as process parameters. Common actions such as finding and adding tasks, using templates, or setting configuration options are easier in the new experience.

What’s New in the new build editor?

Get started with the template of your choice. You can search for one of the out-of-the-box or customized templates and choose ‘Apply’, or simply choose ‘empty template’ to get started.

Working with tasks is now a breeze. You can now search for tasks and add them to a specified location (indicated by the blue line) by using the ‘Add’ button or you can directly drag and drop them to your desired location. You can also reorder tasks in the build definition by using drag and drop or clone them using Ctrl + drag and drop.

Getting started made easy with ‘Process parameters’. When you start with one of the out-of-the-box templates, the most important fields across all tasks in the template are already (pre-defined) bubbled up to a single view called “Process”. Provide the values for these process parameters to immediately get started.

Alternatively, you can bubble up all the important fields across tasks in any of your build definitions to the “Process view” as process parameters. You can also link multiple fields across tasks to create one parameter, thus avoiding entering the same value at multiple places. Process parameters help you quickly make changes to all the important fields and create a build without needing to click through each of the tasks or filling the same value multiple times.

Improved task input forms. Tasks inputs now have a legible and clutter free UX

For a complete walk-through of creating your first build definition using the new editor, see CI/CD for newbies. For various examples on how to build your applications using VSTS and TFS, see Build your app.

Got feedback?

How can we make the new Build editor better for you? Here is how you can get in touch with us

Suggest a feature on User voice

Report an issue on Developer community.

Send me an L: email.

Click to expand...

Source: Announcing General Availability of the New Build Editor | Microsoft Application Lifecycle Management

:)

FStallings · May 10, 2017

VS 2015 - Disable "PowerShell Tools for Visual Studio are available" prompt

Every time I open a .ps1 file in Visual Studio 2015 it tells me "PowerShell Tools for Visual Studio are available" in an annoying yellow bar that pops up wanting me to install these tools.

I don't want to install these tools, I use a separate editor for PowerShell that I'm quite happy with.

All I'm using Visual Studio for is analyzing changes before checking things into TFS.

How can I make this prompt go away? I'm about to just go back to using Visual Studio 2012.

Thanks,

- FS

franx_dj · May 10, 2017

Clickonce cause Visual Studio hangs on Windows 10

Hi,

Visual Studio 2015 on Windows 10 Enterprise hangs frequently when the project is using Clickonce technology.

There is no apparent causes for the hangs, because the hangs occurs even when Visual Sudio is simply opened, but I'm not working with it.

Other times, the hangs can occurs when I'm digiting on the editor.

When an hangs occurs, simply the visual studio process is not responding and I must kill it and restart.

Often, otherwise, the hangs occurs when launch the debugger: in that cases, the IDE is responsive, bug the builds is still on starting build. If I try to do anything, VS ask if I want to stop the debugger, but, if I click yes, the debugger does not stops.

Even in that cases, I must kill Visual Studio.

I'm using Visual Studio 2015 Enterprise, but the same problems occurs with other versions (VS 2010, VS 2012, VS 2012).

My collegues have same problems with same configuration:

Visual Studio,

Windows 10,

projects with Clickonce

With Windwos 8 or previous no problems occurs.

Had anyone same problems?

Thanks,

Francesco

Windows 10: Announcing General Availability of New Build Editor in Visual Studio

Announcing General Availability of New Build Editor in Visual Studio

Announcing General Availability of New Build Editor in Visual Studio

Announcing General Availability of New Build Editor in Visual Studio - Similar Threads - Announcing General Availability

Visual Studio 2019 version 16.2 Generally Available and 16.3 Preview 1

Announcing general availability of Visual Studio IntelliCode

Visual Studio 2019 now generally available

Microsoft announces availability of Visual Studio 2019 Preview 1

Microsoft Announces Visual Studio 2019

Announcing Azure DNS General Availability

Announcing general availability of Upgrade Readiness

Announcing Visual Studio Connected Environment

Announcing the .NET Framework 4.7 General Availability