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.
Post by this author
Hi everyone, this post is in my name but it’s authored by Sourabh Shirhatti. He was a **Program Manager Intern **from the University of Texas at Austin that I’ve had the pleasure of working with this summer. This post is long overdue,
In previous releases we have added support for scaffolding controllers/views based on project artifacts in both MVC and Web Forms projects. The technology used for those previous releases was tied to Visual Studio. With ASP.NET vNext one of our high level goals is to enable Visual Studio customers to work with non-Visual Studio users.
In Visual Studio 2013 we shipped support for creating new ASP.NET projects which use Windows Azure Active Directory for Organizational Authentication. Vittorio Bertocci has recently written a great blog post Setting Up an ASP.NET Project with Organizational Authentication Requires an Organizational Account.
In Visual Studio 2013 we introduced the Add New Scaffolded Item dialog. This dialog replaced the Add View/Add Controllers ASP.NET MVC dialog which was had in 2012. This new dialog works for all ASP.NET projects (MVC, Web Forms and Web API).
In Visual Studio 2013 we have added a couple of small features for web publishing that I’d like to share with you. Those updates are; how to take your app offline during publishing and how you can update the default file compare option.
The other day I received an email from a customer with a question which I’ve summarized as below.
I have a solution containing multiple web projects. One of the projects, _RootSite, is the top level website which I want to publish.
I’ve written a few blog posts on how to exclude files from publishing/packaging. In each of these posts you’d have to be familiar with MSBuild and the Web Publish process. I’ve been looking for a much simpler way to exclude files/folder from publishing.
Today we released an update to the Visual Studio **2013 Preview **which enables you to create ASP.NET applications which use Windows Azure Active Directory for authentication.
In this post I will describe; how you can get the additional support, where to find more info and a list of known issues.
In Visual Studio 2010 we introduced a simple and straight forward method of transforming web.config during publishing/packaging. This support is called XML Document Transform, aka XDT. It allows you to transform any XML file, not just web.config. To learn more about XDT check out the docs.