Version management

Are you developing .NET assemblies intended to be used from C/AL? If so, then you must have realized that keeping proper track of them and managing them on the server (or client, in case you still do that) is not a simple affair. Assemblies in .NET are identified through their fully qualified name, and that’s how NAV tells one assembly from another, as well.

[Updated] I had to update this post a little bit, see below for the details, but the killer feature had to go 🙁 [/Updated] Remeber that tool “ Automated Version Management ” that I published here and on Mibuso five months ago? It has just got an update: version 2.0.

Imagine that whenever you edit an object in C/SIDE Object Designer, and save it, the system automatically saves it in the version history. Imagine that it never simply overwrites your previous version, but keeps all of them there for you.

When I posted my last relevant post on this blog, I’ve got a comment from infonote (a visitor) how bad it was that Microsoft Dynamics NAV can’t use a versioning system. Well, as the matter of fact, it can. One of the nice things in NAV is that at any given moment, the development environment is just a Shift+F12 away.