ILSpy versus .NET Reflector

ILSpy - open source.NET assembly browser, decompiler and software utility for Microsoft .NET combining class browsing, static analysis and decompilation. Tool for code internal assemblies code analyze or reflector tool for our applications to improve the performance or to know the internals of the assembly we have created. I was using Red Gate .NET Reflector earlier for same as it was free and with frequent updates. Now Red Gate has made that tool paid (about 35$) version so I found alternative tools from that I can see IL and C# code easily for free. Why we need to pay money if we can develop open source product like ILSpy? That decompiler tool almost giving same functionalities like .NET Reflector. More...

Continue Reading »

An article by Slava Agafonov 4 Comments

Microsoft Test and Lab Manager and Visual Studio 2010

Dedicated testing tool that allows manuals tests plan, test cases, file bugs, create bugs in TFS for quality assurance team. This article demonstrates how to use the Microsoft Test and Lab Manager in Visual Studio 2010 to manage test suites and test cases. This article is based on the Application Lifecycle Management Hands-on Labs. That article will include end-to-end software testing capabilities of Visual Studio 2010. This includes a deep look at manual testing, lab management, data diagnostics adapters, the "actionable bug", functional UI testing, test impact analysis, test automation, and much more which will help you more easily find and eliminate defects from your software. More...

Continue Reading »

An article by Slava Agafonov 8 Comments

Continuous Integration and build engineering in Microsoft .NET

In this article will be introduction to Continuous Integration in .NET. I will use two cool book regarding to this topic: "Addison.Wesley.Continuous.Integration.Jun.2007" and "Deploying .NET applications. Learning MSBuild and ClickOnce" which you can download at the end of this article. I will do some kind of book review with best for my opinion phrases, questions and advices. Have you ever heard the term “integration hell”?

It is a situation where it takes more time to integrate the changes into the code base than to develop them. Normally the developer takes a repository snapshot to work with. While he is working on his copy the main code base changes because other developers submit their changes. But he has to eventually submit his work. That’s when all (integration) hell may break loose. More...

Continue Reading »

An article by Slava Agafonov 11 Comments