.NET IL Code
-
What was MS thinking when they created The .NET Compiler ? Man , the .NET Exe file can be easily disassemble :( and Don't tell me about The Blah ,Blah Obfuscated Code , My Cat can crack it :-\ :~
I know nothing , I know nothing ...
This should be posted in the Lounge as it's not a C# question.
Dave
If this helped, please vote & accept answer!
Binging is like googling, it just feels dirtier. Please take your VB.NET out of our nice case sensitive forum.(Pete O'Hanlon)
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn) -
What was MS thinking when they created The .NET Compiler ? Man , the .NET Exe file can be easily disassemble :( and Don't tell me about The Blah ,Blah Obfuscated Code , My Cat can crack it :-\ :~
I know nothing , I know nothing ...
Stark DaFixzer wrote:
Man , the .NET Exe file can be easily disassemble
OK I'm gonna bite, which .net exe file?
ragnaroknrol The Internet is For Porn[^]
Pete o'Hanlon: If it wasn't insulting tools, I'd say you were dumber than a bag of spanners. -
What was MS thinking when they created The .NET Compiler ? Man , the .NET Exe file can be easily disassemble :( and Don't tell me about The Blah ,Blah Obfuscated Code , My Cat can crack it :-\ :~
I know nothing , I know nothing ...
Maybe they were thinking "this would be a nice way to get more support for 64bit" or maybe "this would make it easier to support new instruction sets in old programs without recompiling them" but if they were thinking that they should think again, it's true of course but they are still using the FP stack instead of SSE registers.
-
What was MS thinking when they created The .NET Compiler ? Man , the .NET Exe file can be easily disassemble :( and Don't tell me about The Blah ,Blah Obfuscated Code , My Cat can crack it :-\ :~
I know nothing , I know nothing ...
People that worry about their code being recompiled are worrying about the wrong things. I seriously doubt Apple would care if you managed to completely reverse engineer and steal there iStore for iTunes or whatever it is called because you would not be able to steal their market share or business model. And that, is what is important. Most software that can be thought of as needing real protection from decompiling can actually be protected by patents, trademarks, and DMCA suits.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me
-
This should be posted in the Lounge as it's not a C# question.
Dave
If this helped, please vote & accept answer!
Binging is like googling, it just feels dirtier. Please take your VB.NET out of our nice case sensitive forum.(Pete O'Hanlon)
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn) -
People that worry about their code being recompiled are worrying about the wrong things. I seriously doubt Apple would care if you managed to completely reverse engineer and steal there iStore for iTunes or whatever it is called because you would not be able to steal their market share or business model. And that, is what is important. Most software that can be thought of as needing real protection from decompiling can actually be protected by patents, trademarks, and DMCA suits.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me
-
Maybe they were thinking "this would be a nice way to get more support for 64bit" or maybe "this would make it easier to support new instruction sets in old programs without recompiling them" but if they were thinking that they should think again, it's true of course but they are still using the FP stack instead of SSE registers.
-
Thank you , My thought ( Would Lounge know what is the IL code ? )
I know nothing , I know nothing ...
Most would, but I get your point. It was more of a statement/comment than a question IMO, if meant as a question then the .NET Framework forum would have been the correct place. I didn't mean it personally hence not downvoting your post :thumbsup: [Edit: unlike others I see :sigh: )
Dave
If this helped, please vote & accept answer!
Binging is like googling, it just feels dirtier. Please take your VB.NET out of our nice case sensitive forum.(Pete O'Hanlon)
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn) -
Most would, but I get your point. It was more of a statement/comment than a question IMO, if meant as a question then the .NET Framework forum would have been the correct place. I didn't mean it personally hence not downvoting your post :thumbsup: [Edit: unlike others I see :sigh: )
Dave
If this helped, please vote & accept answer!
Binging is like googling, it just feels dirtier. Please take your VB.NET out of our nice case sensitive forum.(Pete O'Hanlon)
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)I didn't downvote, but there is a certain "lives-under-a-bridge waiting for goats" smell around the OP....
ragnaroknrol The Internet is For Porn[^]
Pete o'Hanlon: If it wasn't insulting tools, I'd say you were dumber than a bag of spanners. -
What was MS thinking when they created The .NET Compiler ? Man , the .NET Exe file can be easily disassemble :( and Don't tell me about The Blah ,Blah Obfuscated Code , My Cat can crack it :-\ :~
I know nothing , I know nothing ...
Is it really that different than disassembling a native executable? No matter what language it's in, or how it's compiled, it can be broken down and analyzed. My thoughts are, put a bit of money/effort in to disuade 'casual' disassemblers, and that's probably enough. Anyone who cares enough can crack any application.
-
What was MS thinking when they created The .NET Compiler ? Man , the .NET Exe file can be easily disassemble :( and Don't tell me about The Blah ,Blah Obfuscated Code , My Cat can crack it :-\ :~
I know nothing , I know nothing ...
More likely they were thinking that they should provide a unifying environment where you can write programs in a language of your choice, and get access to common features in the same way regardless of the language. This environment should be independent of the operating system and should provide a modern object oriented development experience. Obfuscation has never really been part of this roadmap, and is not really relevant to most corporate developments which value speed of development.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
People that worry about their code being recompiled are worrying about the wrong things. I seriously doubt Apple would care if you managed to completely reverse engineer and steal there iStore for iTunes or whatever it is called because you would not be able to steal their market share or business model. And that, is what is important. Most software that can be thought of as needing real protection from decompiling can actually be protected by patents, trademarks, and DMCA suits.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me
5!
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
-
What was MS thinking when they created The .NET Compiler ? Man , the .NET Exe file can be easily disassemble :( and Don't tell me about The Blah ,Blah Obfuscated Code , My Cat can crack it :-\ :~
I know nothing , I know nothing ...
Mushrooms! :-D
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
-
Is it really that different than disassembling a native executable? No matter what language it's in, or how it's compiled, it can be broken down and analyzed. My thoughts are, put a bit of money/effort in to disuade 'casual' disassemblers, and that's probably enough. Anyone who cares enough can crack any application.
Sir Dot Net wrote:
Is it really that different than disassembling a native executable?
Yes it is, you can't just Reflect a compiled C++ program and reproduce the source code the way you can with .NET IL.
Sir Dot Net wrote:
No matter what language it's in, or how it's compiled, it can be broken down and analyzed.
Indeed, but MS have made it particularly easy with .NET IL.
-
Sir Dot Net wrote:
Is it really that different than disassembling a native executable?
Yes it is, you can't just Reflect a compiled C++ program and reproduce the source code the way you can with .NET IL.
Sir Dot Net wrote:
No matter what language it's in, or how it's compiled, it can be broken down and analyzed.
Indeed, but MS have made it particularly easy with .NET IL.
-
Java's not a native executable, it's also intermediate code.
-
Mushrooms! :-D
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
Badger badger badger badger badger badger badger
-
Java's not a native executable, it's also intermediate code.
-
Are you here for the five minute argument or the full half hour? ;P