Features & BenefitsThe Assembly Version Manager was created to address a pain point that I experience with nearly every project I have ever worked on in Visual Studio. In most projects, it is a common need to have a project file reference an external assembly that exists somewhere on disk. Sometimes this assembly comes from a 3rd party component vendor, sometimes it comes from an open source project, and sometimes it comes from your company's own build server. If the assembly you are referencing never changes versions, then you'll never run into any problems... but how do you handle the situation when new versions of that assembly are released? In the past this has always been something of a manual process... sometimes involving management (for components we have purchased) and sometimes involving QA (to help determine which versions of components have been tested), and it always involves one or more developers who will have the ultimate responsibility of updating the project-level references. Doesn't that sound like a lot there's a lot of room for error? In my experience, it is pretty easy to forget to update one of the project-level references in a complex solution or to forget that you have some other project that also has a project-level reference to the updated assembly in another solution. This is where the Assembly Version Manager comes in to save the day. Related Links Quick Start
Getting Started Guide
Best Practices
Version History Support Forums Product ScreenshotsTrack the status of the references in your solution: 
Add as many configurations as you need to identify builds/releases: 
Define custom naming conventions to identify builds/releases or use the defaults: 
Filter which references are shown in the grid: 
Assign these configurations to references in your solution: 
Easily see when your build server or component libraries have new builds/releases available: 
Quickly switch the reference to the new build of the assembly: 
Easily verify that you are using the latest build/release: 
| 
