If any of you are on the fence about reading this: please give it a go! Nate is one of the best people I know (both personally and professionally). He's an incredibly hard worker, really great developer, and awesome human. I'm sure you'll learn a lot from him.
One of my concerns about .NET core is it seems that there are a handful of ways to do things compared to Java. But I'm starting to like the fact that there are fewer options that work really well. Plus there are things like LINQ that I haven't seen used much elsewhere that blow my mind.
I have an issue with the first view, when running I get the error below on all references in the cshtml. I'm using a stock install of VS 2017. Any ideas?
/Views/Todo/Index.cshtml(4,5): error CS0103: The name 'ViewData' does not exist in the current context
/Views/Todo/Index.cshtml(8,33): error CS0103: The name 'ViewData' does not exist in the current context
/Views/Todo/Index.cshtml(8,27): error CS0103: The name 'Write' does not exist in the current context
/Views/Todo/Index.cshtml(19,31): error CS0103: The name 'Model' does not exist in the current context
/Views/Todo/Index.cshtml(23,1): error CS0103: The name 'WriteAttributeValue' does not exist in the current context
/Views/Todo/Index.cshtml(25,16): error CS0103: The name 'Write' does not exist in the current context
/Views/Todo/Index.cshtml(26,16): error CS0103: The name 'Write' does not exist in the current context
dotnet --version shows 1.1.0, I think I assumed that the latest VS2017 would have the latest dotnet core but this doesn't seem to be the case.
Then you have also Scott Hanselman, a known .net evangelist: https://www.hanselman.com/ and Scott Guthrie
Jeffrey Way, Tyler Otwell are the stars of the php world thrse days.
But some interesting people to follow are Jimmy bogard, greg young, David Fowler.
I've found that I rarely read Hanselman's stuff any more... he's great if you're playing around with bleeding-edge ASP.NET Core on Linux on Azure, but not if you're trying to dig into the guts of C#. (I was so burned by the so-called "release candidates" of ASP.NET Core that I stopped following that vein of blogger.)
For ASP, David Fowler without a doubt, also recommend Barry Dorans and Scott Sauber
One of my favorite things about the ASP.NET team is that a lot of them were community leaders - speakers, writers, open source library authors, etc. - before being hired at Microsoft. So it's hard to pick just one or two community leaders on the team, as pretty much everyone regularly speaks at conferences, publishes open source code, blogs, etc. So it's really hard to make a short list! Hopefully this is still useful to someone.
As several others have mentioned, you really should start with Scott Hanselman (https://www.hanselman.com/ and @shanselman).
[Disclaimer: he's my boss, but I joined his team because I was a big fan long before either of us worked at Microsoft]
The ASP.NET Weekly Community Standup is a great place to connect both with the team and with the leading members of the developer community. It's at https://live.asp.net/ with Damian Edwards, Scott Hanselman and me. Damian Edwards (https://twitter.com/damianedwards) is the program manager for the ASP.NET team. During the show, I usually share 10ish links to top posts, open source projects, etc. by the community. We feel like the ASP.NET Community is made up of developers both inside and out of Microsoft, so you'll see a mix. The links are usually in the show notes, and we also tweet the links out daily at @aspnet. I'm not going to risk making a list because I don't want to leave anyone off - there are too many for me to even try to pick favorites!
Next, check out the "official" Web Dev blog: https://blogs.msdn.microsoft.com/webdev/. We have a general rule that all posts are signed by actual people, not "the ___ team", so you can see who's working directly on specific topics. You'll definitely see a lot of posts by Jeff Fritz (my team mate), who (in addition to program managing several features) does a ton of work to write up release posts, organize content for conferences, etc.
I think of David Fowler (https://twitter.com/davidfowl) as the "crazy genius" on the team. He and Damian wrote SignalR, he worked on prototyping some of the very early work that became ASP.NET Core (and .NET Core all up), etc. Check out this video to see what I mean: https://channel9.msdn.com/Events/NDC/NDC-Oslo-2017/BRK06
You'll also see Glenn Condron (https://twitter.com/condrong) listed on several of the recent Web Dev blog posts. He covers a lot of deep back end tech, including a lot of stuff with ASP.NET Core on Docker.
You can see quick (5-10 minute) interviews with most of those people, as well as a lot of other people on the .NET team, on a show that Maria Naggaga (https://twitter.com/ladynaggaga) and I started up recently called Code Conversations (https://channel9.msdn.com/Shows/Code-Conversations). These are short, code focused interviews you can watch while your code is compiling and hopefully put to work right away.
Finally, please ping me at @jongalloway if I can help connect you with anyone or if you're having trouble finding information, code samples, etc. I'm happy to help!
Consider me sold!. Have been watching .NET Core from the sidelines while I have been "teaching myself" Python. But being constantly on a Windoze systems there is so much more that one could with .net core. Thanks for putting this together.
Having read through it, it is indeed nice and concise - but I'm of two minds of the content - is it really good to introduce server side rendering with jquery and ajax - today?
I think, that showing server side rendering is good, for a beginner (how do I go from a form, to db, and back to a simple html table?) - but I'm not sure how useful the "half-way to smart client"-approach of jquery is. I'm almost convinced throwing out most of the server side rendering in favour of returning json and rendering everything client side would be better, than the "in between" approach.
But for someone that "grew up" with the html to html+ajax it made the book very accessible, and manages to show off a remarkably broad and (apparently) useful section of asp.net core to someone not well versed in asp.net core.