atillatan/robo-aspect-framework

Stars
2
Language
C#
Created almost 8 years ago
Updated over 6 years ago

atillatan/robo-aspect-framework

atillatan

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

This project demonstrates when we invoking some method we can pass the method as a parameter to another method. If we design the second method for separating of concerns (SoC), we can use Aspect Oriented Programing (AOP). we can catch method attributes, and we can call BeforeAspects() and AfterAspects().

Enterprise-Angular-Project

This project demonstrates how to build Enterprise Grade Angular Project.

sso-with-identityserver4

Single Sign-On implementation using IdentityServer4

robo-thread-manager

Single Class Thread Pool Managar; The ThreadPoolManager is controls thread pool and job queue, it supports separated dynamic job queue from threads Comparing the other thread management methods, ThreadPoolManager gives you the best performance.

kafka-microservices-and-transactions

blog

nonsetup

robonom

Simple blog framework

IP-Man

IP-Man scans your network (WAN and LAN) to determine the identity of all devices, which automatically discovers sevices of devices. It allows you to access your devices everywhere.

cross-platform-desktop-application-with-netcore2x-and-angular6x

This project introduce simple cross platform desktop application with .Net Core 2 and Angular 6 in Electron environment.

roboutil

simple utility library

filehoo

robo-middleware-framework

This project demonstrates when we invoking some method we can pass the method as a parameter to another method. If we design the application using middleware pipeline. we can success method calls with Separating of Concerns (SoC) we can catch all methods in middleware pipeline, and we can execute before middleware and after middleware

Chain-of-Responsibility-pattern-implemention.

The Chain of Responsibility pattern is one of the twenty-three well-known "GoF design patterns" ASP.NET Core applications uses "The Middleware Pipeline". The term “pipeline” implies that requests enter one end, are processed by each middleware component in turn, and exit the other end. In reality, the run-time behavior is a variation of the Chain of Responsibility design pattern