Our Most Popular Resources for Developers
Tags: productivity, beginners, development, technology
Published: 2021-06-15 12:03:10

Let's be honest, developing has its challenges. To meet the ever more diverse demands on applications and technologies, we all rely on a multitude of resources to make our lives easier. So we, the makers of your future favorite reporting tool [_List & Label_](https://www.combit.com/), thought it might be helpful to let you benefit from our experience. Below you will find just a small selection of the tools that we can't do without.

##__Helpful Tools__

[WinDbg](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools) is an absolutely indispensable tool for any serious developer. You can look into dump files, check the threads, stacks and module versions and even (sometimes <g>) get information on locals. Microsoft has recently released a preview of a Windows Store App that adds a nice UI.

[Sysinternals Suite](https://docs.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite) is a no-brainer to install. Process Monitor lets you find the culprit for any file or registry access - including stacks. And Process Explorer helps to kill the process that locks the DLLs you currently want to build.

[Fiddler](https://www.telerik.com/fiddler/fiddler-classic), a free web debugging proxy, is great for debugging http(s) traffic, decoding request headers and responses etc.

[bcTester](http://www.bctester.de/index.php?id=67&L=1) is a freeware tool that can be used to decode the contents of most barcodes. It's very useful to check the contents, encoding etc. It also can handle GS1 data.

The recent versions of Microsoft Visual Studio also include very interesting tools such as the Performance Profiler to investigate CPU usage (individual threads, durations, etc.) or the memory usage of different code segments. A good introduction to this can be found here.

In addition to the tools already included in Visual Studio, the well-known [Deleaker](https://www.deleaker.com/) is also used to record and then selectively eliminate a wide variety of leak types such as memory, GDI and handles. Of course, this is not only used when problems occur. It should also be used after new implementations of features in order to exclude any anomalies in advance. Cyclical reviews of the entire application should also be considered at regular intervals.

Ref12 is a very helpful Visual Studio extension that forwards F12 on .NET Framework class members to [ReferenceSource.Microsoft.com](https://referencesource.microsoft.com/), which shows you the source code right there in your browser.

Debwin4 is not only our customers favorite [tool to record List & Label commands](https://blog.combit.net/en/blog/development/november-2016/new-logging-application/), if something doesn't work as you want it to. Because of its good performance and versatile filtering capabilities, it is also used by us in various tools and applications.

##__Useful Documentation__

Microsoft Developer Network - MSDN is an inexhaustible source of information about Windows programming and it's almost impossible to imagine any developer without it. The [Microsoft API and reference catalog](https://docs.microsoft.com/de-de/documentation/) is a good starting point. For the native Windows API there is a very good overview in the area [Windows API Index](https://docs.microsoft.com/de-de/windows/win32/apiindex/windows-api-list?redirectedfrom=MSDN).

And, no big surprise, [Stack Overflow](https://stackoverflow.com/) helps if it gets trickier and you can't get any further with the board funds. You will certainly find an interesting approach or impulse in the right direction. There is a solution for everything. For combit List & Label there is even the tag 'listlabel'.