Things I’ve Learned This Week

Things I’ve Learned This Week

Things I've Learned This Week (14th April)

Things I've Learned This Week (14th April)

Things I've Learned This Week (14th April)

I’m not sure whether this will become a regular thing but starting this week I’ve been writing here on the things I’ve learned, problems I’ve faced and resources that I’ve read, watched or listened to and absolute must Errors I’ve got. Posts will include such as information about ASP.NET and getting better what I want to do. 

We will evolve with new technologies, see how to collaborate with favourable libraries and implement those to suitable design pattern all together. As we all do, saving the links, pointing lines, implementing someone’s code to our projects. I hope that we can highlight key points of information I have found useful and to share links to things I've learned from, and make them useful for all of us. 

Logging in .Net Core 

Firstly in all our application that we need to take care of bugs, errors, future user mistaken (at the end it’ll be no doubt about it) and actions which take most costs. So, situations will define that which log mechanism you should go for.

As @stefvardalos mention, “There is another part which is called audit logging. Where the diagnostic logging takes care of recording the events that happen during runtime (method calls, input/outputs, HTTP calls, SQL executions), the audit logging is responsible for recording more abstract, business logic events. Such events can be user actions (adding/editing/removal of content, transactions, access data) or other things that have either managerial value or, more importantly, legal value.”

In that case our application may contains many tenants and we cannot afford to save log that every database change in to sql server. To follow borakasmer (Audit Logging with ElasticSearch)  

Identity Server 4

As part of my work for Argemera & FiguresNFacts I’ve been actively investigating Identity Server 4 as an option to handle our authentication. The allReady application currently uses ASP.NET Core Identity within the application to support login and user management. As a result this led Ali Doğan to suggest we look into Identity Server 4 to help with this identity flow.

I drawted the architecture of database how it will look like and then we aggree to have user can manage their own role inside the applications. As we allready have an option for our wpf application but it's not nicely fit in the .net core web applications. So, for that we look around and found the Serenity App . As I continue investigating and testing Identity Server 4, I hope to put together some more details posts about how we’re using it and what I learn along the way.

Read : Authentication:

Logging .Net Core:



#Best Practices:



Dominick Baler on Identity Server  A demo of using Identity Server 3.

Entity Framework Core With Julie Lerman

  • Visual Studio 2017 More Effective Usage
    Visual Studio 2017 More Effective Usage