tag:blogger.com,1999:blog-4011252463639388552.post5422192721503020863..comments2024-03-20T14:03:01.388-04:00Comments on JTB World Blog: Software Licensing and Protection Services from MicrosoftJTB Worldhttp://www.blogger.com/profile/02249678064305703202noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4011252463639388552.post-35581060028027294972008-08-02T07:59:00.000-04:002008-08-02T07:59:00.000-04:00Restored commentby AnonymousI just wanted to add a...Restored comment<BR/>by Anonymous<BR/>I just wanted to add a few words on a) the role of the "code protection" technology now offered by MSFT and b) the integration of both the security and licensing technology inside Dotfuscator (the PreEmptive obfuscator that you reference.<BR/><BR/>The secure virtual machine (SVM) approach taken by MSFT is very secure - but like any strong medicine - it comes with side-effects and counter-indications. Before I continue - i want to state that we are using code protector on some of our commercial software - this is not a negative post by any measure - this is more like what you might find on the label of your pharma prescription.<BR/><BR/>Targeted .NET frameworks (compact, silverlight 1.1), SQL server .NET extensions and other specialized runtime environments may pose special challenges. The runtime translation of code essentially transforms bytecode into an interprested language. This can result in material performance implications and should be monitored. One last example, programming techniques such as reflection and the use of generics may pose additional restrictions.<BR/><BR/>In short, code protector is a very secure solution that - when appropriate - will serve a developer well.<BR/><BR/>On the integration within Dotfuscator...<BR/><BR/>The result of this integration is that custom attributes (or a Visual Studio GUI) can target obfuscation transforms, code protection transforms, Microsoft licensing logic and PreEmptive application analytics in any combination and on any one or combination of methods. So - Dotfuscator could be used to instrument MSFT code protection via Visual Studio without obfuscation or any of the other capabilities Dotfuscator has been traditionally known for. The premise is that a blend of obfuscation and code protection provides the maximum protection with the fewest limitations or constraints.<BR/><BR/>This approach also simplifies a scenario where a development group might want to iteratively include and adjust protection, analytics, and licensing options.JTB Worldhttps://www.blogger.com/profile/02249678064305703202noreply@blogger.com