Comments
Sort by recent activity
No, I'm afraid it's not done yet, I'll try to remeber to let you know when it is.
The version 6 eaps each start a new 14 day trial for you to use, so you shouldn't have to worry about your trial expiring while you're using them. / comments
No, I'm afraid it's not done yet, I'll try to remeber to let you know when it is.
The version 6 eaps each start a new 14 day trial for you to use, so you shouldn't have to worry about your trial ex...
I like to keep the information that they must be excluded from obfuscation in the code, where you can see it if you add, for example, another element to the enum, or another similar enum. You won't forget to exclude it from obfuscation then. / comments
I like to keep the information that they must be excluded from obfuscation in the code, where you can see it if you add, for example, another element to the enum, or another similar enum. You won't...
Looks like the property grid reads the names of something that has been obfuscated (enum members it looks like) by reflection.
Obfuscators can't guarantee to preserve behaviour when reflection is used, of course.
You can either exclude it from obfuscation using the SmartAssembly project settings, or I prefer using attributes: http://www.red-gate.com/supportcenter/C ... .5/toc.htm / comments
Looks like the property grid reads the names of something that has been obfuscated (enum members it looks like) by reflection.
Obfuscators can't guarantee to preserve behaviour when reflection is u...
The second AppManifest was a workaround to a bug in the zipping library that we use. It's harmless and small, so we won't fix it unless the zipping library's underlying bug is fixed.
We're considering removing the fake metadata stream feature altogether because it doesn't provide any protection against the people that matter (crackers and people who want your intellectual property), it only ever stopped the casual observer (usually the developer) seeing inside the assembly. / comments
The second AppManifest was a workaround to a bug in the zipping library that we use. It's harmless and small, so we won't fix it unless the zipping library's underlying bug is fixed.
We're consider...
Should be fixed now, thanks again for the report. / comments
Should be fixed now, thanks again for the report.
Thanks a lot for the report, we've been migrating a server, and something seems to have gone wrong. We'll get it fixed as soon as possible. / comments
Thanks a lot for the report, we've been migrating a server, and something seems to have gone wrong. We'll get it fixed as soon as possible.
Reflector does make use of a temporary executable during it's automatic update process.
The fact that you are seeing this problem even when you have not used Reflector, and your antivirus is giving you messages frequently rather than just when you ask Reflector to auto-update, suggests that you have a virus that doesn't have anything to do with Reflector. / comments
Reflector does make use of a temporary executable during it's automatic update process.
The fact that you are seeing this problem even when you have not used Reflector, and your antivirus is giving...
You'll be glad to know that the self-deletion behaviour was removed a while ago, and the remaining versions that do it will ask to update tomorrow, so if you update tomorrow, you'll never see it again. / comments
You'll be glad to know that the self-deletion behaviour was removed a while ago, and the remaining versions that do it will ask to update tomorrow, so if you update tomorrow, you'll never see it ag...
The trail will start after the first decompilation in version 6.5, as we noticed that some people got into the same situation as you. If you have been using 6.1, getting the latest version will give you a new trial.
If not, get in touch with sales, and they should be able to help you. / comments
The trail will start after the first decompilation in version 6.5, as we noticed that some people got into the same situation as you. If you have been using 6.1, getting the latest version will giv...
The target runtime is a different thing to the target framework. When you have a target framework of 3.5 in VS, you're asking for a target runtime of 2.0 and to reference the 3.5 framework assemblies (like system.core).
Reflector is showing you exactly what is in your assembly.
If you want to know whether something has a target framework of 2.0 or 3.5, you need to look at the assemblies it references. / comments
The target runtime is a different thing to the target framework. When you have a target framework of 3.5 in VS, you're asking for a target runtime of 2.0 and to reference the 3.5 framework assembli...