Unable to protect single file in .net 8

Issues related to VMProtect
Post Reply
howze
Posts: 11
Joined: Thu Dec 07, 2023 9:55 am

Unable to protect single file in .net 8

Post by howze »

I'm testing the product features of vmp to evaluate if it meets my needs, but I'm running into a problem.

Use .net 8 and vs 2022 to generate a single file and use the latest version of vmp to protect it. The protected program cannot run and there is no error message.

I don't provide the source code because you can reproduce the problem as follows:
1. Simply write a Hello World WPF application
2. When publishing, select self-contain and single file
3. Protect the generated application
You will find that the protected file cannot be started
Admin
Site Admin
Posts: 2586
Joined: Mon Aug 21, 2006 8:19 pm
Location: Russia, E-burg
Contact:

Re: Unable to protect single file in .net 8

Post by Admin »

You have to protect your application before publishing.
howze
Posts: 11
Joined: Thu Dec 07, 2023 9:55 am

Re: Unable to protect single file in .net 8

Post by howze »

Admin wrote: Thu Dec 07, 2023 11:20 am You have to protect your application before publishing.
It seems that I can only protect it by adding markers in the code, and cannot directly protect it using the GUI version of VMP.
Is VMP designed to not directly protect single files in. net 8, or will this feature be added in the future?
Admin
Site Admin
Posts: 2586
Joined: Mon Aug 21, 2006 8:19 pm
Location: Russia, E-burg
Contact:

Re: Unable to protect single file in .net 8

Post by Admin »

Your published application is just a container with required files of your application, so any modifications of this container will not protect your real code inside it. Just look at your application before publishig - usually it contains 2 files: EXE (required environment to execute dotnet) and DLL (your real code). The publishing process just merges 2 files into one, that's all.
howze
Posts: 11
Joined: Thu Dec 07, 2023 9:55 am

Re: Unable to protect single file in .net 8

Post by howze »

Admin wrote: Fri Dec 08, 2023 2:31 am Your published application is just a container with required files of your application, so any modifications of this container will not protect your real code inside it. Just look at your application before publishig - usually it contains 2 files: EXE (required environment to execute dotnet) and DLL (your real code). The publishing process just merges 2 files into one, that's all.
Thank you
Post Reply