TeleScope DOCS
✨ The project aims for any project type or distant targets, just like a telescope.
💎 The NuGet packages are strongly based on Clean Architecture Principles and are encapsukated to maximize their reusability.
📚 The framework contains of 15+ packages for cross-cutting concerns, like connectors to external services, persistence layer and helpers for client code or user interactions.
🔭 Structure of this site
📋 Articles | 📚 API Documentation |
---|---|
Explore examples and further explanations about major features. In the next time there will be examples about all cathegories. | Discover the entire public API. Classes, methods, events, members and so on are described with the auto-generated documentation. |
🚀 Quick Start
The TeleScope project provides separate NuGet packages for abstractions and implementations. Please use the assemblies within a particular application layer, depending on whether an abstraction or its implementation is needed.
Simply install the desired packages in your preferred way with NuGet Package Manager, CLI or xml reference.
PM> Install-Package TeleScope.{awesome-package} -Version 2.*.*
NuGet Packages
A full overview of all provided packages can be found below.
TeleScope.* | Packages |
---|---|
GuardClauses | |
Logging |
🌐 Clean Architecture Principles
The TeleScope project supports any architectural approach, but it was designed for Clean Architecture projects. There might be differences in naming this architectural approach or its layers, but the goal remains the same.
Note
Keep your business logic clean and free from external dependencies or their breaking changes.
The implementation of follows the ideals of Uncle Bob and Jason Taylor - so thank you both! 🍻
Of course, TeleScope packages are external dependencies for other projects. So TeleScope separates its entities from the implementations, so that other projects may inject them where they are needed. Additionally, you can take advantage of the example implementations or you are also free to create your own implementations.