VSTA v 2 Proxy Names- Unique Names for Proxy Versions

For VSTA v 2 Visual Basic add-ins, unique version specific proxy names are required for registration in the VSTA pipeline.  Also, each host should use host specific names for all proxies. 

If multiple versions of a proxy will be used by VSTA v 2 Visual Basic add-ins, the different versions of the proxy must each have a unique name.  This will avoid a proxy being overwritten in the VSTA pipeline folder by another proxy with the same name but different version number.  This is not an issue for C# add-ins because they can resolve the reference to the proxy assembly in the GAC; however, for Visual Basic add-ins this is a requirement.

All proxies should have a host specific name.  This will avoid file naming collisions in the VSTA pipeline with other hosts, which can result in a proxy being overwritten in the pipeline and Visual Basic add-ins being unloadable (VSTA v 2).  This will also avoid any ambiguity in the GAC (VSTA v 1 and v 2).  For example an add-in could reference a proxy with the same name as another proxy present in the GAC and end up referencing the first instance of a proxy in the GAC with the same name instead of the intended proxy (see the section on loose versioning in the Proxy Versioning Options for Project Templates blog).

Example Proxy Names:
BAD- VSTAProxy

GOOD- HostA_VSTAProxy_v1

Related blogs:
Proxy Versioning Options for Project Templates
Proxy Assembly Registration- Unique Name Required
Creating Proxies- Installing the Proxy Assembly with the Host Application