Notes from the ASP.NET Community Standup – April 12, 2016
This is the next in a series of blog posts that will cover the topics discussed in the ASP.NET Community Standup. The community standup is a short video-based discussion with some of the leaders of the ASP.NET development teams covering the accomplishments of the team on the new ASP.NET Core framework over the previous week. Within 30 minutes, Scott Hanselman, Damian Edwards, Jon Galloway and an occasional guest or two discuss new features and ask for feedback on important decisions being made by the ASP.NET development teams.
Each week the standup is hosted live on Google Hangouts and the team publishes the recorded video of their discussion to YouTube for later reference. The guys answer your questions LIVE and unfiltered. This is your chance to ask about the why and what of ASP.NET! Join them each Tuesday on live.asp.net where the meeting’s schedule is posted and hosted.
This week’s meeting is below:
Links of the Week
I think the guys want me to rename this segment to “Jon Loves Community…”, but I think we should re-use the intro song lifted from Mr. Rogers Neighborhood for that. Hmm….
Ben Foster discussed the new JSON patch support in APIs in ASP.NET Core.
Armen Shimoon published an article on using dependency injection to load custom services based on a request
James Chambers posted a reminder about the open source’d AllReady project in the Humanitarian Toolbox. If you want to get started with open source and are looking for a cool project to get started with, check this one out. The ASP.NET and Visual Studio teams kicked off this project as part of the Visual Studio 2015 launch.
Rahul Sahay is starting a blog series on creating a SPA that works with ASP.NET Core and Angular
Luke Latham wrote up a tutorial on using ASP.NET Core on Nano Server.
Shayne Bower has a blog post about using Kestrel as a static server for Aggular
Retschgi.com has an article about using ASP.NET with Postgres and Heroku
Mads Kristensen has released a new extension for Visual Studio that verifies web accessibility standards.
Muhammed Rehan Saeed published an article about social taghelpers in ASP.NET Core
Hans Arne Vartdal wrote up how to connect ASP.NET Core with Auth0 bearer tokens
Jon also pointed out RestBus to help with messaging to connect ASP.NET Core, WebAPI, and ServiceStack with RabbitMQ
Scott encourages everyone to check out these blogs and leave some encouraging comments because these blogs are getting more and more impressive.
Question of the Week:
From Twitter, Grahame Horner asked about some samples demonstrating how to run Kestrel on ServiceFabric.
— Ben Adams helpdully answered by pointing to the weidazhao/Hosting repository on GitHub.
At this point… things took a slight diversion, as Jon turned off his screen-sharing for the community links and Scott noticed that Jon looked a little… different.
Instead of Questions and Answers this week, Damian and David Fowler shared a demo of using a daily build of the .NET CLI and Visual Studio Code. These items are the current state of things as they are being assembled and are not in their final packaged model ready for shipment and easy installation. Here are the steps with extensive links (updated for this morning’s announcements) so that you can follow along and try it for yourself:
- Download the .NET Core SDK from the .NET CLI Github repository appropriate for your machine.
- Scott noticed Damian’s install of posh-git and the cool command-prompt that it offers.
- Damian verified that the CLI is installed properly by running dotnet –help
- Next, Damian installed the Visual Studio Code editor. In the video, he downloaded the March Insiders Release. However, the 1.0 version of Visual Studio Code was released and you can install that.
- Download or clone the ASP.NET CLI Samples repository. You can close it with the git command:
git clone https://github.com/aspnet/.git
- Damian navigated his command-line to his new CLI-SamplesHelloWeb folder and ran “dotnet restore” from that location.
- Next, the project was built by executing “dotnet build”
- The web application was started by calling “dotnet run”. This launched the web server and started hosting this simple web application at http://localhost:5000
- This should show a simple “Hello World” page in the browser.
- Next, lets look at the editor experience. Open the HelloWeb project folder in the new version of Visual Studio Code.
- By default now, Visual Studio Code does NOT come with C# language support and you need to add it. VS Code will detect that you need C# support and prompt you to download it. If yo uwant to grab the latest version of C# support, navigate to the Omnisharp repository and download the VSIX there.
- If you download a VSIX, install it in Visual Studio Code by using the File – Open command in Visual Studio Code to open the VSIX file you downloaded.
- This install will look like it isn’t doing anything, but there is an indicator in the bottom-left statusbar of the editor that shows that the install process is taking place. Once this has completed, an indicator will appear at the top requesting a restart of VS Code.
- Once restarted, you should see the Omnisharp flame in the bottom right statusbar with the name of the project.
- You should also see that Visual Studio Code will download and install the .NET Core Debugger
- Put some breakpoints in the startup.cs file on the app.Run statement and the return statement inside of app.Run
- Select the Debugger panel in VS Code, indicated on the left side as a bug with a line through it.
- In the debugger panel, choose the .NET Core Launch (console) and click the ‘play’ button to the right of that combobox at the top
- Congratulations! You’re now debugging with Visual Studio Code!
This should work on any OS as all of these tools are now cross-platform. Its a big first step for the team to have this complete tooling and framework setup working together properly. Join us next Tuesday as we talk more about ASP.NET