.NET Code Easy to Disassemble
-
Hey guys, This is the Ultimatum of a thread i post yesterday and is gone back in pages anyway. This was about .NET transparent code, and at first thought realised that .NET was not suitable for commercial software. I JUST WANT YOU TO READ MY NEW POINT OF VIEW!!! I have to tell you, i have been thinking and commercial software means you buy a software and that software is yours, 100% yours and that should mean that source code should be included to do whatever you want with it cause now it's your property. But this doesn't apply to MS products, i haven't seen a bit of Windows src included rather than API methods calls in my apps. Anyway it's an example. If we analyse it from the moral & etical point of view, it's right to include sources to commercial software. But users should be responsible from what they do with it. MS .NET provides an easy way of deployment for the people who wants to play with the sources. So i'm glad the way .NET works and if any of you are going to develop a commercial app then copyright it and apply all the legal stuff to it. So if you find your software cracked or ilegally modified you can theorically apply legal penalties to the cracker or whatever you wan't to call the victim. I didn't know that the fast and "secure" C++ native code could be disassembled and watch code the same way it was written, so any programming language can be disassembled, that means all the languages are at the same level but something i'm sure about is .NET rocks and is the way to go man! Best regards, Heinz
-
Hey guys, This is the Ultimatum of a thread i post yesterday and is gone back in pages anyway. This was about .NET transparent code, and at first thought realised that .NET was not suitable for commercial software. I JUST WANT YOU TO READ MY NEW POINT OF VIEW!!! I have to tell you, i have been thinking and commercial software means you buy a software and that software is yours, 100% yours and that should mean that source code should be included to do whatever you want with it cause now it's your property. But this doesn't apply to MS products, i haven't seen a bit of Windows src included rather than API methods calls in my apps. Anyway it's an example. If we analyse it from the moral & etical point of view, it's right to include sources to commercial software. But users should be responsible from what they do with it. MS .NET provides an easy way of deployment for the people who wants to play with the sources. So i'm glad the way .NET works and if any of you are going to develop a commercial app then copyright it and apply all the legal stuff to it. So if you find your software cracked or ilegally modified you can theorically apply legal penalties to the cracker or whatever you wan't to call the victim. I didn't know that the fast and "secure" C++ native code could be disassembled and watch code the same way it was written, so any programming language can be disassembled, that means all the languages are at the same level but something i'm sure about is .NET rocks and is the way to go man! Best regards, Heinz
Heinz Suez wrote: i have been thinking and commercial software means you buy a software and that software is yours, 100% yours and that should mean that source code should be included to do whatever you want with it cause now it's your property. No, it's not. You bought a license to USE the software, not own it. The code is NOT yours. In most EULA's, you're expressly forbidden to reverse engineer the executable code to come up with anything resembling the source code. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
Hey guys, This is the Ultimatum of a thread i post yesterday and is gone back in pages anyway. This was about .NET transparent code, and at first thought realised that .NET was not suitable for commercial software. I JUST WANT YOU TO READ MY NEW POINT OF VIEW!!! I have to tell you, i have been thinking and commercial software means you buy a software and that software is yours, 100% yours and that should mean that source code should be included to do whatever you want with it cause now it's your property. But this doesn't apply to MS products, i haven't seen a bit of Windows src included rather than API methods calls in my apps. Anyway it's an example. If we analyse it from the moral & etical point of view, it's right to include sources to commercial software. But users should be responsible from what they do with it. MS .NET provides an easy way of deployment for the people who wants to play with the sources. So i'm glad the way .NET works and if any of you are going to develop a commercial app then copyright it and apply all the legal stuff to it. So if you find your software cracked or ilegally modified you can theorically apply legal penalties to the cracker or whatever you wan't to call the victim. I didn't know that the fast and "secure" C++ native code could be disassembled and watch code the same way it was written, so any programming language can be disassembled, that means all the languages are at the same level but something i'm sure about is .NET rocks and is the way to go man! Best regards, Heinz
If you are making a customized software for a particular customer, it is alright to give him the source code. But, when you are launching it as a generalized product to a large number of people, disclosing source code may not be desirable and is not necessary as a legal requirement. Even as per the moral requirements, it is not necessary because what will a common or lay customer do with your source code? He is simply a user of the product and that too one of a large number of users. But, your rivals will definitely benefit. Of course, if your target group is the open-source, you may very well disclose your source code. So, unless it is a customized software made for a particular customer only, a commercial application need not disclose source code. In today's cut-throat competition, it may not be advisable. So, disclosing source code of a commercial application may be injurous to your financial health. Heinz Suez wrote: But this doesn't apply to MS products, i haven't seen a bit of Windows src included rather than API methods calls in my apps. In some cases, even MS is also disclosing its source code, e.g., in MFC classes. Even for the .NET classes, you can see the code of the relevant dll files of MS, using the same ILDASM as for your code. Heinz Suez wrote: So i'm glad the way .NET works and if any of you are going to develop a commercial app then copyright it and apply all the legal stuff to it. So if you find your software cracked or ilegally modified you can theorically apply legal penalties to the cracker or whatever you wan't to call the victim. Legal processes are lengthy and costly. You may not be able to enforce your rights. Moreover, in an international scenario, enforcing legal copyrights becomes very difficult or almost impossible. Even a big corporation like MS has to live with a high level of piracy as the legal processes are not always productive or feasible. Regards, Ashok Dhamija _____________________________ Padam Technologies
-
Heinz Suez wrote: i have been thinking and commercial software means you buy a software and that software is yours, 100% yours and that should mean that source code should be included to do whatever you want with it cause now it's your property. No, it's not. You bought a license to USE the software, not own it. The code is NOT yours. In most EULA's, you're expressly forbidden to reverse engineer the executable code to come up with anything resembling the source code. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
If you are making a customized software for a particular customer, it is alright to give him the source code. But, when you are launching it as a generalized product to a large number of people, disclosing source code may not be desirable and is not necessary as a legal requirement. Even as per the moral requirements, it is not necessary because what will a common or lay customer do with your source code? He is simply a user of the product and that too one of a large number of users. But, your rivals will definitely benefit. Of course, if your target group is the open-source, you may very well disclose your source code. So, unless it is a customized software made for a particular customer only, a commercial application need not disclose source code. In today's cut-throat competition, it may not be advisable. So, disclosing source code of a commercial application may be injurous to your financial health. Heinz Suez wrote: But this doesn't apply to MS products, i haven't seen a bit of Windows src included rather than API methods calls in my apps. In some cases, even MS is also disclosing its source code, e.g., in MFC classes. Even for the .NET classes, you can see the code of the relevant dll files of MS, using the same ILDASM as for your code. Heinz Suez wrote: So i'm glad the way .NET works and if any of you are going to develop a commercial app then copyright it and apply all the legal stuff to it. So if you find your software cracked or ilegally modified you can theorically apply legal penalties to the cracker or whatever you wan't to call the victim. Legal processes are lengthy and costly. You may not be able to enforce your rights. Moreover, in an international scenario, enforcing legal copyrights becomes very difficult or almost impossible. Even a big corporation like MS has to live with a high level of piracy as the legal processes are not always productive or feasible. Regards, Ashok Dhamija _____________________________ Padam Technologies
Thanx for your comments, i agree in all you said. I'm developing a commercial app for a huge crowd, and i have got competition and people who hates me so i asume that there will be a cracked version or something that smells around the net only to take me down. But it's part of the normal process, as you said MS has to deal with that i'll have to deal with it too but it's going to hurt more. Thanx for your help and lets face the reality.