Yes, obfuscation will help, a little, with the code in C#, VB, etc.,
but not at the CLR level.
This is the same thing I remember from olden days where companies
thought they could "hide" code. In the olden days all you needed
was one developer with some assembler know-how. With .Net, you
just need one developer with some CLR know-how.
So even if you try some obfuscation tool on your code, it won't
be "hidden" or "secret". Someone could still just look at the
"raw" code to see what it does.
If anyone thinks their code is really great, unique, etc., their
only option is a software patent.
<soapbox>
<action type="get on">
</soapbox>
Thankfully, software patents are not accepted in the EU, I hope
the USA sees the light as well and blocks software patents.
Software is nothing more than instructions, just like a recipe
is nothing more than instructions. In the USA you cannot patent
instruction for a recipe (which many fortune 1,000 companies
would love to have, and have bribed^h^h^ paid to try to get), yet
you _can_ patent instructions for a computer?
<soapbox>
<action type="get off">
</soapbox>
Thanks, I will be here all week, please tip the bartender.
Sorry for the top post!
On Tue, Apr 7, 2009 at 12:05 AM, santhosh vs <[email protected]> wrote:
> and about the code hiding yes astro was right, but you can use obfuscation
> tools to make the refactoring difficult. The technique you used will decide
> the complexity and he may drop refactoring in the middle :) There are free
> tools also for obfuscation
>
> On Mon, Apr 6, 2009 at 8:58 PM, santhosh vs <[email protected]> wrote:
>>
>> Yes i was telling the same, the suggession of fruitman to create a
>> classlibrary.
>> I thought u may get what i told.I think now its clear with his points.
>>
>> On Mon, Apr 6, 2009 at 11:03 AM, AstroDrabb <[email protected]> wrote:
>>>
>>> You can do as other have pointed out. However, there is no way to really
>>> "hide" your .Net code. Any developer can disassemble the compiled code and
>>> recreate it.
>>>
>>> Just do a Google search:
>>> http://www.google.com/search?q=.net+disassembler
>>>
>>> MS gives developers their own disassembler and there are other really
>>> good ones out there too.
>>>
>>> If you have "top secret" code that you do not want someone to USE without
>>> permission, use a license agreement to restrict the usage of your code.
>>> There is really no other good way to protect your source code.
>>>
>>>
>>> On Mon, Apr 6, 2009 at 1:55 AM, sara <[email protected]> wrote:
