My Rants and Raves about technology, programming, everything else...
The Vue team has been working hard. Much like Angular, the Vue team has a command-line interface (CLI) to help develop projects with Vue.
If all you're doing is building a SPA, the CLI can really help simplify setting up a project. But is that all you should be doing with Vue?
To start this workshop, I'm starting with my home town of Atlanta. On January 16-18th, I'm having a three day workshop to teach how to build a website using ASP.NET Core 2.2 and Vue.js.
The workshop will use the following technologies:
I was reading my newest issue of MSDN Magazine and came across Julie Lerman's great article on how to configure Logging in Entity Framework Core. While this is great information, it only covered logging Entity Framework Core from a non-ASP.NET Core project so I figured I'd explain how to do it in ASP.NET Core.
The biggest thing that is different from the way that Julie shows this is that ASP.NET Core automatically wires up the ASP.NET Core logger to the context when it injects a context into your project. So to see Entity Framework Core logging, you need to enable it your ASP.NET Core logging, not in Entity Framework Core.
First let's talk about how Logging is handled in ASP.NET Core. In your
Program.cs file, the
WebHost.CreateDefaultBuilder() automatically sets up logging:
I had the great fortune of doing a remote presentation for a user group in Saudi Arabia. I showed the basics of ASP.NET Core and I loved the questions from the audience.
In general I don't prefer to do remote talks, but with my self-imposed land-locking, I'm available for them for your group if you have a meeting coming up. So as promised, here is the code and slides:
As ASP.NET Core 2.2 is now in preview, i've been looking at some of the early features for an update to one of my Pluralsight courses. ASP.NET Core 2.2 includes a number of new features, but this is a feature I really like.
If you haven't seen the whole list of new ASP.NET Core 2.2 features (in Preview 3 as of the updating of this post), take a look at the announcement here: blogs.msdn.microsoft.com.
UPDATE: 2.2 Preview 3 Changes this behavior
If you're not in the south part of the Netherlands, you might have missed my most recent appearance last night. Great hosts, guests and sponsors make the night and easy and fun talk.
After a long day at Techorama NL, I was whisked away to Eindhoven for a talk at the .NET Zuid group (e.g. Southern .NET Group). I was able to show them the basics of Vue.js and pontificate about my continued hatred of the phrase "Single Page Applications".
As promised, I wanted to make the slides and code available to the attendees. You can get them here:
This time I was in Ede, Netherlands for the first Techorama outside of Belgium. As usual, the team did an amazing job! Here are the slides and code as promised from that event:
Thanks for asking great questions and attending the sessions!
I'm in the middle of a road trip for three conferences and it's been an amazing time. Next up is Techorama Netherlands! I am lucky to be asked to speak at so many amazing conferences.
As so many of you know, I travel a lot for speaking and work. This year has been a tumult of experiences and emotions. With my film finally heading into post-production I've made a decision about conferences for the next fifteen months or so.
So I'm going to stop doing conferences that require a plane trip. This is a big disappointment for me, but I think it's necessary. I have a lot I need to get done this year and, as fun as conferences are, they take a lot of time and energy.
I've been advocating using NPM for a client-side package manager in the last few months since Bower support has been depreciated. And while this works pretty well (using Scott Allen's UseNodeModules middlware) to allow you to just point at the NPM folder.
Of course, for production, this isn't a great solution. I've been showing people to use Gulp or WebPack to copy only the files you need in production. But for development, there is a problem: Intellisense.
I've noticed that Visual Studio 2017 only seems to notice files in the wwwroot folder. After trying a bunch of things, I think I found a solution. If you open the CSPROJ file and add this section to point at the node_modules directory: