Thanks all the guys who have been trying to help. I have just did it (or better say hacked it :-) In short, there is really a KEY in the registry. I couldn't locate it because it wasn't under the path of the software name. After I copied that KEY (and with some programming knowledge it works like magic. Here are my steps. I did a few researches, and a lot more google searches. I started with this site teaching How to get the serial number of a program with Olly Dbg. However, I found it is a Microsoft Visual C / Basic. NET in PEi D. I couldn't debug my.exe by Olly Dbg. Told by this site: Olly isn't the answer here, because its a. Net program. So use google in order to find the program that will help ya. First, I came upon. NET decompiler. It is a good tool. After my first inspection into the source code, I located the critical method btn OK_ Click which is the point for checking the User Key. Sadly, the method content is masked by / trial in. NET decompiler (wtf) as it isn't a freeware, and it costs 399 USD (not less for me). And more, I don't have confident that it is guaranteed to get the User Key after purchasing the. NET decompiler. (it's my first time anyway) Then I moved on to other free alternatives, such as ILSpy (free) and. NET Reflector (14-day trial). I finally could inspect the btn OK_ Click method: private void btn OK_ Click(object sender, Event Args e) this.pbc User Key = Strings. Trim(this.txt User Key1. Text + this.txt User Key2. Text + this.txt User Key3. Text + this.txt User Key4. Text this.pbc User Key = Strings. LSet( Strings. Trim(this.pbc User Key 16 try this.create User Key = mod Common. Xx Get User ID(ref this.pbc User Key if (this.create User Key) My Project. Forms. Frm Launcher.str User ID = this.pbc User Key; catch ( Exception expr_86) Project Data. Set Project Error(expr_86 Application. Exit Project Data. Clear Project Error this. Close Simply, pbc User Key is the User Key we.
Spices. Net Decompiler - Download Patch Keygen Download.
Look inside any. NET code ✔ Debugging your application Follow bugs through your application to see where your problems lie – whether it's in your own code, third-party libraries, or components used by your application. ✔ Understand how applications work Inherited applications with little or no documentation or comments are hard to develop. Use. NET Reflector to understand how the code runs and avoid bugs. ✔ Share Point and other third-party platforms Like many third-party platforms, Share Point APIs and libraries aren't always well-documented. With. NET Reflector you can look inside their assemblies and see how they work and which APIs you can call. Code smarter with. NET Reflector. NET Reflector saves time and simplifies development by letting you see and debug into the source of all the. NET code you work with. Development is increasingly dependent on third-party technologies – using available frameworks and libraries is a great way to get stuff done fast without re-inventing the wheel. But the problem with using code you didn't write is that you're dependent on the documentation, and it's hard to debug. Documentation is often missing or incomplete, and debugging has to stop where your own code stops. This gets even worse with a legacy code base. Use. NET Reflector to look into the black box of missing or undocumented source code and start coding with confidence. Video Tour EVERY DEVELOPER NEEDS THIS TOOL. The ability to step into third–party code including Microsoft Share Point Server assemblies opens up new possibilities and lets you understand what Microsoft's APIs are doing. You can step right into their code and see what it happening, all from Visual Studio. This knowledge lets you build better applications, and provides insight into undocumented APIs. Daniel Larson, Software Architect, News Gator Technologies How. NET Reflector can help you Makes all. NET code.
Download Now