Reply to thread

Message: [QUOTE="AndrewG, post: 6927390"] I tried posting this in the 'Visual Studio Tools For Office' forum - perhaps it should have been here instead: I have a number of c# classes which I need to expose using an Addin - so that they can be used by others from within MS Excel vba - to be achieved by wrapping the c# classes in com visible objects which need to be deployed as a 'shared addin'. My normal dev/working environment is: Vista / VS 2008 / Excel 2007 - however this addin must be deployed to a target environment where desktops use Windows XP / Office 2003. After several unsuccessful attempts - and searching for answers I have switched to a dev environment which is Win-xp / VS 2005 / Office 2003 - so there is the greatest similarity between dev and deployment environments, and less chance of incompatibilities. With each combination of attempts it is quickly possible to get the addin working on the dev machine - but not when deployed. The current situation is as follows: Dev on win-xp/vs2005/Office 2003. Shared addin - targeted at excel only and ..Net 2.0 - contains a single test class exposed to com. The Office 2003 PIAs have been installed on the target machine and KB908002 has been set up as a prerequisite for the addin installer. The addin installer appears to run successfully on the test deployment machine - as far as I can tell registry entries, etc are as they should be. However, when running excel on the test deployment machine there was an error message in the system event log - about a 'missing module' - no indication of which one(s) though. I then added the dlls referenced in the vs2005 shared addin project as additional files to be installed during setup. Now there are no more error messages in event log. If I then run excel 2003 on the test deployment machine - and open the 'Com Addins' dialog - the addin appears in the list - with a tick next to it, Location is 'mscoree.dll' (?) and Load behaviour is 'Load at Startup' (does this mean: 'should be', 'has been', 'wasnt', 'might have been' ?). However the addin does not appear in the (excel) vba 'Tools-References' list (which it does on the dev machine), and hence cannot be used. What is likely to be going wrong ? [/QUOTE]

Verification