^* - an assembly resolver is given a logical assembly name, and attempts to find a file with that name, and an appropriate version.

I tried for a long time to provide you a single-file application, but my obfuscator produces unusable output. I am currently looking at .NET 8.0 Ahead-Of-Time compilation which results in small files and faster start-up, but causes problem with ASP.NET's use of reflection. Fingers crossed.

^* - an assembly resolver is given a logical assembly name, and attempts to find a file with that name, and an appropriate version.

I tried for a long time to provide you a single-file application, but my obfuscator produces unusable output. I am currently looking at .NET 8.0 Ahead-Of-Time compilation which results in small files and faster start-up, but causes problem with ASP.NET's use of reflection. Fingers crossed.

From a console (CMD, bash, PowerShell, cmder, Take Command, etc.) change to the directory where you installed the product, and type:

./DotNetExplorer [ --version -dr ] [ --help ] [ --urls="http://localhost:9000" ]

The square brackets are optional parameters:

• --version -dr prints the current version and does not run the Web server;
• --help prints some command-line options, mostly used for trouble-shooting; and
• --urls runs the Web server on port 9000 because you are already using 5000 yourself

Now open your favorite browser and navigation to http://localhost:5000 or whatever port the server says it is listening on.

The application will run in a trial mode until a purchased license is registered.

Note: R1 and R2 can be run from the command line, but are designed for inter-process communication with DotNetExplorer

The application is now compiled AoT, and this seems to have stemmed the gross number of false positives from major AV vendors. If you have any problems please drop me a note - thanks!