Be more efficient. Today: Windows Explorer

June 24, 2009 at 11:10 AMAndre Loker

Just a reminder for myself or for anyone who’s interested, here are some useful tips and tricks to use in and with Windows Explorer that not probably everybody knows about.

Keyboard shortcuts

  • Move back in history: ALT-LEFT
  • Move forward in history: ALT-RIGHT
  • Move one folder up: ALT-UP (seems to work on Vista only)
  • Expand current folder: NUMPAD + or RIGHT
  • Collapse current folder: NUMPAD – or LEFT
  • Recursively expand all subfolders of the current folder (yeah, don’t try that on C:\): NUMPAD *
  • Recursively collapse all subfolders of the current folder (a bit tricky): first NUMPAD – or LEFT, then F5
  • Goto address bar: ALT-D (US systems), ALT-E (German systems – Windows Help says it’s ALT-S, but it won’t work on Vista, at least for me)
  • Toggle fullscreen: F11
  • Auto-completion in address bar: TAB (you can navigate fairly quickly by using ALT-D, TAB and BACKSLASH)

 

Other stuff

  • Fire up Explorer rooted at a specific path: explorer /root,directory where directory is the desired root directory, e.g. on my system explorer /root,e:\Tools yields
    image 
  • By the way, this makes for a useful external tool in VisualStudio:
    image
  • Open Explorer with a specific directory or file selected: explorer /select,Item – e.g. explorer /select,e:\Tools
  • Starting Explorer in a specific directory: explorer directory
  • Not directly related to the Explorer but a pretty cool tool nonetheless is VisualSubst. It lets you mount any directory as a new drive, just like the good old subst.exe but with a nice UI:
    image

 

 

If you have more tips and tricks related to the Windows Explorer, feel free to share them, I’ll add them here.

References:

Posted in: Tools

Tags: , ,

Meine Top 3 Dev Tools

May 19, 2009 at 9:53 AMAndre Loker

Mal wieder ausnahmsweise ein deutscher Beitrag. MSDN Deutschland ruft die Bloggemeinde auf, Ihre Lieblings Entwicklertools zu verkünden und lockt mit Gewinnen zur Befriedigung des Spieltriebs. Da will ich natürlich nicht hinten anstehen. Hier also zunächst meine persönliche Top 3 der Entwicklertools:

  • Visual Studio 2008. Keine Überraschung, zugegeben. Aber machen wir uns nichts vor, VS ist nun mal die IDE für .NETler und Plattform für eine Menge nützlicher Add-Ins.
  • ReSharper. Wieder keine Überraschung. Aber das Tool ist mir dermaßen in Fleisch und Blut übergegangen, dass ein arbeiten ohne R# wie eine Qual vorkommt. Mit ReSharper „strömt“ mir der Code quasi aus den Fingerspitzen. Und nein, ich arbeite nicht für JetBrains.
  • NAnt. Mein persönliches Schweizer Taschenmesser und Mädchen für alles: vom automatisierten Build bis hin zum Server-Backup, im Grunde gibt es nichts, was sich damit – mehr oder weniger elegant – steuern ließe. Auch wenn einige Entwickler mittlerweile rake verwenden, bleibe ich vorerst bei NAnt, da es sich mMn leichter deployen lässt.

Aber nur drei Tools zu nennen wäre recht eingeschränkt. Hier eine Auswahl von Tools, die für mich wichtig bis unentbehrlich sind:

  • Subversion, das Version Control System meiner Wahl. Mittlerweile bevorzugen viele git. Ich mag dessen Konzept, aber die Unterstützung von git für .NET-Entwickler ist im Moment besser.
  • TortoiseSVN kennt wohl jeder, der Subversion unter Windows einsetzt.
  • VisualSVN + VisualSVN Server. Nunja, besagte Unterstützung für .NET-Entwickler :-)
  • Testdriven.NET: Noch ein VS Add-In, dass wohl fast jeder kennt. Schneller kann man seine – in meinem Fall MbUnit - Unit Tests wohl nicht ausführen.
  • .NET Reflector, machmal ist Quellcode halt die beste Dokumentation!
  • CruiseControl.NET, mein bevorzugter Continuous Integration server.
  • CCNetConfig, Konfigurationstool für CruiseControl.NET
  • MS Sql Server Manament Studio 2008 – Code completion in Queries find ich richtig gut!
  • Notepad++, schlanker Text editor mit einer Menge Funktionen
  • dotTrace. Keine Ahnung warum die Anwendung lahmt? Dieser Profiler könnte helfen.
  • Balsamiq Mockups – Richtig cooles Tool um UI Attrappen zu basteln. Vor allem für die Kundenkommunikation hilfreich.
  • NDepend. Ich nenn es gerne “Code Qualität in Zahlen”.
  • NCover. Code coverage ist ebenfalls eine wichtige Metrik.

