In the last post, I said I'd post shortly so - here's the skinny on the code that's currently in the ArcDeveloper Assembla repository.

The VSTemplates Project

Back in September I posted about using MSBuild to package up Visual Studio Item templates. I've uploaded this code into the repository, and it's ready to roll. The templates are setup for ArcDeveloper projects (i.e. an MIT license, "ArcDeveloper" etc.), but you can easily modify this and re-run the MSBuild script to create a set customized for your company / team.

At this time, there are just 3 templates - class, interface and non-COM class - with both C# and VB.NET flavors. I've got ideas for others, and will be adding more as they come up in my development.

Running MSBuild

If you have edited the templates, you'll want to run the ArcDeveloper.Templates.Build file. Here's how you do that:

1. Edit the .build file so the SolutionDir and BuildFolder are correct for your machine.
2. Open a Visual Studio Command Prompt
3. cd to the folder with the .build file
4. run msbuild arcdeveloper.templates.build

The build script will zip up the templates (as required by Visual Studio) and drop them into the BuildFolder. In order to have Visual Studio pick these up, you need to tell it where your Item Templates are. Go to Tools --> Options and select the Projects and Solutions item. Set the User Item Template location.

Now when you add an item to Visual Studio, you'll have some additional options

Get It!

If you just want the templates, you can download them from here: http://www.assembla.com/spaces/files/arcdeveloper

If you want to be able to build the templates, grab the code from Subversion: http://svn2.assembla.com/svn/arcdeveloper

I just finished off some burly refactoring of our security management code base so that it could be better unit tested. This subsystem essentially controls what tools a user has access to, as well as what layers / features a user can edit, so it's a pretty critical part of the infrastructure.

I'm working on some posts about how I did this, and should get them out next week, but for now, I'll just show this...

Although there are only 16 tests listed, many of these methods actually contain a number of individual test assertions, and there are more than 80 tests that are actually run.

My system was acting kind of slow, so I popped up Task Manager to see this...

This is a new personal best in terms of memory use by Visual Studio 2005 (devenv.exe) - 900 Mb.

Granted, I have 26 projects open but this is out of hand.

When I've looked into this in the past I have not seen any info on memory leaks etc, but if that's not the issue, then how how how does this process expand to this size? I re-started Visual Studio and now I'm back at a much more manageable 400Mb. Sigh.