.net miner

RichTextBox is a control which provides formatting features that TextBox control does not provide. For instance, you can customize the text’s color, style and/or size. So, you can apply formatting to a word, a line or all of the paragraph. RichTextBox is useful if you want to have more control over styling, but although it supports search in its content by the “Find” functionality, it does not have a search UI, so this reduces control’s user-friendly design. If you need to search something in RichTextBox you should add new code blocks, functions, UI controls.

With the following code blocks, we derived a searchable RichTextBox control from RichTextBox which provides search(Find) functionality with a “Find” pop-up. Searchable RichTextBox does not assist any UI customization nevertheless it allows using ‘Control + F’ function in the text content. For more, review the following blocks.

An example screenshot of the Searchable RichTextBox Control

You can get full source code from my git-hup page. Here is the link.

If you get ReflectionTypeLoadException during loading an assembly to your AppDomain or running an assembly, it will be hard to find which assembly cause the problem from the given standard error.
Generally the exception says something like “Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.“

You must have a look to the LoaderExceptions in the ReflectionTypeLoadException to understand exact problem. That property contains the whole resolution fail exceptions in it. But if you don’t have source code of your program or if you can not debug your program then it will be hard for you to access LoaderExceptions during run time. To solve this problem and take some help, you can use AssemblyLoadLogger, which I developed it for this purposes.

If you are developing a setup project with visual studio which contains custom action in it, you might have problems with the OLE calls (for ex: Copy to clipboard or paste from clipboard) and showing a dialog (for ex: FolderBrowser, OpenFileDialog, SaveFileDialog etc.). This is simply because of the thread structure of the setup projects.

MSI projects does not expect that your custom actions needs OLE  calls. Therefore they are not calling your custom actions with a thread which is apartment state is STA. If you want to make OLE calls, your thread must be in STA apartment state. Therefore if you show a form in your custom action and try to call Clipboard.SetData or Clipboard.GetData in your form, then you get a STA-MTA thread exception. Also your setup project will be locked when you try to show a dialog form in your custom action form.

Spoon, which is developed by Code Systems (Xenocode) was released. You can access and try it from the http://www.spoon.net(Turbo.net)  address.

So what is spoon?

Spoon allows users to run applications instantly from their web browsers with a single click. Spoon takes only minutes to deploy and embeds directly into your existing web site.
Spoon allows most apps to launch after downloading less than 10% of the app. Adaptive background downloading continues during execution.

Download Source Code From GitHub | Watch Sample Movie(v1.0.5.0)

 What is Process Viewer?

I can say that Process Viewer is a program like Microsoft Spy++. Unlikely to Spy++ it allows you to edit some properties of the Controls and also allows you to manage its window messages. You can change Text, Visibility, Enabled, Window Styles and Window Ex Styles properties of a control by using PV during run time. There withal you can ignore window messages, change incoming message to a different message or edit parameters of any window messages by putting breakpoints to the control’s window procedure with PV.

An example screenshot of the Process Viewer

An example screenshot of the Custom Property Grid Tab

Most of the programmers who uses Visual Studio .NET knows PropertyGrid which is the main control in the Properties Window of the Visual Studio.

If you are using Team Foundation Server with Visual Studio, it will be useful for you to integrate your projects bug system with the TFS Work Items system. You can write a simple module for your program which will handles the exceptions and collects needed information and send them to the TFS.

So how can we do something like that? First you have to write an error management module which will handles exceptions, errors, etc. and generates understandable information from them. After generating this information lastly you have to send this information to the TFS.

When I was newbie in .NET, it was a shocked for me to learn that .NET assemblies can be decompile. But today I know that this is a normal situation for a language which is compiling to an intermediate language. As we know that, after compiling a .NET project the output will be in MSIL (Microsoft Intermediate Language). And during the application lifecycle this codes will be compiled to Native Codes by the JIT (Just-In-Time Compiler) when they first used and cached in that computer for the future usages. Anyway this is another subject for us how JIT works, but here the problem is our assemblies are in MSIL format which has about 229 opcodes and all these opcodes has a standard working procedure. So if we know these opcodes and how they are working, we can produce the .NET codes by reverse engineering. This is simply what decompilers do. But why there are no stable decompilers for the native exes?

In one of my public projects, I used Xenocode PostBuild to obfuscate my codes. PostBuild is a very popular and common Obfuscation Tool for the .NET assemblies. When I worked for the Xenocode, I saw that the developers of PostBuild are really very good at doing their jobs. Most of them had worked for the Microsoft before. So I can say that if you need an obfuscation tool, you can use Xenocode PostBuild obfuscation tool without thinking a second.