Mike and Bernd currently attend the DevCon Europe 2004 (German site). They are presenting two talks - one is an overview of #develop, the other an in-depth talk on the architecture of #develop. To better visualize the idea of the addin infrastructure, Mike revamped the Addin Scout.

There is now a real tree view of the addin tree, where you can see which tree node is extended by which addin:

The addin view in contrast tells you exactly what tree nodes are extended by an addin.

Pretty neat tool for explaining the concept of the addin tree.

We are currently mulling the possibility of a public build server (CruiseControl.NET-based). Anybody willing to step up as a sponsor (hosting, advertising, ...)? Speaking of sponsoring: if you or your company wants to sponsor a specific feature, please contact me @ christophw at alphasierrapapa.com.

Roman fixed the problems with our source code control server. It is up and running again.

As some of you have already noticed, our Subversion server is currently down (reachable, but not servicing requests). We'll keep you posted once it is up and running again.

• SD-253: The templates for DirectX projects now reference the newest SDK libraries
• SD-267: Saving files in an interim removed folder doesn't cause an exception any longer

• SD-248 - "Warnings are always treated as errors"
• a long outstanding bug in the SharpAssembly library has been fixed (thanks to "amih" in the forum). It can now load Managed C++ executables and DLLs, so eventually there is code completition for the DirectX classes available.

Daniel introduced an exception bug in revision 1636 - and we didn't find it in time for release (though it was all too obvious to reproduce). 1649 is now released, and he checked in the change again - the new file dialog is now smart about subdirectories and namespaces (1650 if you are curious).

Also, the 1.0.1 installer is using a Windows Scripting Host (WSH) script to install three assemblies into the GAC and generate the help index. If your initial start tells you about a missing file, it might be that (a) scripting is disabled on your box or (b) your antivirus scanner has script blocking enabled. Sorry for the inconvenience, but simple batch files don't cut the mustard any more.

We are proud to have released the first maintenance release of the 1.0.x series (almost on schedule). It is available on our download page, the changes are documented as usual. One thing that wasn't possible due to time constraints (read: necessary testing) is to fix the resource import issues for VS.NET projects. You can count on us tackling this next.

#Assembly has a problem when loading unmanaged .NET DLLs - this affects the DirectX 9 code completion for example. #Assembly will be removed when we do the #D 2.0 port, thus you will have to live with missing code completion for unmanaged .NET DLLs for the 1.x branch. The .NET Reflection API in .NET 2.0 in contrast has everything I can dream of, which is why there will be no further work on #Assembly.

A longstanding issue has been resolved: consistent assembly versioning is now in the source tree. With this change, all assemblies reflect a central scheme - a three digit version number followed by the Subversion revision number of the tree it lives in. With this build process change, we also fixed all assemblies that had missing assembly infos (mostly backend bindings).

In other news: we also checked in NProf 0.9alpha.