.net

Object datasource or code-behind: which is better?

by

I know that it’s a subject that can raise a lot of debate, but I’d like to know what people think the various pros and cons of using Object Datasources are. I’m doing a project right now with another programmer who’s experience and comfort level are all rooted in classic ASP, and I’m unsure of which way is going to
a) get the job done quickly
b) get the job done with a minimum of fuss

Getting the ClaimsPrincipal in a logic layer in an aspnet core 1 application

by

I’m writing an aspnet core 1 application.
Using a bearer token authentication I have the User property inside the controller with the correct identity. However I cant seem to find a way to grab with identity as I did before using the ClaimPrincipal.Current static.
What is the current best practice to get this data inside the BL layers with out passing the ClaimPrincipal object around?

Patterns / design suggestions for permission handling

by

We have a rather complicated system of permission handling in our (ASP.NET web) application. Users can have specific permissions on different kinds of objects, some permissions are even packed into groups / roles that are assigned to users. All in all this ends up in a pretty complicated mess where for determining whether a user can do / see something you have to evaluate many different sources of permissions and this is done somehow on-demand and based on specific situations.