A
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
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