Da es hier um tools geht, habe ich meine Lieblingsbibliotheken an dieser Stelle außer Acht gelassen.

Hier noch einmal der Link zum MSDN Blogeintrag.

Posted in: Tools

Tags: , ,

NDepend update brings 64 bit compatibility

September 23, 2008 at 9:00 PMAndre Loker

Patrick Smacchia kept his word: the current version of NDepend added support for dependency graphs under 64 bit operating systems. If you remember, this was one of the few points of criticism I mentioned in my little review on NDepend. Visual NDepend can now visualize the dependencies between types, namespaces and members. If you're hovering over a cell in the Matrix view, NDepend will tell you how the types/namespaces/members on the two axes depend on each other in the small Info window in the lower left area of the screen:

image

When you click the cell a window appears with one or several graphs showing those dependencies visually:

image

While this dependency graph does not show you something completely new, it still a beneficial feature: visualizing the dependencies between types and members makes it much easier to understand them and to communicate them to other developers.

The NDepend people have done their homework. The The dependency graph - like almost every other part of Visual NDepend - uses visual variables effectively to get the maximum information out of the visualization: box sizes, line thickness * and colour are used to not only tell provide the user with additional information on the role and importance of the involved members (lines of code, number of incoming and outgoing dependencies etc.).

All in all, with the 64 bit support for dependency graphs there's one more reason to recommend NDepend.

* There's a drop down that can be used to define what the thickness of edges should represent. As Patrick Smacchia explains in the comments, changing the value does not necessarily lead to a visible change depending on the code that is analysed.

Posted in: Tools

Tags: ,

NDepend: code metrics at your service

July 8, 2008 at 10:07 AMAndre Loker

If you ever wrote code for a non-trivial project chances are that from time to time you stop an think: "I don't know, but I have the feeling that the code is not really clean/too complex/[insert adjective here that makes you feel bad about your code]". Chances are even that you did not had these thoughts - but your source code indeed was not really clean, too complex or what not. While the latter situation is certainly the worse of the two, both situation make clear that we need means to quantify the quality of our code. And how do we quantify things? By attaching numbers to it, of course. While a statement such as "80% of my code is crap, I think" is certainly a quantification (one which is not applicable in practice, I hope though), we are looking for a tool that can do the math for us and tell us everything we want to know about our code...

... and here comes NDepend!

NDepend is an incredibly versatile tool that can help us improving our code base. The tool analyses project assemblies and source code regarding a multitude of metrics. NDepend can create static reports containing the results in tabular and graphical form, but it also provides an interactive tool (Visual NDepend) which allows us to drill down into assemblies, namespaces and types in virtually every possible way.

First of all, let's realize why it is so useful to have a tool like NDepend at hand:

Improve Communication

Communication is extremely important if you are developing software in a team. One reason why there are catalogues of design patterns is the fact that they introduce a vocabulary that developers get used to. If I talk about abstract factories, commands and strategies, my colleagues know what I mean.

Using NDepend extends the developers' vocabulary and enriches the way in which developers can communicate. This can be a dialogue between two developers: A: "Hey, this type has high efferent coupling, we need to have a look at it" - B: "You're right, it also has a high lack of cohesion value" - A: "Looks like we should concentrate our next refactoring session on this type..." - B: "Absolutely!" - A: "... but first have a cup of coffee :-)" [note: the last statement is independent of any third party tools]

Track progression and evolution

NDepend is capable of comparing two builds of the same project. This allows us to quantify how the quality of a project evolves. For example, code refactoring should generaly lead to code that is less complex (for example in terms of "number of lines per method" or cyclomatic complexity). By comparing a build before refactoring with one after refactoring you can track how effective your refactoring session was.

