See GitHub Issue #795 for the details and discussion. One of the undocumented changes of converting from project.json to csproj, was the <DocumentationFile> no longer automatically copied to the output folder during the build or publish process. There have been multiple solutions, both pre and post publish scripts. However, understanding how MSBUILD works and finding the simplest way is key. Thanks to Eric Erhardt's latest comment here I think that this is the cleanest way. Add the following snippet to the .csproj to enable the copy of the documentation file to the output folder. It supports the F5 options as well as the dotnet build / dotnet publish CLI commands. Another important option tested was the ability to...

Taking on a new role as a Sr. Cloud Developer Advocate withing the Cloud and Enterprise group. What does that mean? Talking to the community about the technologies that I love; ASP.NET, ASP.NET Core, Docker, services and how these can best be run on Azure and what we as a community can do to make it better. docs.microsoft.com, where I have spent my time since joining Microsoft, is a very important part of what we are moving to accomplish. With a new look at documentation for all of the products; Azure, ASP.NET/ASP.NET Core, Visual Studio and many more products continue to migrate over to the new Open Source platform. I will continue to...

Visual Studio 2017 has been released and the features are great for Windows developers. However along with it comes .NET Core 1.0 tooling and large improvements to the command line experience for macOS and Linux users developing ASP.NET Core applications. One of the prevalent features shown off in VS 2017 is the Docker support and capabilities to push to Azure App Service. Using the Azure CLI 2.0, Docker and .NET CLI these same capabilities can be accomplished without friction and with just as much success and satisfaction. dotnet new The new command now is driven by a whole new template system. A number of new templates, including webapi, are available with the ability to install and create...

The decisions around what to use for packaging client side libraries is still a length discussion. Mostly, if not always, will start and stop with "It Depends...". However, getting started with something and being able to build upon that is a good starting point rather than what some call "Paralysis through analysis". Bundler & Minifier When this component was originally available, only Visual Studio 2015 / 2017 users could take advantage through the use of an extension (VSIX) or you could use dotnet bundle by adding a dotnet tools CLI package to your project. Now, in the recent update, the NuGet package fully integrates with MSBuild and you can take advantage of using the bundling and minify capabilities as a part...

When you create a web API, documenting its capabilities for the consuming developers can be a task if you take it on manually. Swagger gives you the ability as the API developer to add self-documenting helper pages and test harnesses to your API. Recently John and I took some time away to discuss how to use Swagger to document a Web API written in ASP.NET Core using Swashbuckle and Visual Studio for the Mac Here is the result of that conversation. Check out the Play by Play on Pluralsight Resources docs.microsoft.com : ASP.NET Web API Help Pages using Swagger Swashbuckle GitHub repository Visual Studio for the Mac...