VMProtect Software » Forum

It seems you don't need our software, because you can't even solve such a "simple problem" by yourself. I don't understand why you think that "Wpf App.exe" is a VMProtect project file. P.S. You still use wrong code here: <VMProtectInputFile>$(IntermediateOutputPath)$(AssemblyNam...

Just change PATH_TO_VMP_FILE to the full name of ".vmp" file created by GUI: <Target Name="VMProtectCompile" BeforeTargets="GenerateSingleFileBundle"> <PropertyGroup> <VMProtectCon>"C:\Program Files\VMProtect Demo\VMProtect_Con.exe"</VMProtectCon> <VMProtectI...

The build 1932 supports self-contained executables. Here is simple example of .csproj to protect compiled assembly before publishing in a single file: <Project Sdk="Microsoft.NET.Sdk"> ... <Target Name="VMProtectCompile" BeforeTargets="GenerateSingleFileBundle"> <Prope...

Admin wrote: ↑Wed Dec 27, 2023 11:20 am viewtopic.php?t=31481

That's exactly the answer I want to know, thank you so much!

1. Compile your application with MSVC (for example Test.sln for .NET Core 6.0). MSVC will create "Release\net6.0\Test.dll" and "Release\net6.0\Test.exe" 2. Publish your application with the " dotnet publish " command. It will create the folder "Release\net6.0\publ...

Admin wrote: ↑Sat Dec 16, 2023 7:51 pm It seems you still don't understand what I explained in other topic:
viewtopic.php?p=38412#p38412

I'm sorry, but I really don't understand how to use vmp to protect my dll file first, and then use vs 2022's built-in publisher to publish as a single file

Reference VMProtect.SDK Don't need if you don't use functions from SDK. And add [Obfuscation(Feature = "ultra", Exclude = false)] before the method After compilation, you can still see the source code using ILSpy or dnSpy After loading of your application in VMProtect you will see in the ...

I downloaded the latest version of vmp to try out Reference VMProtect.SDK And add [Obfuscation(Feature = "ultra", Exclude = false)] before the method After compilation, you can still see the source code using ILSpy or dnSpy Is it because the trial version does not provide protection functi...

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 DL...

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?

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 ...