M
Mike
Hello,
I hope there is a solution to this.
I am required to develop a service application using Visual Studio
..NET.
I am required to develop it using C++.
Originally we set out using Visual Studio .NET 2003. But for the
database bugs in this framework, this environment supports Windows
Service project type for the C++ language.
I currently have a solution prepared and (mostly) working but for the
..NET framework database bugs.
The application requires Visual Studio .NET and the Service Pack 2 in
support of key database connection patches.
Unfortunately there is no Service Pack for VS.NET 2003 or the decision
would be easy to remain using 2003.
There does not appear to be a Windows Service project available in the
C++ language?!
Is it easy to add such a project type? Or do I simply start from a
blank project and copy over any source code that supported the VS.NET
2003 solution?
If necessary I'll use the C# language since this seems to be
outweighed by framework robustness where database connectivity is
concerned. And the C# is close enough to C++ to make the migration not
as painful.
Any similar experiences would be appreciated.
Best regards,
Michael Powell
I hope there is a solution to this.
I am required to develop a service application using Visual Studio
..NET.
I am required to develop it using C++.
Originally we set out using Visual Studio .NET 2003. But for the
database bugs in this framework, this environment supports Windows
Service project type for the C++ language.
I currently have a solution prepared and (mostly) working but for the
..NET framework database bugs.
The application requires Visual Studio .NET and the Service Pack 2 in
support of key database connection patches.
Unfortunately there is no Service Pack for VS.NET 2003 or the decision
would be easy to remain using 2003.
There does not appear to be a Windows Service project available in the
C++ language?!
Is it easy to add such a project type? Or do I simply start from a
blank project and copy over any source code that supported the VS.NET
2003 solution?
If necessary I'll use the C# language since this seems to be
outweighed by framework robustness where database connectivity is
concerned. And the C# is close enough to C++ to make the migration not
as painful.
Any similar experiences would be appreciated.
Best regards,
Michael Powell