Note that this version is for Visual Studio 2017 RC 3 and later.Įxtensions that, uh. You can automate build and deployment tasks, get desktop notifications from Visual Studio Team Services, and more. Specifically, these tools are focused on continuous build integration and deployment for ASP.NET and other projects targeting Microsoft Azure. Once your code is built and tested, you'll need Continuous Delivery Tools for Visual Studio from Microsoft DevLabs.
If you're using Squirrel as an installation and update framework for your Windows-based desktop applications, Chris Pulman's VS.Squirrel integrates the ability to add the Squirrel packages to your project, rebuild and even deploy the installer from within Visual Studio 2015 or 2017. No more clicking around Windows Explorer. OpenBinFolder, by Eli Berezovsky, gives you a one-click menu item to open the \bin folder to access the compiled binary for your project. for license details, documentation, and details on becoming a beta tester. 90-day trial versions are available, as well as licenses for support and upgrades. Error Unit currently includes compatibility libraries for SimpleInject, PostSharp, Autofac, log4net and Elmah, and more are under development. Plus, it's compatible with Visual Studio 2012, 2013, 20.ĮrrorUnit for Visual Studio 2015 and ErrorUnit for Visual Studio 2017, by John Gold, are extensions to help debug C# applications, enabling errors that you encounter to generate MSTest, xUnit or NUnit unit tests. With ITweakMyBuild you can interact directly with MSBuild, locally overriding any property on-the-fly to turn on or off features that may slow down or provide unhelpful messages during a build. ITweakMyBuild, by Tom Englert, lets you change global build parameters on the fly without having to set up or change a solution configuration.
Last time, we looked at a dozen extensions, and we continue with build, test, and shipping tools.
0 kommentar(er)
