A basic implementation of ASP.Net Core as backend with a React Single Page Application as frontend. The login process is completely implemented (including front end). This project can be used a starter. My experience has shown that it's sometimes really nice to have real world example about how an application can be structured and implemented. Lot's of tutorials are written fairly abstract without actual examples that respect all the challanges you will face. This project should by no means be an allrounder, but I think it covers a big part of what most applications need. From my experience, this is the ideal project structure with the best libraries, but I'm always open to criticism and discussion.
- Build Task: Use Fake to build the project and execute tests which can be executed locally aswell as by your CI
- Deployment: Dockerfile to create a Docker image for your application that can be executed in every environment
- Best Practices and popular patterns to create a maintable and modern structure
- State of art implementations of all used frameworks/libraries, using the most recent updates
- Domain Driven Design
- TypeScript for a strongly typed code base
- typesafe-actions to strongly type the Redux store, reducers and actions
- Allow absolute imports using
src/store/....(thesrcprefix, see discussion here) - Material-UI as design framework
- Axios for HTTP requests
- TsLint and Prettier are preconfigured
- Formik together with redux-promise-listener for easy forms (with custom typings and a React Hook)
- C# 8 with nullables
- Swagger API
- Serilog for structured logs
- Autofac for fast dependency injection
- AutoMapper for object mapping (e. g. entities to dtos)
- Ef Core as ORM
- ASP.Net Core Identity with BCrypt password hasing
- Authentication is implemented using JWT and refresh tokens
- The front end automatically refreshes the JWT if a refresh token is available (using Axios interceptors)
- SignalR
- in front end, it is directly connected to the redux store, hooks are included that subscribe/unsubscribe to events if the component is loaded
- Provide a clean and defined way to transfer errors from the backend business logic to the React ui
- Every error has a code, a message and a type
- The ui has easy ways to process and show the error
- Unit Tests are implemented using XUnit
- Mocks are created using Moq
- Integration tests that can be debugged
Build with Fake
fake build
In root lies a script (/rename-solution.ps1) that will rename AwesomeAspCore to the name of your application. Just run it and it will prompt you asking for the new name.