Created: Wednesday, 10 May 2017 10:47 | Written by Joseph Sewell | 5266 Hits |

Automating Xamarin Protection with Dotfuscator

This week, all eyes of the software community will be fixed on Microsoft's Build conference. Microsoft and its partners are set to announce new technologies and lay out their vision for the future of software development. Recent years have seen the narrative take a decidedly cross-platform approach. Visual Studio Code gives developers tools to create what they want no matter their OS of choice. .NET Core extends the reach of the popular .NET Framework to Mac and Linux. Finally, Xamarin, which was acquired by Microsoft in 2016, lets app developers write their app once, then publish it for Android, iOS, and Windows devices.

As a Visual Studio 2017 Premier Launch Partner, PreEmptive Solutions is pleased to announce, as part of Microsoft Build 2017, a new way to integrate Dotfuscator's protection into Xamarin apps. Read more ...

Created: Thursday, 23 February 2017 12:13 | Written by Bill Leach | 4415 Hits |

Building in the Cloud with Dotfuscator Community Edition

Most of our previous blogging about Dotfuscator Community Edition (CE) assumes you are doing local builds, or have a dedicated build server—but what if you want to use Dotfuscator CE within a distributed build system such as Visual Studio Team Services (VSTS) or Team Foundation Server (TFS) on-premises? Until now, you've had to do extra work to install and provision Dotfuscator CE on each build agent host in your pool. Now, we're pleased to announce a VSTS build extension for Dotfuscator CE, available in the VSTS Marketplace. It does the extra work for you, making it easy to get Dotfuscator CE into your distributed build.

Read more ...
Created: Thursday, 16 February 2017 12:23 | Written by Joseph Sewell | 14043 Hits |

Getting Started with Dotfuscator in Visual Studio 2017

PreEmptive Protection - Dotfuscator began life as the world's first .NET obfuscator; nearly fifteen years later, Dotfuscator has grown beyond just obfuscation to become the industry-standard .NET protection tool, able to protect your .NET applications against IP exposure, tampering, and unauthorized debugging.

We are pleased to announce that Visual Studio 2017 honors the tradition set by its predecessors and ships with a free copy of Dotfuscator Community Edition. Read more ...

Created: Wednesday, 16 November 2016 12:20 | Written by Sebastian Holst | 6717 Hits |

(Re) Introducing Dotfuscator Community Edition

The most widely used .NET obfuscator – and now, much more

This morning, as we readied our latest Dotfuscator Community Edition (CE) announcement, it struck me that this remarkable piece of software has a unique story to tell. A story that can’t be expressed in a feature table or change log.

Read more ...
Created: Tuesday, 16 August 2016 10:06 | Written by Bill Leach | 8726 Hits |

Using Dotfuscator Community Edition with Xamarin

Note: this document is deprecated. Please see Obfuscating Xamarin Applications with Dotfuscator for up to date instructions on obfuscating Xamarin applications.

We've previously blogged about Using Dotfuscator Professional with Xamarin Applications. We've also blogged about the recently added command line support for Dotfuscator Community Edition. Now it is time to put these two concepts together, and show how to make reverse-engineering your Xamarin application more difficult by integrating Dotfuscator Community Edition (CE) into your Visual Studio build process.

Read more ...
Created: Friday, 01 April 2016 10:33 | Written by Joseph Sewell | 13648 Hits |

Automate Your Builds with New CE Command Line Support

At Microsoft Build 2016, we introduced a new feature for Dotfuscator Community Edition (CE): command line support. This will allow you to integrate Dotfuscator into your automated build process, so that your builds and releases can automatically use Dotfuscator for obfuscation, tamper protection, usage tracking, and expiration. To help you get started, this post will walk through how to use the command line interface (CLI), as well as how to integrate it into MSBuild and Visual Studio for automated builds.

Read more ...
Created: Wednesday, 28 October 2015 11:36 | Written by Sebastian Holst | 8498 Hits |

.NET Native; what's it mean for obfuscation and Dotfuscator in particular

I recently got a question from a client asking why .NET Native (the process of transforming a .NET assembly into a native app to improve performance) did not also make products like Dotfuscator irrelevant. Here's my response (with personal details removed of course).

First, the .NET Native process is only applicable to Universal Apps distributed through a Microsoft marketplace. If you are developing .NET (using VS2015 or anything else) BUT are targeting anything other than a Universal App architecture - .NET Native does not apply – also, if you’re developing in F# - even if Universal - .NET Native does not apply.

Read more ...