So, i want to protect my IP (Intelectual Property), I spend days thinking of methods that do this and that and there is nothing i can do to hide that IL…

In short, the CLR has to execute this thing, and so can the deassembler and the free reflector decompiler, if not then there is always salamander.

Holy crap, Boomerang was useless when i wrote native, it was an excellent decompiler of X86 code, but X86 was much more complicated than IL (that i can comprehend without even decompiling) !

So, what options do i have ?

First, Revert back to C++ (Yes, this is where i will go as soon as i know i am master of C#) so that i dont feel left behind when they say i tell the GC to do this right after that and then bam, i reallocate the object blah on the microsoft heap…
A childish reason to hold off going back to C++ for some time, but then again, it is not just the bragging, i really want to know what is on the other side, especially with MONO around.

Second, See what automated tools exist for converting IL to C++ (Holy crap, you can do that), up to now i found a single tool that can do that and it is free…. Codeplex CorssNet, So my dreams of a factory precompiler could come true finally (But i have not tested it yet).

Third, Learn as much as possible about this new Phoenix from Micro$oft. it should have some answers !

See what options i have concerning obfuscators and put them here…

First, the free guys.

Or maybe i want to use the one that comes with my Visual Studio 2008

And taking a look at those non free obfuscators ! that i will resort as i look into them, putting the most note worthy first

To begin with, this is by no means a bad book, It can also take you there if you know any sort of Object oriented programming, or even if you code in a procedural language (C or PHP 4) for example, but surely if you are an OO programmer you can go faster.

I have always done C, C++, PHP, and i feel like i know a big bunch more, but really, the only ones i am really good at are the ones i mentioned here, Unless you like to call SQL a programming language you can consider them 4, And now i am at intermediate level C#.

C# is more like Java++ (I have a good idea about Java),but everything changes on the .NET when you code for efficiency and the like.

Our friend Andrew Troelsen does a lovely Job explaining things that you would otherwise google out, the questions that come to a long time developer’s mind are answered on the spot.

Some are criticizing the book for 2 reasons, the first is that it explains SQLDataSource rather than the new objectdatasource, Others criticize it for missing the cryptographic features in .NET (security and crytography namespaces), I agree with the 2 above fully, No doubt Andrew Troelsen should have explained those in Length.

As to all the other reviews i found online, I totally disagree, here are the points

–Takes 2 long to read

You are learning something new, C# is not small, what do you expect

–Expects you to already know Object Oriented

Not true, in chapter 4 one single page says, if you don’t know OO come back here after you finish chapter 5, and really, i think this is the best way to do it.

–I already do C# and i wanted to be updated, i only need 25% of this book

Really, he wasen’t targetting you alone as an audience, it did the job for you, you can go faster on what you already know, and he did the job fine for all other programmers of all sorts

–Useful but no advanced material. Bloated writing style

You can’t be serious, “the depth is limited and for those areas with which I was familiar, there was little new.” So it seems you are already master of C# why read this book ?

The book explains pleanty about new things in .NET 3.5, or is it that the sound of your own voice soothes you when you say “As a professional programmer”….

– Real hard topics (Understanding Object lifetime, Behind the scenes of Linq etc.) are more like touch and go type

It says PRO in the title, what do you expect… and i think the hard parts are explained in a very nice fashion

–Maybe a little disappointing the examples

The examples are simple and quick. the best kind i know

I don’t even understand how Microsoft can claim Virtual Machine running your code can be faster than native code, for one thing i know, if this is true then they have not put enough effort on the native compiler.

Easy, straight forward, if you want me to stay here, you need to give me means of pre-jitting my software at the factory before i ship, Not as the user installs !

IP, Speed, Compatibility, Support for those extra processor flags i learned to love, What’s wrong with you Microsoft !