Verify development guidelines

NDepend can help us enforcing guidelines that have been agreed upon. For example, you might define that method should not have more than X lines (or Y IL instructions) or that methods with more than 5 lines of code should have at least 20% comment. Checking those guidelines is easily done with NDepend.

Improve code quality

This is, of course, the ultimate goal of all of us - at least I hope :-) Having the numbers (ie. metrics) is one thing, taking consequences from those numbers is the other thing. The numbers (and graphs) NDepend gives us can help us spot places in the code that can be improved. Places which we might have overlooked otherwise. This gives us very concrete chances to improve our source code.

Some basic metrics

Before we go into detail on NDepend, here are some of the more advanced metrics that we will deal with:

  • Afferent coupling (Ca)
    This metric desribes the number of types or methods from outside of the current assembly that use a given type or method. The higher this value, the more important the given type or method is to users of the assembly.
  • Efferent coupling (Ce)
    This is the counterpart of Ca: it describes the number of assembly external types/methods that a specific type/method uses. A high value indicates that the specific type/method is very dependent on the external assembly.
  • Relational cohesion (H)
    A metric that describes how strong the types within a single assembly are related to each other. Generally, types within an assembly should be strongly related, but not too strong.
  • Instability (I)
    This describes how sensitive an assembly is regarding changes ion assemblies it depends on. It is measured as the quotient of efferent coupling (Ce) and total coupling (Ca+Ce).
  • Abstractness (A)
    Describes the ratio of abstract types in an assembly.
  • Distance from main sequence (D)
    Instability and abstractness should be in a certain balance. With my own words, I would describe this balance like that: an assembly with high abstractness should be stable as it is most likely used as an input assembly for other assemblies. If it were instable, it would be likely that it has to change sooner or later and this change would ripple through all assembly that depend on this assembly. On the other hand, a very concrete assembly (low abstractness) is likely to be at the end of a dependency graph, that is, almost no assemblies depend on it. It can and will therefore be quite instable.
  • Lack of cohesion (LCOM)
    In a coherent class, most of the methods will deal with most of the fields of that class. If you find that many methods in the class deal only with a subset of the fields it might be an indicator that the responsibility of the class is too broad and the class should be split.
  • Cyclomatic complexity (CC)
    This metric describes how many pathes a method has. The control flow in a method branches at every conditional statement, loop and other statements. A method with a high CC is hard to maintain.

Visual NDepend

Now that we are convinced that metrics are a Good Thing™  let us have a look at what NDepend brings along.

The NDepend package comes with two programs: the console runner (NDepend.Console.exe) and the graphical user interface (Visual NDepend). The former will be mostly used in automatic builds. To get in touch with NDepend let's stick to the GUI.

User interface styles

Visual NDepend supports to styles:

  1. the "Menu & Toolbar" style -  this is a look and feel comparable to MS Office 2003
  2. the "ribbon" style - this style uses the tabs & ribbons look and feel that you know from MS Office 2007

Here's what you get after you fire up VisualNDepend.exe. To the left, the "Menu & Toolbar" style, to the right the "ribbon" style:

imageimage  

As you see, both versions look very pleasing. The UI of Visual NDepend is extremely polished, certainly among the most polished UIs of any of the tools I use. Personally I prefer the ribbon style - it's well arranged and I can find everything quickly.

You can change between the two styles in the options:

image

Hint: to reduce the amount of place the ribbons take, double click on the tab header. The ribbons will then disappear:

image

A single click on a tab header will show the ribbon temporarily, a double click restores the view back to normal. This is useful if you need as much space as possible, e.g. when you're analysing a solution.

Creating a project - a simple example

imageVisual NDepend supports two operation modes which only differ in the fact whether you explicitly create a project file or not: if you just want to do a quick analysis, simply select the menu point "Select .NET assemblies". This will allow you to perform the analysis without creating an explicit project file.The other option is to create an explicit project. This is of course recommended if you need to perform the analysis more than one time (eg. in continuous builds). image

