I have developed a .NET DLL for another team who will be deploying it with
their VB6 application.  This DLL must also work with .NET applications in the
near future.  This team has been able to succesfully integrate my .NET DLL
with their VB6 application, but it appears that each time I give them a new
build of this DLL, they must un-register the old version, and re-register the
new version.  If they don't, they get this message when starting their
application:

"The located assembly's manifest definition with the name 'BlocktimeCalc'
does not match the assembly reference."

This team is deploying the application by creating an MSI package which is
executed from a software depot that temporarily elevates the user permissions
during installation.  However, after the initial installation this team wants
to deploy application updates via a custom update scheme that does not
accomodate un-registering and re-registering my DLL, and does not elevate
permissions that would allow modification of the registry.

Is there some tweak to my project that I can do that will eliminate the need
to un-register and re-register each new build?

Currently this DLL has a SNK, and is deployed in the application's directory.