Services in VB.NET standard

[russgreen]

Does anyone know of a macro or way of enabling Windows service projects to be created in VB.NET standard? Thomas Erdösi has written a fantastic macro to enable new projects to be compiled to dll's.

If not the would someone be kind enough to create a new blank windows service project for me?

Russ

[russgreen]

I've created a service and installer and installed my service. It show up in the list of services now but when trying to start it it takes too long and the status is stuck on starting.

Any ideas?

I've posted the project in its current state here.

Russ

[Slow_Learner]

I haven't written any services, but it seems very likely that you need to investigate the ServiceController component:
ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfsystemserviceprocessservicecontrollerclasstopic.htm

"Represents a Windows service and allows you to connect to a running or stopped service, manipulate it, or get information about it."

[Slow_Learner]

That isn't what you wanted at all, is it. I'm trying to figure out service installation/removal also, or maybe someone else already has done it and will post your answer.

[Slow_Learner]

Got it. Read:
ms-help://MS.VSCC/MS.MSDNVS/vbcon/html/vbwlkwalkthroughcreatingwindowsserviceapplication.htm

I followed its instructions exactly and was rewarded with the following attached project. The output of the project (two projects actually) is a) a service and b) an installer package. I ran the installer package, my toy service showed up in the services list (right-click My Computer -> Manage...) and the service started/stopped, as well as stuck an event in the event log.

Something a bit tricky (although you sound like you got past this: When you provide username/password, if you are installing on your local machine, the format for username is COMPUTERNAME\username.

Hope it helps.

[Slow_Learner]

Project files for the installer:

[russgreen]

Thanks, I did get past this stage and I have narrowed down the problem.

I get my service working fine now with the on start

Dim watcherThread As Thread = New Thread(AddressOf listener)
 
Protected Overrides Sub OnStart(ByVal args() As String)
        WriteToLog("logs\webproxy.log", "Service started")
        watcherThread.Start()
    End Sub

the listener code is this

Private Sub listener()
        Dim tcplistener As New TcpListener(port)
        tcplistener.Start()
 
        WriteToLog("logs\webproxy.log", "Listening on port " & port.ToString)
 
        'While True
        ' Dim socket As Socket = tcplistener.AcceptSocket()
        '  Dim webproxy As New WebProxy(socket)
        '   Dim thread As New Thread(New ThreadStart(AddressOf webproxy.runproxy))
        '    thread.Start()
        'End While
    End Sub

The problem code has been commented out. How else can I continuously monitor the tcp port for sockets?

My WriteToLog isn't working in a service either. Any ideas? It works in all my winforms and console apps.

Is there a service equivalent of Application.Startuppath?

Public Sub WriteToLog(ByVal Filename As String, ByVal Comment As String)
        Dim sw As System.IO.StreamWriter
        Try
            sw = New System.IO.StreamWriter(Filename, True)
            sw.WriteLine(Date.Now & "     " & Comment)
            sw.Flush()
        Catch e As Exception
        Finally
            If Not sw Is Nothing Then sw.Close()
        End Try
    End Sub

Russ

[Slow_Learner]

TcpListener is kind of out of my bailiwick. Have you read:
ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfSystemNetSocketsTcpListenerClassTopic.htm
ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfsystemnetsocketstcpclientclassgetstreamtopic.htm
and
ms-help://MS.VSCC/MS.MSDNVS/cpref/html/frlrfsystemnetsocketsnetworkstreammemberstopic.htm

From the example it looks you're using a different way of dealing with TcpListener though, so these may not be helpful. I have no idea beyond that.

As to why your logging isn't working, why don't you put something in your exception handler to write an event log entry on a catch. Not sure why that's giving you trouble.

As for Application.StartupPath, it works fine in a service (just tested it). The trick is to add a reference to System.Windows.Forms.dll in the Project menu -> Add Reference...

[russgreen]

So is it OK to use Application.Startuppath with a service? I wasn't sure thats all.

Thanks for all your help

Russ