Let's just create a new project. You only need to name the project and enter a location for the project file (an xml file). I really appreciate the simplicity here. I don't like it if a program requires you to make a lot of decisions when creating a project.

image

After the new project is created you need to add assemblies that NDepend can analyse. To the left you have a list of "Application assemblies". Those assemblies are the ones that are compiled from the source code in the project. To the right there's a list of "Tier assemblies". These are the assemblies that your application assemblies reference, for example mscorlib, the System.* assemblies or other third party libraries. The separation between application assemblies and tier assemblies is extremely useful. Most likely you'll only want to analyse your own assemblies and their dependencies to the tier assemblies - there's no need to analyse the cohesion of classes in System.Core.dll.

To add application assemblies either drag and drop them from the Explorer to the application assemblies list or use "Add Assemblies of a Visual Studio solution" to use a .sln file to look up the project assemblies. The "View folders" button allows you to inspect and add folders from which application and tier assemblies should be loaded. After adding some application assemblies, my screen looks like this:

image

You can use the tabs on the left side to edit additional properties of your project, for example if and how to compare your project to an earlier build, where to put the report files and what to show in your report.

image image

imageAfter we have set up the project, we're ready to go: it's time to run the analysis! NDepend will start analysing your assemblies and generating the report files. The generation process does not take to long, about 20 seconds for a medium sized project on a decent machine.

Result windows

This what you will see after running the analysis;

image

Class browser

On the left side you have a class browser which shows the assemblies, namespaces, types and members of your project. Application assemblies are black, tier assemblies are blue. If you hover over a type or member it is selected in the metrics window and the Info window displays the metrics of the selected element (see the description of the metrics window).

Metrics

The metrics window visualizes the relative and absolute size of assemblies, namespaces, types and methods in terms of lines of code, number of IL instructions etc. This allows us to easily pinpoint the most important types etc. at a glance. If you hover with the mouse over one of the squares it is highlighted, the metric value is shown and the Info window in the bottom left displays all metrics for the selected square:

image

There is a little issue with the Metrics window, though. While hovering or clicking a square updates the Info window, the selection is not fixed. This means that as soon as the mouse leaves the selected square, the Info window will be either empty (if the mouse does not hover a square) or reflects the element that is currently under the mouse. It would be better if a single click on an element in the Metrics window would fix the selection. Clicking on an element in the Class Browser by the way does fix the selection.

Double clicking a member will launch Visual Studio and open the appropriate file. Cool!

Info

The Info window shows metrics for the selected element in the Metrics window or in the Class Browser: number of IL instructions, number of lines, number of lines with comment, percentage of comments, cyclomatic complexity etc.

Dependencies

This window displays the dependencies between the assemblies and types in our project. Starting on the Assembly level this tool allows us to drill down to deeper levels (namespaces, types, members) to detect dependencies between on these levels. Again, NDepend displays application assemblies and tier assemblies differently.

Application assemblies are shown in a triangulated matrix: all app assemblies can potentially be used by other assemblies and use other assemblies at the same time. For example: in this test project, 6 methods in the assembly Vanilla.Web.Monorail together use 17 members of the assembly Vanilla.Web.

image image

 

For tier assemblies only one direction is displayed, that is how they are used by app assemblies. For example, we can see that Vanilla.Web.MonoRail uses 68 types of the Castle.MonoRail.Framework assembly:

image

A single click on any of the squares is meant to show you a dependency graph. As of now this does not work on 64bit platforms. This issue comes from an incompatibility of the used graph rendering library with 64 bit systems. Patrick Smacchia promised that this problem will be taken care of in one of the next versions.  In the current version of NDepend this issue is not present anymore, dependency graphs work like a charm on 64 bit platform. Read more.

I will show an example dependency graph when I come to automatic builds.

By clicking on one of the "+" buttons on the left side or the top side of the matrix you can dig down to lower levels: namespaces, types, members. This gives you endless possibilities of determining dependencies.

image

If you want to focus on a specific dependency, double click the corresponding square and Visual NDepend will "zoom in" into this dependency:

image

Let's leave the Dependencies window alone for now - it's possibilities are countless, just play with it!

CQL Queries

Let me put it straight: this feature is just awesome! NDepend spits out a lot of metrics on its own, but it also gives you a powerful query language that you can use to gather almost any information about your source code that you like.

