|
Apolon Ivankovic
Posts: 4
Joined: 2006-11-25
|
We are having some trouble moving from ADX.Net V2.7 to V2.8 in our development environment. It appears it is because the adxloader.dll functionality in V2.8 won't over-write V2.7 registry information even when registering again or unregistering.
(See http://torqsoftware.com/blogs/apolon/2006/12/adxnet-v27-and-v28-registry-comparison.html)
Can you confirm that V2.8 performs no registration actions if V2.7 registry information is already there?
Assuming that this is the case, can you modify V2.8 and future versions to automatically remove previous addin registration information for a matching COM GUID?
I understand that a simple solution is to check whether the unregistration process for a V2.7 addin has completed, but I think that this is a weak approach in practice. Consider the weird and wonderful scenarios and states the Microsoft installer can get into as a justification for this request. Once an ADX.Net based addin is deployed across a large number of systems, we want to minimize any problems that occur as part of an upgrade. Having ADX.NET registration/unregistration over-write all previous registry states from previous versions of a particular addin would help reduce support problems.
|
|
|
Sergey Grischenko
Add-in Express team
Posts: 7233
Joined: 2004-07-05
|
Hi Apolon.
Sorry for inconvenience but you must unregister the add-in before you register it again with a new version of the ADX Loader.
Now it is not possible to upgrade Add-in Express based add-ins written using Add-in Express v2.7 without uninstaling them completely. This process will be smoother starting from Add-in Express v2.8.
P.S. Note that we take up your forum requests in the order we receive them.
Besides, it may take us some time to investigate your issue. Please be sure we will let you know as soon as the best possible solution is found.
|
|
Forums
Topics
Search
Help
Login
Register