ASP.NET Core : Getting Clean with SOAP

Being able to take the packaging off the new toy and spin up a new project is a lot of fun I must admit. However, when leaving the latest conference, hack-a-thon or turning away from the latest webcast on that shiny penny; real life hits and trying to get this new thing to work with the old thing sets in. WCF WCF is a framework that many .NET developers came to love and built many of services on to support Silverlight and WPF applications and was the basis for Web API. However, it's primary protocol was SOAP and a message format of XML. There are many other great features, WS-*, Transactions, Reliable Messages and more; but for most business it...


Weekly Ink 5/24/16

This is the first installment of Weekly Ink where I'll share a few links if the articles, posts, videos etc that I found valuable. I am not a link collector, but feel the need to share certain posts that have some value, at least to me and if nothing else, I have a place to go back and reference. ASP.NET Core Getting the Web Root Path and the Content Root Path in ASP.NET Core - @mariusschulz Changes to Project.json - Scott Hunter @coolcsh Strongly Typed Configuration Settings in ASP.NET Core - Rick Strahl @RickStrahl ASP.NET CORE DISTRIBUTED CACHE TAG HELPER - ASP.NET Monsters Angular 2 How to Use TypeScript Enums w/ Angular 2 -...


ASP.NET Core: Watching Code

Being able to edit code and see the changes on the fly is a big advantage when developing applications with all of the "moving parts" in today's tech stack. Simply hitting F5 doesn't cut it anymore. Everything needs to be compiled, minified, uglified, or transpiled to get your app to show up right. On the node.js side of the dev stack I have been using nodemon to watch files for changes and execute whatever functions need to be run and restart the node server for my client apps during development. nodemon ./server.js localhost 8080 Early on in the ASP.NET Core days, beta 3, I creates a nuget package called KMon that used nodemon under the covers to...


Angular 2 : Giving Your CLI a Server

...be sure to read Angular 2:Re-Quickstart with the CLI Although the CLI includes a number of great features, the deployment of the application is a story or issue that is still under discussion (Production deploy #326). What is the right server, what are the features etc. A simple static server for Angular applications should be able to handle a few things: static files - like that pesky fav.ico, images, css, and javascript files deep links - routing to specific portion of our SPA maybe something simple like compression In this case, node.js using Express fits the bill. Let's see how to add it to the quickstart generated in the previous post. First, grab the index.js and...


Angular 2 : A Re-Quickstart using the CLI

The Angular team created a quickstart which is a great starter project template and I've covered that in another post which shows adding an express server to that to get you up and running with a more complete quickstart at Angular 2 : Getting Off the Starting Line. Both are great starters, but static templates. This Re-Quickstart* is using the CLI (command line interface) to create the same application in a fraction of the time. angular-cli The angular-cli is the new command line interface for creating Angular 2 applications. Well, It's much more than that. It creates applications, follows the best practice or approved style guide, sets up the tests, runs the tests and much more. Head over to cli.angular....