CQL (Code Query Language) is a query language similar to SQL - which is the first cool thing as most of us are used to SQL. Using CQL you can query against a large set of metrics. Have a look at the CQL specifications to see how complex the query language is.

To give you an example of a simple CQL query:

   1: SELECT TYPES WHERE NbFields > 6

This query returns all types with more than 6 fields. Easy, hm? Another example: methods that are potentially unused:

   1: SELECT TOP 10 METHODS WHERE 
   2:  MethodCa == 0 AND            // Ca=0 -> No Afferent Coupling -> The method is not used in the context of this application.
   3:  !IsPublic AND                // Public methods might be used by client applications of your assemblies.
   4:  !IsEntryPoint AND            // Main() method is not used by-design.
   5:  !IsExplicitInterfaceImpl AND // The IL code never explicitely calls explicit interface methods implementation.
   6:  !IsClassConstructor AND      // The IL code never explicitely calls class constructors.
   7:  !IsFinalizer                 // The IL code never explicitely calls finalizers.

Taking the queries a step further, you can define constraints using CQL which can be used to express design guidelines or rules. For example if your design rule is to not have methods with more than 20 lines of code, you can express this constraint like this:

   1: WARN IF Count > 0 IN SELECT METHODS WHERE NbLinesOfCode > 20

When you analyse your project NDepend will generate a warning for all methods that have more than 20 lines of code (you might want to refactor those methods).

In the CQL window you can group the queries. NDepend comes with a standard set of useful queries so you don't have to write everything from scratch.

image

The CQL query editor is - like the rest of the application - well polished. It provides syntax highlighting and code completion:

image

By the way, the CQL is constantly extended. New metrics are added in almost every new version of NDepend.

Here's a screen shot of the query result window showing types with more than 20 methods:

image

While CQL is already very powerful, I've been missing some features:

  • aggregation - for example I'd like to calculate the max, min and average number of lines of code per method (update: while aggregates are not queryable, the query result window shows some aggregated values, see the screen shot above)
  • comparing metrics - for example I cannot select methods with too many IL instructions per line (like "SELECT METHODS WHERE NbILInstructions  > (NbLinesOfCode * 10)"); CQL won't allow me to compare NbILInstructions with anything other than integer numbers.

But all in all, CQL is a great idea and a powerful language. It is what makes NDepend such a versatile tool.

With this I'll conclude this short overview of Visual NDepend. The programs contains heaps of other features which you should discover for yourself.

The HTML report

Where Visual NDepend is used to setup a project and analyse it interactively, the HTML is meant to represent the state of a project in a static and concise way. The analysis data that NDepend generates is stored in an XML files. This has the advantage that you can simply use XSLT to transform the result into HTML. This is exactly what NDepend does to generate the HTML report. In Visual NDepend you can select to either provide your own xsl file or use the default transformation that NDepend comes with. The latter is certainly useful in most cases. If you need more control, go ahead and build your own xsl transformation file. This fits perfectly into NDepends philosophy: provide a useful default set of functionality, but be open for extensions!

So, what does the default report show:

  • General application metrics
    • lines of code
    • number of IL instructions
    • number of lines with comment, percentage comments
    • number of assemblies, types, classes, interfaces, structs,  etc.
    • Percentage of public types and methods etc.
    • Average number of fields per type, method per type etc.
    • ...
      image
  • Metrics per assembly
    • LOC, number of IL instructions, ...
    • coupling metrics (Ca, Ce, relational cohesion, instability, abstractness, instability-abstractness-balance)
  • Assembly dependencies
    image
  • CQL query & constraints results
    • Warnings for constraints that have failed
       image
  • Type metrics
    • LOC, number of IL instructions, ...
    • coupling metrics (Ca, Ce, lack of cohesion ...)
    • cyclomatic complexity
    • Number of directly and indirectly derived classes, depth in inheritance tree
  • Type dependencies (initially not enabled)
    • Defines which types depend on which types.

The report also contains a dependency view (as in the Metrics window in Visual NDepend), a dependency graph (again, no 64bit support) and graph that show the balance between abstractness and stability.

image

(In the example project, the assemblies seem to be quite instable)

