Things to do before making a .Net application commercial.
-
I have created a application in .Net for remote desktop connection and it is working fast and secure also, but for some reason i am not satisfied with the User Interface so just decided to rewrite the code again from the beginning. ;) But the problem came with the security from the hacker,cracker. yeah i know that .Net app can be easily de compiled so obstruced the code and declared all the class as not inheritable so that they can't import the app and create a object for the some important class and understand the algorithm or working behind it. Is there any other thing i am missing :doh: Can give any suggestion for the UI or features. One More Question: Should i kill features for the shake of UI.(i think i should kill features).
-
I have created a application in .Net for remote desktop connection and it is working fast and secure also, but for some reason i am not satisfied with the User Interface so just decided to rewrite the code again from the beginning. ;) But the problem came with the security from the hacker,cracker. yeah i know that .Net app can be easily de compiled so obstruced the code and declared all the class as not inheritable so that they can't import the app and create a object for the some important class and understand the algorithm or working behind it. Is there any other thing i am missing :doh: Can give any suggestion for the UI or features. One More Question: Should i kill features for the shake of UI.(i think i should kill features).
kburman6 wrote:
i am not satisfied with the User Interface so just decided to rewrite the code again from the beginning.
You're building a new house, because you did not like the way the old one is painted? :)
kburman6 wrote:
But the problem came with the security from the hacker,cracker. yeah i know that .Net app can be easily de compiled so obstruced the code and declared all the class as not inheritable
"NotInheritable" is meant as a code-construction that helps during development, not as a means to stop hackers. Open up ILSpy, load your assembly, copy and paste.
kburman6 wrote:
One More Question: Should i kill features for the shake of UI.(i think i should kill features).
Dunno, how many have you got? How many would your users want? If the app is becoming too complex for the average user, then hide some of the features under an "Advanced" tab or button.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
kburman6 wrote:
i am not satisfied with the User Interface so just decided to rewrite the code again from the beginning.
You're building a new house, because you did not like the way the old one is painted? :)
kburman6 wrote:
But the problem came with the security from the hacker,cracker. yeah i know that .Net app can be easily de compiled so obstruced the code and declared all the class as not inheritable
"NotInheritable" is meant as a code-construction that helps during development, not as a means to stop hackers. Open up ILSpy, load your assembly, copy and paste.
kburman6 wrote:
One More Question: Should i kill features for the shake of UI.(i think i should kill features).
Dunno, how many have you got? How many would your users want? If the app is becoming too complex for the average user, then hide some of the features under an "Advanced" tab or button.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
Eddy Vluggen wrote: You're building a new house, because you did not like the way the old one is painted? Actually, the house has wrong things in wrong places which could not be done by just shifting the rooms. :( Eddy Vluggen wrote: "NotInheritable" is meant as a code-construction that helps during development, not as a means to stop hackers. Open up ILSpy, load your assembly, copy and paste I have put a method
verify(apikey,secret)
with which you can activate every class and without it nothing will work. It may be seen as constructor method. Eddy Vluggen wrote: Dunno, how many have you got? How many would your users want? If the app is becoming too complex for the average user, then hide some of the features under an "Advanced" tab or button. Hmm, that is good point :thumbsup:
-
I have created a application in .Net for remote desktop connection and it is working fast and secure also, but for some reason i am not satisfied with the User Interface so just decided to rewrite the code again from the beginning. ;) But the problem came with the security from the hacker,cracker. yeah i know that .Net app can be easily de compiled so obstruced the code and declared all the class as not inheritable so that they can't import the app and create a object for the some important class and understand the algorithm or working behind it. Is there any other thing i am missing :doh: Can give any suggestion for the UI or features. One More Question: Should i kill features for the shake of UI.(i think i should kill features).
kburman6 wrote:
compiled so obstruced the code and declared all the class as not inheritable
You can always obfuscate your code by using an Obfuscator tool. This will help reduce the risk of someone decompiling your code.
WP Apps - Color Search | Arctic | XKCD | Sound Meter | Speed Dial
-
kburman6 wrote:
compiled so obstruced the code and declared all the class as not inheritable
You can always obfuscate your code by using an Obfuscator tool. This will help reduce the risk of someone decompiling your code.
WP Apps - Color Search | Arctic | XKCD | Sound Meter | Speed Dial
Thanks But little bit scared because Obfuscator only change the names of methods,class,var to some random name.Means still can be decompiled and a very curious person can understand it. And one more thing
Dim password as String ="sometxt"
sometxt can still be seen in memory dump of process is there any way to hide.
-
Thanks But little bit scared because Obfuscator only change the names of methods,class,var to some random name.Means still can be decompiled and a very curious person can understand it. And one more thing
Dim password as String ="sometxt"
sometxt can still be seen in memory dump of process is there any way to hide.
-
Thanks But little bit scared because Obfuscator only change the names of methods,class,var to some random name.Means still can be decompiled and a very curious person can understand it. And one more thing
Dim password as String ="sometxt"
sometxt can still be seen in memory dump of process is there any way to hide.
Nothing can protect you completely and even obfuscated code can be decompiled. It is harder to do so though.
WP Apps - Color Search | Arctic | XKCD | Sound Meter | Speed Dial
-
I have created a application in .Net for remote desktop connection and it is working fast and secure also, but for some reason i am not satisfied with the User Interface so just decided to rewrite the code again from the beginning. ;) But the problem came with the security from the hacker,cracker. yeah i know that .Net app can be easily de compiled so obstruced the code and declared all the class as not inheritable so that they can't import the app and create a object for the some important class and understand the algorithm or working behind it. Is there any other thing i am missing :doh: Can give any suggestion for the UI or features. One More Question: Should i kill features for the shake of UI.(i think i should kill features).
This is like locking the door to your house. Does it prevent somebody from knocking the door down with a bulldozer? No. It prevents them from getting EASY access to your house. A determined hacker can always crack your code - any code that can be run on the machine can be decompiled. You can encrypt your application, but the way that works is only the EXE file is encrypted - when the code is loaded into memory, it's decrypted and therefore understandable. Your goal is to make it *not worth my time* to try to decompile your application. You need to make it so the official licensed version of your application is easier to get than the cracked version. Like locking the door to the house - you're not going to make it impossible to crack, just make it so difficult that it's easier to get the legit version. That way the only ones who will crack your app are the people who do that kind of thing for fun, and it won't hurt your app sales. Does anybody download the cracked Angry Birds? NO, because the licensed version is free.
-
This is like locking the door to your house. Does it prevent somebody from knocking the door down with a bulldozer? No. It prevents them from getting EASY access to your house. A determined hacker can always crack your code - any code that can be run on the machine can be decompiled. You can encrypt your application, but the way that works is only the EXE file is encrypted - when the code is loaded into memory, it's decrypted and therefore understandable. Your goal is to make it *not worth my time* to try to decompile your application. You need to make it so the official licensed version of your application is easier to get than the cracked version. Like locking the door to the house - you're not going to make it impossible to crack, just make it so difficult that it's easier to get the legit version. That way the only ones who will crack your app are the people who do that kind of thing for fun, and it won't hurt your app sales. Does anybody download the cracked Angry Birds? NO, because the licensed version is free.
-
Jasmine2501 wrote:
official licensed version of your application is easier to get than the cracked version.
you are right.why don't i thought like that. :doh:
You are learning. We all have to learn these things. Someone told me many years ago, and I told you today. Isn't it wonderful to be a human being? :)