Hi,
I've got a VB 6 application that I would like to run as a Windows Service
(new name for NT Services apparently!). However, a quick Google search
suggests that this is not such a great idea.
http://support.microsoft.com/default...b;EN-US;175948 for example.
which gives the quote :
"Microsoft does not currently recommend, and does not support, running
Visual Basic applications as Microsoft Windows NT, Windows 2000 and Windows
XP Services because the applications may exhibit unstable behavior when
installed and run as Microsoft Windows Services. "
I was just wondering what people's experience / thoughts / etc. are with
this, before I take the plunge and port it to VB .NET .
Thanks,
Rowland.
I've got a VB 6 application that I would like to run as a Windows Service
(new name for NT Services apparently!). However, a quick Google search
suggests that this is not such a great idea.
http://support.microsoft.com/default...b;EN-US;175948 for example.
which gives the quote :
"Microsoft does not currently recommend, and does not support, running
Visual Basic applications as Microsoft Windows NT, Windows 2000 and Windows
XP Services because the applications may exhibit unstable behavior when
installed and run as Microsoft Windows Services. "
I was just wondering what people's experience / thoughts / etc. are with
this, before I take the plunge and port it to VB .NET .
Thanks,
Rowland.