problem with component service and terminal server

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jussi K - 12 Aug 2003 19:02 GMT

Hi!

I'm using Win2000 server as an component server and as a terminal server. I
have a component that i'm running on a component services. The component
includes one form. The problem is that when terminal server users log on to
their sessions they can't see that form. If i register this DLL to the
system32 the form is shown very fine. But unfortunately i need component
services to run some of this component's parts remotely.

How could i solve this problem without making any changes to the VB code? Is
it possible to show any forms from component services?

Thanks,

Jussi

Reply to this Message

ASP.NET - 26 Aug 2003 06:12 GMT

basically, you should not be showing any forms, message boxes or any other
type of UI element in your middle-tier components. There are several
reasons for this one of the most fundamental being that your application
architecture should not require someone to be sitting at a server watching
forms and message boxes. In fact, it is a good idea to set "Unattended
Execution" in the project's properties. If you want to report errors,
return codes, etc, you should have an exception handling framework set up
which "bubbles" things back to the client that called the component. You
can also log in the system event log.

HOpe that helps,
Stephen

> Hi!
>
[quoted text clipped - 11 lines]
>
> Jussi

Reply to this Message

VB Forum / COM / August 2003

problem with component service and terminal server