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...
- Dipping the toe in the Azure Compute space and then some.
- Serverless like a Superhero with Azure Functions
- Use a container to show your function swagger
- Unmasking your swagger with proxies in Azure Functions
- Do more or less with default values in the Azure CLI
- Testing Azure Functions with Postman and Swagger
- Azure functions - Just the CLI, hold the GUI, add some git
- dotnet new angular to Azure with Docker using CLI
- Angular 2: Application Settings using the CLI Environment Option
- Troubleshooting Installing .NET Core 1.1 RTM on OSX
- Using Apache Web Server as a reverse-proxy for ASP.NET Core
- Deploying an Angular 2 App to Azure with Github
- ASP.NET Core: Watching Code
- .NET Core Slack Channel Sign Up