Recently i am trying to build multi-tenant application using Asp.Net Core. In that journey, I found an amazing series by Ben Foster where he wrote step by step guide to build multi-tenant application with Asp.Net Core and SaaSKit (A developer toolkit for building SaaS applications). With the help of that series, i am able to build foundation for multi-tenant application. I have added a bit more features in my sample like creating database per tenant as they loaded first time. I have shared my multi-tenant foundation application in github so that other can get idea to build their own. I will add more features along the way.
Recently i am working on project where i have to build simple Authentication Server. For that project i need to use Resource Owner Password (ROP) OAuth flow with persistence storage of all data. Also need to handle Social Signup/login with ROP flow. Facebook and Google as third party Identity Provider is available in this sample ( up to now)
So i am using Identity Server 4 and Entity Framework core to build this simple authentication server. This sample might be helpful if you are working on same as my requirement.
Also i am extending this sample to support other OAuth flow in future.
Here is project link in Github.
In first post, i talked about MongoDB briefly and showed how to set up local environment to work with MongoDB.
In this second post, I will show you how to actually use MongoDB as a data storage with ASP.NET Core application with simple CRUD operation. As I mentioned earlier I am using ASP.NET Core Web API for this article.
In this 2 part series, I will show you how to use MongoDB as data storage in your ASP.NET Core application.
As you may know, MongoDB is an open-source document database, and leading NoSQL database. It is a cross-platform, document oriented database that provides, high performance, high availability, and easy scalability. MongoDB works on concept of collection and document.
It has been almost 2 years I started blogging where I am sharing stuffs related to my programming journey (with .NET, Azure and other OS stuffs). I am few post away to hit 50th post on this blog. Up to now I take this blog as a space to share my programming knowledge but now I want to do more with this blog (i.e. earn some passive income). So I want to learn some blogging and money making courses. Since I am long time follower of John’s online content I want to give a try to his blogging courses. I was planning to take money making course (10 ways to make money with your blog) but first I want to finish his blogging course (Create a blog to boost your career) for beginner, after all I want to learn things from ground up. Now my next target is his “10 ways to make money with your blog” course.
In this post, I will guide you on how to add Azure AD as a identity provider in your ASP.NET Core application. We will use OpenId Connect middleware to sign in users from a Azure Active Directory tenant.
Recently I was planning to add logging service in my new side project test-api.net (which provides mock API for test purpose) and found elmah.io interesting so I wanted to give it a try. Maybe this blog post could be a series, if I decide to integrate this service in my project. In this post I will share my first experience with elmah.io from signup to pushing some log messages.
First let’s know a bit about JSON Patch.
JSON Patch is a format (identified by the media type “application/json-patch+json”) for expressing a sequence of operations to apply to a target JSON document; it is suitable for use with the HTTP PATCH method.
Today I was cleaning and sorting my Chrome Bookmark list, I was looking podcast folder weather there are any podcast that I am not listening recently. Didn’t found any but I want to share my podcast list to other developers which i prepared to listen regularly in 2017.
I listen developer, entrepreneur podcast mostly and i am .NET guy so most of my choice are shifted towards Microsoft Technologies. 🙂
Asp.Net Core 1.1 now provides GZip Compression middleware. GZip is a method of compressing files (making them smaller) for faster network transfers. Compression allows your web server to provide smaller files sizes which load faster for your users.