In Visual Studio 2019 Preview 2, The Web Tools team made some changes to improve extensibility features for extension developers. To standardize interfaces, the CSS, HTML, JSON and CSHTML editors renamed their assemblies - table details inside!
Some people say ‘friends don’t let friends right click publish’ but is that true? If they mean that there are great benefits to setting up a CI/CD workflow, that’s true and we will talk more about these benefits in just a minute.
We are working to improve the experience for ASP.NET Core developers in Visual Studio for Mac. If you are working on ASP.NET Core apps in Visual Studio for Mac, we would love to hear you feedback. Your feedback is important so that we can help shape the future of ASP.NET Core in Visual Studio for Mac.
Microsoft Library Manager (LibMan) is now available in the general release of Visual Studio 2017 as of v15.8. LibMan first previewed earlier this year, and now, after a much-anticipated wait, LibMan is available in the stable release of Visual Studio 2017 bundled as a default component in the ASP.NET and web development workload.
With the release of Visual Studio 2017 version 15.8 brings improvements for web developers such as custom docker image tags during publish, zip push deployment for Azure functions, managing Azure functions application settings, and enabling Application Insights as part of publishing to Azure App Service. Also learn about managing user secrets in ASP.NET framework projects, optimizing build performance for solutions containing ASP.NET frame as well as author and source information for ASP.NET Core templates.
Recent releases of Visual Studio 2017 focus greatly on improving the experience of working with Razor. The improvements address the most pressing customer-facing issues like formatting changes and providing general performance and reliability for IntelliSense. Now that the fixes and enhancements are publicly available, we would like to learn more about your experience with the Razor editor.
As of June 25, the version of Bower shipped with Visual Studio was deprecated, resulting in Bower operations failing when run in Visual Studio. If you use Bower, you will see an error something like:
EINVRES Request to https://bower.herokuapp.com/packages/bootstrap failed with 502
This will be fixed in Visual Studio 15.8.
Provider pattern was introduced in ASP.NET 2.0 and it gives the developers the flexibility of where to store the state of ASP.NET features (e.g. Session State, Membership, Output Cache etc.). In ASP.NET 4.6.2, we added async support for Session State Provider and Output Cache Provider.
We’re excited to announce several improvements to the Azure Functions experience in Visual Studio as part of the latest update to the Azure Functions tools on top of Visual Studio 2017 v15.5.
New Function project dialog, including storage account support
.NET Core support
Manage Azure app settings
Detect mismatching functions runtime versions
New Function project dialog
To make it easier to get up and running with Azure Functions,
The ASP.NET team is proud to announce general availability of ASP.NET Core 2.0. This release features compatibility with .NET Core 2.0, tooling support in Visual Studio 2017 version 15.3, and the new Razor Pages user-interface design paradigm. For a full list of updates,