NuGet Configuration =================== You only need this if you hit dependency errors while using BitMono as a NuGet package. BitMono sometimes pulls a nightly build of AsmResolver (when we need a critical fix that isn't on nuget.org yet), and those live on Washi's feed, not the default one. If NuGet can't resolve AsmResolver, point it at that feed too. Add a ``NuGet.config`` to your project root: .. code-block:: xml Then restore: .. code-block:: bash dotnet restore That's it, AsmResolver should resolve now. The packages ------------ Most people only ever need one of these: - `BitMono.Integration `_ - obfuscate your project on every build by adding one ````. See :doc:`msbuild-integration`. - `BitMono.GlobalTool `_ - the BitMono CLI as a .NET global tool (``dotnet tool install --global BitMono.GlobalTool``). See :doc:`how-to-use`. The rest are the engine packages, for building your own tools on top of BitMono (see :doc:`../developers/configuration`): - `BitMono.API `_ - core interfaces and abstractions - `BitMono.Core `_ - the obfuscation engine - `BitMono.Protections `_ - the protection implementations - `BitMono.Shared `_ - shared utilities and models - `BitMono.Host `_ - application host framework - `BitMono.Utilities `_ - helper functions - `BitMono.Obfuscation `_ - high-level obfuscation orchestrator - `BitMono.Runtime `_ - runtime components for obfuscated assemblies