Closed CptObviousDuh closed 9 years ago
Hi, You could just put that dll near your application without including it in the protections.
Yes that would be possible, but I'd like to keep my 1-file solution, due to it's simplicity (easy to deliver, easy to move on disk etc.) Is there a way to support this use case?
ConfuserEx only need that dll to analyze your application; if you had embedded the dll into your exe, you don't need to keep the dll when you release the application.
This works, thank you! :) I found a problem which resulted out of this, but I will open a new issue for that, this one is solved.
I'm using MvvmLight (5.0.2) in my WPF application and have therefore embedded the GalaSoft.MvvmLight.dll as an embedded resource, so that there's only one needed file.
When I try to apply the protection with ConfuserEx v0.5.0 I get the following error:
I wouldn't even care if this dll could not be protected, but due to that error the whole application fails.