Prev | April 2018 | Next | |||||
W | S | M | T | W | T | F | S |
13 | 25 | 26 | 27 | 28 | 29 | 30 | 31 |
14 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
15 | 8 | 9 | 10 | 11 | 12 | 13 | 14 |
16 | 15 | 16 | 17 | 18 | 19 | 20 | 21 |
17 | 22 | 23 | 24 | 25 | 26 | 27 | 28 |
18 | 29 | 30 | 1 | 2 | 3 | 4 | 5 |
Want to receive every Tuesday the best .NET links?
Once subscribed you can login, submit a link and receive the weekly newsletter.
by bill-s, 2018-04-02T20:45:42.564Z
Cloudflare's mission is to help build a better Internet. We're excited today to take another step toward that mission with the launch of 1.1.1.1 — the Internet's fastest, privacy-first consumer DNS service. This post will talk a little about what that is and a lot about why we decided to do it.by bill-s, 2018-04-03T20:08:27.070Z
Each course runs for three months and starts at the beginning of a quarter. January—March, April—June, July—September, and October —December. The capstone runs for four weeks at the beginning of each quarter: January, April, July, October. For exact dates for the current course run, please refer to the course detail page on edX.org.by bill-s, 2018-04-02T20:45:42.564Z
Tired of REST? Let's talk about GraphQL. GraphQL provides a declarative way in which you can fetch data from the server. You can read about every bit of goodness that is baked into GraphQL in the official site. However, in this series of blog posts, I'm going to deal with ASP.NET Core and will show how you can integrate GraphQL with it and use it as a query language for your API.by bill-s, 2018-04-02T20:45:42.564Z
Initially they were just flat out recommendations for the tools but I decided yesterday to give them a bit more structure, add details and design them in the steps form so to give you a better idea about what to pick and in what order.by bill-s, 2018-04-02T22:18:32.263Z
Developer Advocate Nate Barbettini breaks down OpenID and OAuth 2.0 in Plain Englishby bill-s, 2018-03-30T03:12:09.466Z
Connect with experts at Microsoft Tech Summit in Warsaw, a free technical learning event for IT professionals and developers. Choose from lots of learning opportunities to build your cloud skills, including 80+ sessions, keynotes, hands-on labs, and more. Don’t miss out—register today!by bill-s, 2018-04-02T20:45:42.564Z
This project was to be developed in ASP.NET Core with a Web API backend and Vue.js front-end. I also wanted to develop this project completely on my Mac to ensure it was cross-platform (as it will eventually run on a Raspberry Pi), and as a learning experience.by bill-s, 2018-04-03T20:08:27.070Z
e continuing with our series of posts on creating performant and scalable web APIs using ASP.NET Core. In this post, we'll look at using a Microservices architecture to help scale out our APIs.by bill-s, 2018-04-03T20:08:27.070Z
As you may already know, I’m one of the maintainers of the FakeItEasy mocking library. As is common in open-source projects, we use a workflow based on feature branches and pull requests. When a change is requested in a PR during code review, we usually make the change as a fixup commit, because it makes it easier to review, and because we like to keep a clean history. When the changes are approved, the author squashes the fixup commits before the PR is merged. Unfortunately, I’m a little absent minded, and when I review a PR, I often forget to wait for the author to squash their commits before I merge… This causes the fixup commits to appear in the main dev branch, which is ugly.