microsoft.public.developer.outlook.addins

[Ashley Sutcliffe]

Hello all,

I hope this question isn't quite as dumb as my previous one.

I have created my Outlook 2k addin in VB6 and deployed it in an
installer (Inno Setup - great tool), along with the VB6 runtime, if
necessary.

On an XP machine with Outlook 2k, it installs and runs perfectly

However, on an identical machine that has Visual Studio .NET installed,
VS .NET decides that it needs to set itself up with some new files off
the CD when you run the addin for the first time (or cancel the setup
and reload Outlook). Needless to say, this is a right pain for the
majority of my users, who have VS .NET installed and share the same VS
..NET CD.

Does anyone have any idea about either what VS .NET is doing or why it
decides that it needs to? I am at a bit of a loss.

Thanks

Ashley

 

[Ken Slovak - [MVP - Outlook]]

Don't install the VB runtimes and see if that helps. They have been
included with every MS operating system since Win98 so you don't need
them anyway unless you need to support Win95.

 

[Ashley Sutcliffe]

Hi Ken,

I thought about this and checked the VB runtime versions on the test
machine. My installer had not overwritten the more current versions in
the System32 directory of the machine.

I will remove the VB runtime from my installer as I only need to support
NT, 2000 and XP. I'll let you know if that makes any difference.

Thanks

Ashley

 

[Ashley Sutcliffe]

This seems to have solved the problem. I don't understand what could
have being going on as it should not have been overwriting newer files,
but there you go.

Thanks again.

Ashley