My Rants and Raves about technology, programming, everything else...
Just got back from Chattanooga, TN for Scenic City Summit. I got to do two talks there and had some great audiences and questions.
Was great to catch up with some of the best speakers in the southeast at the event. I hope the attendees enjoyed it as much as I did.
As promised, here are the slides and the code from my two talks:
Doing a talk on a preview (ASP.NET Core 2.0) on top of another preview (VS 2017 Preview) is always risky, but it went well. Lots of great questions and hopefully I convinced some of the attendees to give it a try.
As promised, I wanted to share the slides and code:
I’m working on an update for my ASP.NET Core course for version 2.0. One major change is to use Angular (v4 probably) in the new course.
My challenge was to get Angular and ASP.NET Core to work together. I like the idea about Angular-CLI doing all the boilerplate since setup is a bit of a headache. Should be an easy win-win. Well…
UPDATE: Forgot about turning TypeScript off in the project. See Below.
I am sure that many people like me are digging into ASP.NET Core 2.0 and curious about what has been changed. I’m going to start with the very start of your ASP.NET Core project, the program.cs.
Digging into the meat of ASP.NET Core 2.0 might lead you to identity, the better .NET Core support, and other changes. But I think the startup is where you can start to see the platform mature.
So in ASP.NET Core 1.x, the usual program.cs usually looked like this:
I know that some people learn better in-person than online, so starting next month I’ll be back to offering in-person courses. These includes some of the same topics as my popular Pluralsight course, as well as topics that are not covered there.
These in-person training courses can be customized for your company’s particular needs and skill level of students. Feel free to take a look at my company’s website for more details.
The new courses include:
I had the pleasure of being asked to come to Stockholm to attend the DevSum 2017 conference. While my talk was the last of the day on the last day of the conference, I still was able to meet a bunch of great developers who stayed long enough to see my talk on Hololens.
As usual, the demo tanked, but I was able to save face by showing the after version of the demo. Unity can be a little headstrong and getting the settings to work with Hololens mis risky in front of an audience, but we got some good questions about how you’d use Hololens.
As promised, here are links to the slides and demo:
Writing web apps has become complicated. Transpilation has made some thing really awesome, but it also has complicated the field. Webpack, Browserify, Babel and even TypeScript have all make our lives easier and awful at the same time.
I loved this tweet about our current situation:
Developers are an odd beast. Some developers love a big IDE and lots of automation to help them create great solutions.
The other type of developer, wants to write code quickly and spends a lot of time at the command-line. Luckily, Microsoft supports both types of developer.
Even though I use Visual Studio quite a lot, the brevity of Code allows me to be faster sometimes. Because of this I created a course showing how to use VS Code with ASP.NET Core projects.
I love this conference because the attendees are so plugged in and I get great questions every time I do a talk there. I want to thank everyone for coming to see me talk on ASP.NET Core even though I had lost my voice. We muscled through though and hopefully some people are digging in deeper with it now.
But now that we’re in ASP.NET Core 1.1 (I know 2.0 is in preview, but I’m sticking with 1.1 for this discussion) and Visual Studio 2017, it feel a lot harder than it should be.
I miss project.json, but that’s not what this post is about. It’s about a lot of little helpers that used to make it easier for people coming to the platform, including: