External Program Failed Msbuild.exe Return Code Was 1990Version history - Crypto Obfuscator For . Net. Version history - Crypto Obfuscator For. Net Build 1. 60. July 2. 01. 6 )Improved support for obfuscating VS 2. Improved documentation. Build 1. 60. 52. 0 ( 2. May 2. 01. 6 )Improved disgnostics. Slightly improved UI. Build 1. 60. 32. 2 ( 2. March 2. 01. 6 )NEW: Map files location now support environment variables. NEW: Support for multiple developers to consume and view exception report. IMPROVED: Improved obfuscation when using method encryption. FIX: Deep- integration of Crypto. Licensing failed in some circumstances when obfuscation assemblies built with VS 2. FIX: Encrypt Constants did not work in rare circumstances for assemblies compiled with VS 2. Build 1. 60. 11. 8 ( 0. January 2. 01. 6 )NEW: Added support for SHA2. Thank you for responding to my post. Upon starting the sick computer this morning, for the first time it would not connect to the Network via the ethernet cable. The message at the System Tray Icon was. From [email protected] on April 09, 2014 11:05:31 ** TODO dynamorio.dll imports . Creating library lib32\release\dynamorio.lib and object lib32\release\dynamorio.exp CMake Error at D:/derek/dr/git. Changes in Elements (Oxygene, C# and Swift) This document lists the changes introduced by new versions of Elements toolchain, including the Oxygene Language, RemObjects C#, Silver and Fire. New in the 'August 2016' Release. Athenticode signing. FIX: Fixed rare bug in 'Encrypt Constant Values/Arrays' when VS 2. IMPROVED: Improved logging if type resolution fails during obfuscation. IMPROVED: Improved support for exception reporting on some servers. Build 1. 50. 91. 8 ( 1. September 2. 01. 5 )NEW: Ability to generate different names for symbols during each obfuscation when using cryptographic renaming scheme. FIX: Obfuscation failed in rare circumstances for VS 2. Automatic Exception Reporting is turned on. Build 1. 50. 90. 5 ( 0. September 2. 01. 5 )NEW: Ability to specify additional pattern for matching in Exclusion/Inclusion Rules. Build 1. 50. 72. 9 ( 2. July 2. 01. 5 )NEW: Added support for PDBs generated by VS 2. Net 4. 6. NEW: Better support for array type attributes parameters when a null value is passed. Build 1. 50. 61. 9 ( 1. June 2. 01. 5 )Build 1. June 2. 01. 5 )NEW: Ability to pass any command- line parameter as parameter when invoking from MSBuild. Build 1. 50. 60. 5 ( 0. June 2. 01. 5 )NEW: Ability to turn off processing of satellite assemblies. NEW: Ability to pass/override all obfuscation settings and inputs via MSBuild properties. IMPROVED: Improved support for type arrays specified via attributes. NEW: The Exclusion/Inclusion Rules tab can now show only those tree nodes for which rules have been added. NEW: Exception. Handler. Send. Report. To. Service(byte. Build 1. November 2. 01. 4 )NEW: Exclusion/Inclusion rule patterns can now be matched against the attributes on the enclosing type as well as its entire hierarchy. Service Servers (Workers) 2 Dell R630 Servers, each with: Dual E5-2643 v3 Processors (6 cores @3.4–3.7GHz each) 64 GB of RAM (8x 8 GB DIMMs) 1 Dell R620 Server, with: Dual E5-2667 Processors (6 cores @2.9–3.5GHz each) 32. Sharing my tips, tricks, and code to help other developers be more productive. Build 1. 41. 10. 8 ( 0. November 2. 01. 4 )CHANGE: Updated exception reporting service code to use On. Upload. Report. Ex instead of On. Upload. Report. IMPROVED: Default exception reporting takes over if the custom exception handling code fails. Build 1. 41. 00. 2 ( 0. October 2. 01. 4 )Minor documentation updates. Build 1. 41. 00. 1 ( 0. October 2. 01. 4 )NEW: Ability to save full parameter type names in mapping file. NEW: Produces new names each time assemblies are obfuscated even if they are not changed. Build 1. 40. 92. 5 ( 2. September 2. 01. 4 )NEW: Ability to pass Exclusion/Inclusion Rules via the command line. NEW: Ability for the Exception Reporting service to store reports in a database instead of the file system. Build 1. 40. 91. 8 ( 1. September 2. 01. 4 )NEW: Ability to specify the mainassembly (in which dependant or additional assemblies are embedded) via the command- line. Build 1. 40. 91. 2 ( 1. September 2. 01. 4 )NEW: Ability to specify additional assemblies via command- line. Build 1. 40. 90. 8 ( 0. September 2. 01. 4 )Minor documentation updates. Build 1. 40. 90. 3 ( 0. September 2. 01. 4 )FIX: UI layout of Exclusion/Inclusion tab got messed up under some siutations. Build 1. 40. 82. 0 ( 2. August 2. 01. 4 )NEW: Ability to access the Report ID in the exception reporting service, when a new report is sent.
NEW: Ability to select a specific report automatically in the Exception Viewer Dialog by passing the report ID via the command- line. Minor UI improvements. Build 1. 40. 80. 8 ( 0. August 2. 01. 4 )NEW: Assemblies to obfuscate can now be specified via the command- line. FIX: Dependency assembly embedding failed to load assemblies at run- time in some circumstances. Build 1. 40. 70. 3 ( 0. July 2. 01. 4 )FIX: Error occurred in rare circumstances on some machines on which environment variables are not properly defined. Build 1. 40. 52. 8 ( 2. May 2. 01. 4 )Build 1. May 2. 01. 4 )Minor documentation updates. Build 1. 40. 42. 5 ( 2. April 2. 01. 4 )IMPROVED: Improved processing for certain assemblies with bad . Net metadata. Build 1. April 2. 01. 4 )Minor documentation updates. Build 1. 40. 41. 5 ( 1. April 2. 01. 4 )Build 1. April 2. 01. 4 )NEW: Ability to add the Debugger. Step. Through attribute to methods via Obfuscation attributes. CHANGE: Features specified via obfuscation attribute must have exact spelling; earlier, suffix mistakes like . Build 1. 31. 22. 5 ( 2. December 2. 01. 3)FIX: Improved exception reporting support for some Visual Basic projects. Build 1. 31. 22. 3 ( 2. December 2. 01. 3)CHANGE: Improved support for some Visual Studio project files when running the Visual Studio Project Integration Wizard. Build 1. 31. 21. 9 ( 1. December 2. 01. 3)FIX: Regression bug: deleting assemblies from obfuscation project files did not work. Build 1. 31. 21. 1 ( 1. December 2. 01. 3)NEW: Exclusion/Inclusion rules can now be applied at the namespace level. Minor UI improvements. Build 1. 31. 20. 4 ( 0. December 2. 01. 3)Minor documentation updates. Minor UI improvements. Build 1. 31. 20. 3 ( 0. December 2. 01. 3)NEW: Ability to add assemblies to the obfuscation project via drag- drop. NEW: Ability to suppress warnings via Obfuscation attributes or Exclusion/Inclusion Rules, both of which can be applied to methods, types or assemblies. Build 1. 31. 13. 0 ( 3. November 2. 01. 3)Minor documentation updates. Minor UI improvements. Build 1. 31. 11. 8 ( 1. November 2. 01. 3)Build 1. November 2. 01. 3)NEW: Improved auto- exclusion of API from renaming for WPF & Silverlight projects. Build 1. 31. 02. 4 ( 2. October 2. 01. 3)FIX: Inclusion/Exclusion Rules . Minor documentation updates. Build 1. 31. 01. 2 ( 1. October 2. 01. 3)NEW: Added support for key files which only specify public keys (for delay signing). NEW: Support for obfuscating . Net Micro Framework 4. Build 1. 31. 00. 2 ( 0. October 2. 01. 3)Build 1. September 2. 01. 3)Build 1. September 2. 01. 3)IMPROVED: You are first prompted to save an unsaved modified project if a MRU project is opened. FIX: If multiple properties of the same type are present in a class hierarchy and one of them is Read. Only/Write. Only, then . Instead. now, Crypto Obfuscator allows you to enable or disable automatic obfuscation of your assemblies via the Crypto Obfuscator UI using the Project menu - -> Enable Visual Studio Integration menuitem. Build 1. 30. 90. 4 ( 0. September 2. 01. 3)Minor UI improvements. Minor documentation updates. Build 1. 30. 83. 1 ( 3. August 2. 01. 3)Minor logging improvements. Minor documentation updates. Build 1. 30. 82. 8 ( 2. August 2. 01. 3)Build 1. August 2. 01. 3)Build 1. August 2. 01. 3)IMPROVED: Assemblies added to the obfuscation project are now shown in a listbox instead of a dropdown list box. Further, you can now select multiple assemblies from the listbox and easily change obfuscation settings. Build 1. 30. 81. 5 ( 1. August 2. 01. 3)Minor UI improvements. Minor documentation updates. Build 1. 30. 81. 2 ( 1. August 2. 01. 3)Build 1. August 2. 01. 3)NEW: Visual Studio Integration Wizard now presents a list of all available configurations which you can select. NEW: Visual Studio Integration Wizard now supports incremental integration - that is, you can run the wizard on your Visual Studio projects multiple times with different configurations or first/last projects. IMPROVED: Visual Studio Integration Wizard now checks any error conditions before starting the modification of project files - this gives you a chance to remedy the errors before proceeding in the wizard, instead of having to restart the wizard from start. Build 1. 30. 80. 2 ( 0. August 2. 01. 3)NEW: Inclusion Exclusion Rules Tab allows you to exclude or include symbols from any obfuscation setting, visually via a easy- to- use UI based hierarchical view. Advanced matching criteria are supported. IMPROVED: Various optimizations to improve speed of obfuscation a bit. Build 1. 30. 73. 1 ( 3. July 2. 01. 3)NEW: Dependant Assembly Embedding is now supported for . Net 1. 0/1. 1 assemblies also. Build 1. 30. 72. 3 ( 2. July 2. 01. 3) - ** v. R2 **Version bumped to Crypto Obfuscator For . Net v. 20. 13 R2. These code patterns are replaced by method calls which do the exact same thing, but whose purpose is not as easy to understand as the original code pattern. Build 1. 30. 71. 8 ( 1. July 2. 01. 3)NEW: Environment variables can now be used inside the Build. ID. NEW: Build. ID can now use a special environment variable of the form %assemblyname. FIX: Exclusions for features other then . Build 1. 30. 62. 8 ( 2. June 2. 01. 3)IMPROVED: Members of enums which are marked as Serializable are not renamed. Build 1. 30. 62. 4 ( 2. June 2. 01. 3)NEW: Added ability to exclude fields/properties/methods/events by type. IMPROVED: Added some minor details to the log. NEW: Added support for scenario where a Portable Class Library is referenced by the assembly being obfuscated. Minor documentation updates. Build 1. 30. 62. 0 ( 2. June 2. 01. 3)FIX: Fixed layout issues with Visual Studio Project Integration Wizard, which causes the . Build 1. 30. 61. 4 ( 1. June 2. 01. 3)NEW: Ability to explicitly specify an assembly added to the obfuscator project as a Win. RT assembly. FIX: . Build 1. 30. 40. 4 ( 0. April 2. 01. 3)IMPROVED: More helpful error messages if obfuscation errors occur. Build 1. 30. 40. 3 ( 0. April 2. 01. 3)NEW: Added support for . IMPROVED: Improved usability of the Crypto Obfuscator Visual Studio Add- In. The menu command added by the add- in now changes text - . NEW: Added support for deobfuscated stack traces generated by Unity. D. Build 1. 30. 32. March 2. 01. 3)IMPROVED: Improved reporting of errors/exceptions that occur in the exception reporting service back to the Crypto Obfuscator UI.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |