This is not question but this is very big study subject. I suggest you to read some books and MSDN to get information about .net framework. single line answer is, it is Framework developed by Microsoft for developing Web/Windows and other applications.
No way. As a developer, stealing money from other developers is inacceptable.
You have been reported in the Spam & Abuse watch forum. As I can tell you from experience with similar cases, your account will be gone within few hours.
The reason that you'll always receive the answer "whatever your comfortable with" is a simple and practical one; you can write applications in both, and one can use RAD-principles in both. Both have specific advantages and drawbacks.
Now, if you have a team of .NET developers, it'd be an awful idea to teach them C, or worse go ahead and have them learn by doing. Same goes for a group of seasoned MFC-devs; they'd be wanting simple pointers and clean control over memory-allocation.
The idea that some "high lever CEO" needs to pick a tech is nonsense. Ask your developers. If they say the new language will be LOLCODE, than that's what you'll get. The reason you'll need to ask your developers is also a practical one; they'll know the restrictions and possibilities of each possible choice. As an example, it's technically not possible to replace the Windows login-screen using a managed language, or to write a device driver. If it's a larger project, the chances that multiple languages will be used increases. Again, it's merely being practical; one uses a managed language for convenience, unmanaged for speed.
Now, if you want a more fruitful discussion, you'll ask what front-ends one should focus on. Does your project need to be accessible from a lot of devices?
If yes, go for ASP.NET.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
i am actually getting desperate with this... i have developed a nice User-SelfService Site where user can modify some settings and also change their own password.
Unfortunatly now it should run against a Novell eDirectory also instead of AD only.
I did some research and from my understanding the easyest way would be to execute an LDAPMODIFY command but unfortunatly i can not find the LDAP Tools for windows (it looks, that they only exist for Linux )
At the Time when the password of a user has to be changed, we have the current password, the whole Path of the Users Object in eDir and also an Proxyaccount that is permitted to reset users passwords.
Did anyone have expiriance with LDAPMODIFY or Change Password on eDir?
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
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).
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 asString ="sometxt"
sometxt can still be seen in memory dump of process is there any way to hide.
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.