Contents tagged with ManagedAddIns

  • NAnt Add-In

    Over the last few days I have been working on a new add-in. This time the aim is to integrate NAnt in a similar way to how NUnit Add-In works. At the moment you can right click on a solution, project or inside a build target to run NAnt. I have already eaten a fair amount of dog food as it’s something I've written out of necessity. It is now at the point where it is useful. I’m looking for a few dedicated alpha testers who promise to beat me up if it doesn’t work! If you’re zealous enough for the task – drop me an email or comment here.

  • Reflector Add-In + Reflector 3.3.1.0

    If anyone has tried using the Reflector Add-In with the latest version of Reflector, they will have found that the automatic download isn't working.  Reflector's download location and public key changed recently causing it to break.  I'm sorry I haven't released an update sooner.  I've been rather distracted with a complete rewrite of the Managed Add-Ins framework.  At some point you can expect a leaner, meaner add-in machine.  For the moment I've got a fixed version of the Reflector Add-In for you (plus source).  Unfortunately something in Reflector has changed causing it to stop working inside VS.NET 2002 (I imagine most people are using 2003 now anyway).  If you have any idea what the problem is please let me know!

  • Add-Ins Gallery Update

    Here are a few more example add-ins...

    1. Lutz Roeder's Reflector runnain as an Add-In
    2. Lutz Roeder's Documentor runnain as an Add-In (it would be quite strait forward to keep in sync with the code you're editing if you fancy and add-in project)
    3. Screenshot of Control Inspector running as an add-in inspecting Visual Studio Convert which also appears as an add-in.
    4. Command Prompt Add-In using the Pavel Zolnikov's Command Prompt Explorer Bar control.  Here is a version that can be run as an add-in.
    5. SqlBuddy running as an Add-In. SqlBuddy expects to find the Icons directory relative to the current directory. When running inside Visual Studio.NET the current directory is \Program Files\Microsoft Visual Studio .NET\Common7\IDE\. As a work around you can copy the Icons directory there. A better solution would be for the application to look for the Icons relative to AppDomain.CurrentDomain.BaseDirectory.
    6. Here is a screenshot of Messenger.NET running as an add-in. Messenger.NET is a messenger client. It is minimalist compared the the Microsoft Messanger, but that is it's beauty! It will happily run in a tool window without beeping, flashing and generaly bothering you!
    Please email here with screenshots and links to your add-ins!

  • Building the Reflector Add-In

    I've just written an article for the Code Project describing how you can easily create an VS.NET add-in like the Reflector one I posted screen shots of a while ago. I'm sorry I haven't got back to many of you who expressed interest in it. This reason is because I haven't been happy with the installation procedure (it too many steps). I'm very close to having an installer ready that does everything. I will email you all when this is ready. Hopefully then you can put your beta testing skills to more interesting problems than installation! If you would like to know when this is ready please drop me an email here.