Windows Service - The Best Choice?

[Khalid]

Hi All,

Can anybody tell me which language is the better choice for creating
"Windows Service" VB.Net, C# or C++

If somebody can point to an article that will be great help.

Thanks.

 

[Guest]

What to choose is up to u.

See managed sample there
http://www.codeproject.com/dotnet/simplewindowsservice.asp

Hi All,

Can anybody tell me which language is the better choice for creating
"Windows Service" VB.Net, C# or C++

If somebody can point to an article that will be great help.

Thanks.

--
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

 

[Lau Lei Cheong]

I think it depends on what you want to do.

Generally, if you want your service to perform tasks that can be done with
the runtimes or 3rd party components that uses .NET, it's better to program
it to run in managed environment. (Memory leakage is especially bad for
services as they trend to run longer than other applications)

But if you have to use libraries that uses callback functions, I'd think C++
is a better choice.

 

[Khalid]

Okay, Let me rephrase, I have a windows service written in VB.Net and it
uses a Third party API which is COM based. Now i want to know are there any
benifits of transferring this to (VC++.Net or C++ ) or to C# OR are there
any problems that we will face in VB.Net or if converted to C# instead of
any C++ version.

Thanks for your responses.

 

[Jianwei Sun]

If it runs well, I even don't bother transferring it.

If it's originally written in VB.Net, I would transfer to C#. Those two
are really just different languages based on CLR, and when compiled,
they are compiled to the same IL code.