Stephan Pilz wrote:
Please don't ask why I do it so, because there is no other way
Keep that up and you'll be completely on your own in no time. Since your ASP.NET WEb Service cannot show a user interface on the server hosting it, you'll have to supply a UI some other way, like a normal Windows Forms app running a custom TraceListener exposed as a singleton class inside a WCF Service. Well, a rather convoluted solution would be to create your own implementation of a TraceListener, setup as a singleton, in a host application that shows all incomming trace messages. This trace listener would be exposed through the host as a remotable object, or do the same thing as a WCF service hosted in a Windows Form or Console application. In your Web Service Global.asax page, in possibly the Application_Start, Session_Start, or Application_BeginRequest handlers, you'd get the reference to the custom trace listener, add it to the Trace.Listeners collection in your Web Service, handle the call and output your trace messages. The custom TraceListenerwould output any messages to a TextBox, Console window, log to a file, ..., whatever you want. The downside is that this is a convoluted solution. The up side is that is lets you deploy your web service to multiple servers and still log all trace messages to a single window on a single monitoring workstation.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007