NDepend in automatic builds

You will most likely want to have NDepend generate a report during automatic builds; it's an invaluable tool to define metrics for code quality and to enforce design guidelines. NDepend comes with a command line tool (NDepend.Console.exe) that can be integrated into the build process. The command line tool is held simple: it simply uses a project file that you generated with Visual NDepend beforehand. While this makes it easy to configure an NDepend project at a central place, it has some drawbacks. NDepend stores only absolute paths, for example to folders that contain tested assemblies or to a previous build you want to compare the current build to. Update: the previous sentence is not true, NDepend supports a relative path mode. I simply overlooked the option the whole time. It can be found under Project properties => Code to analyze => Relative path mode:

image 

While you can override the input folders and output folders with command line flags (/InDirs and /OutDir), other options in the project file cannot be overridden. This could cause trouble if you have a dedicated build server.

NDepend ships with an xslt for CruiseControl.NET and build tasks for nant and MsBuild. I haven't used any of the build tasks. I simply used the <exec> task in nant. Here's an example from one of my build files:

   1: <property name="ndepend.project" value='"${root.dir}\NDependProject.xml"'/>
   2: <property name="ndepend.outdir" value='${reports.dir}\ndepend'/>
   3: <property name="ndepend.indirs" value='"${build.dir}"'/>
   4: <property name="ndepend.indirs" value='${ndepend.indirs} "C:\Windows\Microsoft.NET\Framework\v2.0.50727"'/>
   5: <property name="ndepend.indirs" value='${ndepend.indirs} "C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0"'/>
   6: <property name="ndepend.indirs" value='${ndepend.indirs} "C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5"'/>
   7:  
   8: <exec program="NDepend.Console.exe"
   9:     commandline='${ndepend.project} /InDirs ${ndepend.indirs} /OutDir "${ndepend.outdir}"'/>

Not too hard, if you ask me. The xsl file provided for CruiseControl creates a report that is similar to the HTML report you get when analysing using Visual NDepend, so I won't go into detail here. However, I promised you to show an example of a depency graph, so here we go:

image

Based on a blog post of Robin Curry I further improved ccnet integration, it now looks like this:

image

I needed to update Robin's XSL file to match the current version of NDepend. I plan to write a separate article on this "advanced" ccnet integration, so stay tuned!

Documentation, help, support

One thing I absolutely have to mention positively is the amount of help you get from NDepend. NDepend offers a plethora of tutorials (in video and text form), definition of all metrics, an in-depth specification of CQL, and a massive amount of Tips and Tricks. It is not often that you get that much of support!

Pricing

NDepend licenses are available starting from 299€ (excl VAT), with a massive discount depending on the number of licenses (down to 179€/license if you order more than 20 licenses). Furthermore Enterprise licenses are available on demand. See the purchase page for details.

Conclusion

Wow, that was a long article, wasn't it. Still I could only show you a fraction of the functionality NDepend has to offer. The cool thing is that you can do whatever fits your needs thanks to the extremely flexible and extensible design using CQL. Visual NDepend is a great user interface which makes analysing a project interactively easy fun and interesting. Integrate NDepend into your build process and you have heaps of metrics that you can use to quantify the quality of your code. The price is absolutely adequate.

Pros

  • Extremely versatile and extensible, thanks to CQL
  • Pinpoints problematic areas in your code
  • Quantifies code quality - get rid of "I have the feeling that this and that piece of code is not optimal"
  • Introduces a whole new language to the communication between developers
  • Visual NDepend as a great GUI
  • Large amount of tutorials
  • Useful set of metrics to start with, extensible if needed
  • Very convincing value for the money!

Cons and issues

  • Dependency graphs not supported on x64 machines as of now
  • CQL lacks some possibly interesting features (aggregates, comparison of metrics)
  • NDepend.Console.exe has a limited set of parameters. It would be nice to be able to provide more options instead of relying on project files
  • Project files stores mostly absolute paths  Update: not true, NDepend supports a relative path mode.
  • An HTML report is always created, even in CI scenarios, where the XML files would have been enough.

Granted, none of the issues stated above are show stoppers. All in all there's no doubt that NDepend is an excellent tool. I can wholeheartedly recommend it to any developer who wants to improve the quality of his/her code.

