Skip to content

WPF Renaming producing broken modules when protecting more than one exe at once #105

@ElektroKill

Description

@ElektroKill

When I protect these modules using ConfuserEx(2.0 branch). One always ends not working. I suspect its due to the renaming of paths.

In one of the modules the paths do not match and the module doesn't start:
image

In the second module, the paths match and it starts:
image

The next interesting thing is that both of the modules have the same path in the entry point: ourbopoogrdveenjzkwpafdlxojra.xaml

Here are the applications I am using:
Apps.zip

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions