Comments
Sort by recent activity
james.billings wrote:
The profiler essentially uses IE to hook into your web service to profile it - so, in theory, you can start up the profiler with IE (as you did when it was working), minimize IE, and then work with your Winforms app. This should let you collect profiling data from the web service.
What you cannot do is profile the Winforms app and get profiling info from that AND the webservice together.
Works great.
Thanks / comments
james.billings wrote:
The profiler essentially uses IE to hook into your web service to profile it - so, in theory, you can start up the profiler with IE (as you did when it was working), minimi...
I have a fairly large project that brings in a large number of 3rd party assemblies. After obfuscation, I get error messages with funny character strings. These are likely related to messages with substituted strings.
I tried various Smart assembly options, to try and get my program to run after going through the tool. For example, I just reduced it to dependency merging and embedding and pruning and now my application no longer runs. Seems to be related to web service calls.
There must be a set of rules for exclusions that we can apply to ensure error messages are displayed properly. Any docs outlining best practices for obfuscation? / comments
I have a fairly large project that brings in a large number of 3rd party assemblies. After obfuscation, I get error messages with funny character strings. These are likely related to messages with ...