Reputation:
I have seen many C# obfuscators, and they all need an assembly (.exe, .dll, etc.) Why isn't it possible to just obfuscate the source code? Like you can do with javascript for example: http://www.javascriptobfuscator.com
Upvotes: 4
Views: 1294
Reputation: 2796
I agree with @dystroy, in that you obfuscate what you release.
But to directly answer the question posed-- b/c so few people release C# code.
If you need to release C# code, AND you wish to obfuscate it, I recommend a one-two punch of:
Upvotes: 0
Reputation: 62248
It doesn't make any sense to obfuscate source code. That's because source code is shared for maintainance or experience sharing. That's why obfuscation targets deployable artifacts, like exe
or dll
...
In case of JavaScript
the code itself is deployable artifact, so for Java Script
it has a perfect meaning for intellectual property protection.
Upvotes: 4
Reputation: 382092
You obfuscate what you release to the customer, not what you have to keep clear so that you can maintain it.
You release javascript files, you obfuscate them (and keep the non obfuscated ones to maintain the application). So you have two sets of javascript files : the source and the released. If there was a distinct released compiled format, this would probably be the obfuscation target.
You release .class files, not .java files, so you obfuscate the .class.
You release exe, not c or c# files, so you obfuscate the exe.
Other concrete reasons :
Upvotes: 2