Updated - 1.30.2014 After looking at the kpm pack or publishing step of this solution, there is an undesired affect. All of the folders in the root, now that this is the folder we are working in, will be published to the destination folders. Being approot & wwwroot (yes this is still created), this includes the bowercomponents, nodeemodules, your API code etc. Although IIS will keep you from browsing to the *.cs and other extensions for security sake, it is still not a clean solution. I have updated the dev branch of the git repository where wwwroot is put back in, and the gulpfile.js task called optimize now will publish the necessary files to this folder on...
- 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