C# library with a wide variety of tools and utilities in one easy to use location.
Nuget: https://www.nuget.org/packages/ArcherCore
> dotnet add package ArcherCore --version 1.1.1
ArcherCore is a collection of common tools used in C# (in my opinion) that are simplified and housed in one easy to use library.
- C#
- .Net 6.0 | https://dotnet.microsoft.com/en-us/download/dotnet/6.0
- Library
- Visual Studio 2022 | https://visualstudio.microsoft.com/vs/
This library current has utils for the following:
- Compression
- Credit Cards
- CSV Reader
- Dates
- ECDSA
- Encryption
- Extension Methods
- File IO
- File Download
- Hashing
- Http
- IP
- Logging (Both Text File and DB)
- Memory
- Numbers
- Passwords
- Pinging
- Port Checking
- Randomization
- Strings
- Time
- Timers
- Valid States
- Web Request
- Web Server
We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
We use github to host code, to track issues and feature requests, as well as accept pull requests.
We Use Github Flow, So All Code Changes Happen Through Pull Requests
Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:
- Fork the repo and create your branch from
master. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
Report bugs using Github's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
This is an example of a bug report written, and I think it's not a bad model. Here's another example from Craig Hockenberry, an app developer whom I greatly respect.
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can. My stackoverflow question includes sample code that anyone with a base R setup can run to reproduce what I was seeing
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
People love thorough bug reports. I'm not even kidding.
I'm again borrowing these from Facebook's Guidelines
- 2 spaces for indentation rather than tabs
- You can try running
npm run lintfor style unification
By contributing, you agree that your contributions will be licensed under its MIT License.
This document was adapted from the open-source contribution guidelines for Facebook's Draft
Summary of set up
- For development Visual Studio 2022 is recommended for development. VS Code will also work, but not as much advanced debugging.
- For use setup is simple as binaries are pre-compiled for ease and you can compile them yourself too if desired.
Configuration
- Library uses miminal footprint and depending on what you are doing with it will determine your needs. Memory tools are included.
Dependencies
- .Net Core 6. Core is available on all platforms (Win, Mac, Linux)
- LiteDB
- Newtonsoft.Json
- Repo owner or admin
- Other community or team contact
ArcherCore is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
This code was compiled from 12+ years of projects and random things. If you notice it is similar to something of yours please let me know and I will happily give you credit.
- LiteDB
- Newtonsoft.Json
- Starkbank for ECDSA Library
- Brian A. Danielak for Contribution Guidelines