Simplifying Bundling and Minification in ASP.NET Core

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...


Documenting ASP.NET Core WebAPI using Swagger

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...


Angular 2: Application Settings using the CLI Environment Option

Application wide settings can be a long conversation when starting a new application. Here are just a few questions when some of my teams started this conversation: Do we use ENV variables? What about manual bootstrap? Configuration files? Should we get them from the server? Using angular-cli & environment.ts The new angular-cli have the concept of different environments like development (dev) and production (prod). When creating a new application with the cli ng my-app and /environments folder is a part of the scaffold which contains the environment files. . ├── environment.ts ├── environment.prod.ts . . and then within the /src/app folder is and environment.ts file. Here are the contents: export const environment = { production: false }; As you might imagine, the...


Exploring the new dotnet cli

Note: At the time of this post, the dotnet cli version being used 1.0.0-rc4-004771 available from GitHub dotnet/cli repo - https://github.com/dotnet/core/blob/master/release-notes/rc4-download.md I have been a long time fan of the yeoman generator for ASP.NET Core and still I would argue that it's still the most complete project creation utility for cross platform development. With that said, the dotnet cli has really raised the bar for command line parity development tooling when comparing similar capabilities from other languages or frameworks where CLI is the first tool. Historically, as you know, Visual Studio is the standard for "File->New Project" or anything to do with a .NET solution or...


Troubleshooting Installing .NET Core 1.1 RTM on OSX

.NET Core 1.1 RTM was announced yesterday along with Visual Studio for Mac! So of course, I jumped right over to install them both. During the install of the 1.1 version of .NET Core from the downloads page, hit a snag on OSX. If you have seen recent Scott Hanselman talk ASP.NET Core, there is a slide he uses where he references "How do you like your ASP.NET?" I'm somewhere between "medium-rare" and "medium-well", depends on the machine I am using. I had the preview bits installed which had a version of 1.0.0-preview2.1-003155 and now the RC 1.1 is released with version of 1.0.0-preview2-1-003177. When running the command dotnet --info...