Debugging new versions of Office add-in (registry hell?)

[Boris]

I created a COM add-in in C# for Microsoft Access 2003 some time ago.
Everything works perfectly but new features must be added now. The problem
is that I don't remember how I managed to debug new versions of the add-in.
Visual Studio.NET 2003 is configured to start Access when I want to debug.
However Access uses always the old version of the add-in. If I recall
correctly there was a problem in Visual Studio.NET 2003 - it messes up or
forgets to update the registry when a new version of an add-in is compiled
(or am I wrong?).

Now one solution could be to remove all values in the registry before you
compile and install the new version of the add-in. However I really don't
want to go through the registry all the time when I do only a minor change
in the code. Do others have the same problem, too? I didn't find anything in
Google and the Knowledge Base so I wonder if I am the only one having
problems when trying to debug new versions of an add-in in Visual Studio.NET
2003?

Boris

 

[Boris]

I created a COM add-in in C# for Microsoft Access 2003 some time ago.
Everything works perfectly but new features must be added now. The
problem is that I don't remember how I managed to debug new versions
of the add-in. Visual Studio.NET 2003 is configured to start Access
when I want to debug. However Access uses always the old version of
the add-in. If I recall correctly there was a problem in Visual
Studio.NET 2003 - it messes up or forgets to update the registry when
a new version of an add-in is compiled (or am I wrong?).

Now one solution could be to remove all values in the registry before
you compile and install the new version of the add-in. However I
really don't want to go through the registry all the time when I do
only a minor change in the code. Do others have the same problem,
too? I didn't find anything in Google and the Knowledge Base so I
wonder if I am the only one having problems when trying to debug new
versions of an add-in in Visual Studio.NET 2003?

Problem solved - some registry entries were corrupted. Rebuilding the
project and debugging the new version works again.

Boris