Frequently asked questions
'Arcus' is an umbrella term for a set of NuGet packages/PowerShell modules that helps reducing boilerplate code from projects. Whether it is setting up testing suite, automating infrastructure tasks or other frequently repeated patterns, Arcus provides a well-tested quality solution to kickstart your project.
It is not the purpose of Arcus to replace existing Microsoft technology. It builds on top of their stack to provide added-value and connect missing links. Arcus is and continues to evolve in this goal.
The frequently used boilerplate code that is often copy-pasted between projects is centralized in Arcus. Maintained by experts in the field, it gives confidence and saves you time during development. This results in less code to maintain.
Arcus is split into components, each active in a specific field. The functionality in each component is highly modular and can be used independent or together with other components. The easiest way to get started is to determine in what field you want to experiment with Arcus and go over its getting started guide:
- Arcus Messaging: lets users focus on business logic when interacting with messaging systems.
- Arcus Observability simplifies telemetry tracking.
- Arcus Scripting: provides frequently-used, repeated infrastructure tasks.
- Arcus Security abstracts and simplifies secrets interaction.
- Arcus Testing: provide test infrastructure components.
Arcus is split into components, each active in a specific field. Most Arcus components are available via NuGet packages, with the exception of Arcus Scripting, which are PowerShell modules.
First off: Thank you! We are always happy to receive contributions on our Arcus components. TODO work is managed via GitHub issues:
- Do you want to contribute something simple to get familiar with Arcus' codebases? See our getting started issues.
- Do you have an idea or a problem with Arcus? Feel free to add an issue/bug to the GitHub repository of the Arcus component of your choosing!