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.
According to NIST’s National Vulnerability Database, six vulnerability categories have grown from 68% to over 84% of the total number of reported vulnerabilities in just the past four years.
Beginning with Dotfuscator Professional Edition version 4.25, you've been able to add anti-debug protections to your .NET applications, and now that Visual Studio 2017 has shipped, Dotfuscator Community Edition (CE) users have access to those protections as well.
Let's take this occasion to talk more about these new capabilities and walk through an example using both Pro and CE. Along the way, we will outline some patterns for implementation.
My earlier post, (RE) INTRODUCING DOTFUSCATOR COMMUNITY EDITION, introduced new functionality (command line interface) and updated our vision for how we hoped Dotfuscator CE adoption would evolve.
This update looks back at Dotfuscator CE adoption in 2016 and introduces the latest functionality included with the Visual Studio 2017 version.
As I read the article:
Car Makers Haven’t Learned: Insecure Apps Expose Millions Of Connected Cars To Theft, Risks. I was reminded (again) that an issue for IoT devices is that their manufacturers have been slow to implement security for the software that runs on them. The focus has been on getting them out as quickly and as inexpensively as possible.
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.
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.
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.