DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Coding
  3. Languages
  4. .NET Decompilation is Common: Be Aware

.NET Decompilation is Common: Be Aware

Denzel D. user avatar by
Denzel D.
·
Dec. 26, 11 · Interview
Like (0)
Save
Tweet
Share
4.89K Views

Join the DZone community and get the full member experience.

Join For Free

A while ago I ran a poll asking .NET developers whether they reverse engineer applications that weren't created by them. The results were predictable, and from 110 total votes we got, 84 were cast for yes. As I mentioned before, .NET decompilation is extremely easy in multiple situations where developers do not obfuscate their code. Whether you want it or not, but if no precautions are taken, your code will most likely be torn apart.

I should mention, that code reflection is not a bad thing. Despite the common misconception, disassembling other's code has educational value. If you were developing with the .NET platform at least a year, you probably peeked at existing Microsoft .NET assemblies at least once. It is a great way to see how a re-usable codebase is built. It also allows (in very seldom cases) to see how existing framework code can be optimized and adapted to a specific task.

But does this mean that .NET code is not secure and should not be used for applications that have sensitive elements integrated in their source? No. Are there any solutions that can reduce the chances of your source code being disassembled? Yes.

The answer is obfuscation. Here are some resources that might help you learn more about obfuscation:

  • CLR and .NET Security - Obfuscation
  • Thwart Reverse Engineering of Your Visual Basic .NET or C# Code
  • Best .NET obfuscation tools/strategy
  • .NET Obfuscation using Dotfuscator for Source Code Protection

Obfuscation, however, is not a completely bulletproof solution. At the end of the day, there is always going to be a slight risk with your code being decompiled, whether it is written in managed or native code. Decompilers exists even for obfuscated code.

.NET

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Best Practices to Succeed at Continuous AWS Security Monitoring
  • ChatGPT: The Unexpected API Test Automation Help
  • Image Classification With DCNNs
  • Last Chance To Take the DZone 2023 DevOps Survey and Win $250! [Closes on 1/25 at 8 AM]

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: