Merge pull request #266 from sunnamed434/get-rid-of-deps

Replace Serilog, Autofac, pocket and Microsoft.* dependencies

Author: sunnamed434

README.md

@@ -14,7 +14,7 @@ BitMono is a free, open-source C# obfuscator that was initially designed and int
 
 BitMono uses [AsmResolver][asmresolver] instead of [dnlib][dnlib] (which we used in the past) for handling assemblies. If you have questions or issues, please let us know [here][bitmono_issues]. Download the latest version of BitMono [here][bitmono_releases].
 
-You can also use BitMono as an engine to build custom obfuscators. It is built using dependency injection (DI) using [Autofac][autofac_repo] and follows the latest C# best practices.
+You can also use BitMono as an engine to build custom obfuscators. It is built using dependency injection (DI) with a lightweight custom container based on [MinIoC][minioc_repo] (we used [Autofac][autofac_repo] in the past) and follows the latest C# best practices.
 
 <p align="center">
 <img src="https://raw.githubusercontent.com/sunnamed434/BitMono/main/resources/images/preview/before-after.png"
@@ -187,6 +187,7 @@ Credits
 [bitmono_nuget_packages]: https://www.nuget.org/profiles/BitMono
 [bitmono_nuget_shield]: https://img.shields.io/nuget/v/BitMono.Core.svg
 [autofac_repo]: https://github.com/autofac/Autofac
+[minioc_repo]: https://github.com/pjc0247/minioffice.ioc
 [unityengine_mainpage]: https://unity.com
 [mono_mainpage]: https://www.mono-project.com
 

docs/source/developers/configuration.rst

@@ -2,7 +2,7 @@ Configuration
 =============
 
 Injecting Configuration(s) in Protection constructor.
-BitMono have such configuartions and all of them you can inject in your protection constructor:
+BitMono have such configurations and all of them you can inject in your protection constructor:
 
 - ProtectionSettings
 - CriticalsSettings
@@ -19,15 +19,15 @@ Here's example how to do that:
 		private readonly ProtectionSettings _protectionSettings;
 		private readonly CriticalsSettings _criticalsSettings;
 		private readonly ObfuscationSettings _obfuscationSettings;
-	
+
 		public MagicProtection(
-			IOptions<ProtectionSettings> protectionSettings,
-			IOptions<CriticalsSettings> criticalsSettings,
-			IOptions<ObfuscationSettings> obfuscationSettings,
-			IServiceProvider serviceProvider) : base(serviceProvider)
+			ProtectionSettings protectionSettings,
+			CriticalsSettings criticalsSettings,
+			ObfuscationSettings obfuscationSettings,
+			IBitMonoServiceProvider serviceProvider) : base(serviceProvider)
 		{
-			_protectionSettings = protectionSettings.Value;
-			_criticalsSettings = criticalsSettings.Value;
-			_obfuscationSettings = obfuscationSettings.Value;
-		}	
+			_protectionSettings = protectionSettings;
+			_criticalsSettings = criticalsSettings;
+			_obfuscationSettings = obfuscationSettings;
+		}
 	}

docs/source/developers/first-protection.rst

@@ -18,10 +18,10 @@ Create your protection in the ``BitMono.Protections`` namespace.
 	public class StandardProtection : Protection
 	{
 	    // Inject services right here
-	    public StandardProtection(IServiceProvider serviceProvider) : base(serviceProvider)
+	    public StandardProtection(IBitMonoServiceProvider serviceProvider) : base(serviceProvider)
 	    {
 	    }
-	
+
 	    public override Task ExecuteAsync()
 	    {
 	        // All protection are intended to be async, so you can simply await your things, or if you don't have,

docs/source/faq/disable-path-masking.rst

@@ -1,58 +1,11 @@
 How to disable path masking?
 ============================
 
-You're probably getting a message with the file/directory or just a path ``(***\things)``, and you might have the same folder twice somewhere, and you need to see the full path without masking if this is what you're looking for, all instructions how to do that are provided here.
+.. note::
 
-Open-up ``logging.json`` in the root of the downloaded BitMono, edit this file, and remove this:
+   Path masking was a feature in older versions of BitMono that used Serilog for logging.
+   Since BitMono now uses a lightweight custom logger, path masking is no longer applied by default.
 
-.. code-block:: json
+In current versions of BitMono, file paths are displayed in full without any masking. If you're seeing masked paths like ``(***\things)``, you may be using an older version of BitMono.
 
-	"Enrich": [
-            {
-                "Name": "WithSensitiveDataMasking",
-                "Args": {
-                    "options": {
-                        "MaskValue": "***\\",
-                        "MaskProperties": [ "path", "directory", "file" ],
-                        "MaskingOperators": [ "BitMono.Host.Extensions.PathMaskingOperator, BitMono.Host" ]
-                    }
-                }
-            },
-        ],
-
-
-So, after edit ``logging.json`` looks like this:
-
-.. code-block:: json
-
-	{
-	    "Serilog": {
-	        "Using": [
-	            "Serilog",
-	            "Serilog.Sinks.Console",
-	            "Serilog.Sinks.File",
-	            "Serilog.Sinks.Async",
-	            "Serilog.Enrichers.Sensitive"
-	        ],
-	        "WriteTo": [
-	            {
-	                "Name": "Async",
-	                "Args": {
-	                    "configure": [
-	                        {
-	                            "Name": "File",
-	                            "Args": {
-	                                "path": "logs/bitmono-{{date}}.log",
-	                                "outputTemplate": "[{Timestamp:yyyy-MM-dd HH:mm:ss} {Level:u3}][{SourceContext}] {Message:lj}{NewLine}{Exception}"
-	                            }
-	                        }
-	                    ]
-	                }
-	            }
-	        ],
-	        "Enrich": [
-	            "FromLogContext"
-	        ],
-	        "MinimumLevel": "Debug"
-	    }
-	}
+To get full path visibility, simply update to the latest version of BitMono from the `releases page <https://github.com/sunnamed434/BitMono/releases/latest>`_.

docs/source/usage/how-to-use.rst

@@ -247,8 +247,7 @@ After importing, your project will contain:
        ├── BitMono.CLI.exe                 # The actual obfuscation tool
        ├── protections.json                # Protection settings
        ├── obfuscation.json                # Obfuscation settings
-       ├── criticals.json                  # What not to obfuscate
-       └── logging.json                    # Logging configuration
+       └── criticals.json                  # What not to obfuscate
 
 Configuration
 ~~~~~~~~~~~~~