Update 07/08/2008:

Patrick has just published a post in his blog in which he compares NDepend to other tools. I especially like the comparison to tools like Resharper or CodeRush:

I like to think that what tools such as ReSharper or CodeRush are doing to your code at micro level (i.e methods' body structuring), NDepend does it at macro level (i.e class, namespace, assembly structuring). Hence, as a developer I personally use both kind of tools to automatically control every aspects of the code base I am working on.

@Patrick: thanks for mentioning this post!

Things I updated:

  • Rectified statement regarding absolute paths. NDepends does support a relative path mode
  • Added screen shot of query result window and mentioned that aggregates are shown in that window
  • Added link to Patrick's blog

Posted in: Tools

Tags: , , ,

Kleine Toolkunde (I)

February 11, 2008 at 11:58 PMAndre Loker

Es mag ja durchaus Entwickler geben, die mit Notepad und csc.exe ihre Erfüllung finden. Ich gehöre definitiv nicht dazu und bin bekennender IDE Liebhaber. Neben den Standard-Features die Visual Studio so bietet, gibt es da draußen noch eine ganze Reihe kostenloser und -pflichtiger Add-Ins, die dem Entwickler das Leben noch einfacher machen. Oder sagen wir: weniger schwer.

Hier also eine kleine Liste von must-have Add-Ins für Visual Studio:

  • Resharper – ohne geht nicht, sorry. Wenn man sich einmal in das Tool eingearbeitet hat, ist ein Arbeiten ohne diesen treuen Begleiter eine Qual. Viel sagen muss man zu diesem vielseitigen Tool wohl nicht.
  • VisualSVN – eine vernünftige Subversion-Einbindung. Anders als das relativ instabile AnkhSVN macht sich VisualSVN das Leben viel leichter und verrichtet seine Arbeitet sozusagen huckepack auf dem Rücken der bekannten SVN Shell-Extension TortoiseSVN. Das Add-In kostet rund 37€, ist aber jeden Cent wert, weil es eine sehr löbliche Eigenschaft hat: man merkt nicht, dass es da ist. Stattdessen macht es einfach das, was es soll, ohne den Nutzer zu stören. Empfehlenswert ist auch das Repository-Verwaltungstool VisualSVN Server, welches gratis (!) zu downloaden ist.
  • VersioningControlledBuild – Versionsnummern im Griff. Wenn man nicht gerade einen Buildserver verwendet, ist dieses Add-In sehr nützlich, da es bei jedem Buildvorgang die Versionsnummern der Assemblies erhöht. Deutliche Versionsnummern machen die Kommunikation bei der Fehlersuche erheblich einfacher!
  • GhostDoc – XML-Dokumentation von Geisterhand. Sein wir ehrlich - es ist schon manchmal lästig, Code zu kommentieren. GhostDoc nimmt dem Programmierer insofern schon ein großen Teil der Arbeit ab, indem es XML-Dokumentations-Gründgerüste erstellt und so gut wie möglich probiert auszufüllen. Dabei schaut GhostDoc nach dem Namen des entsprechenden Members und nach bekannten Mustern (z.B. Eventhandlern). Man sollte nur vor lauter Automatismus nicht vergessen, diejenigen Informationen nachzutragen, die eben nicht automatisch abgeleitet werden können…
  • TestDriven.NET - Unit Tests aus der IDE heraus starten. So wird man beim TDD nicht immer dadurch gestört, zwischen Testrunner GUI und IDE wechseln zu müssen. TestDriven.NET unterstützt unter anderem MbUnit, mein persönlicher Favorit unter den Unit Test Frameworks.
  • Web Deployment Project - ein Tool von Microsoft, um Webseiten (Web Sites) und Webanwendungen (Web Applications) vorzukompilieren und zu deployen. Unter anderem erlaubt das Add-In diverse Varianten, um mehrere (oder alle) Pages und Controls zu einer einzelnen Assembly zu kompilieren. Dabei können auch Control-Bibliotheken generiert werden, wodurch die enthaltenen User Controls in anderen Projekten wie Custom Controls verwendet werden können. Code re-use, ik hör dir trapsen!

Posted in: Tools

Tags: , , , , , , ,