Launching .net forms from non .net application - reducing overhead

  • Thread starter Thread starter ErnieJ
  • Start date Start date
E

ErnieJ

I a have a .net application which displays the results of
a database query on a form in graphical format (i.e.
charts and maps). This application is launched from
another legacy Windows application with the query
determined by a number of parameters. This calling
application is not a .net app and does not support the
type of display I am able to achieve with vb.net.
Currently, anytime a user in the intitial application
wishes to see a map a new instance of the .net application
is started up. The overhead of starting the app,
initialising and first login to the database is quite
large compared to the time taken to run the query and
display the results - a second query takes only a fraction
of the time when run from within the .net app.

My question is this :- is there a way to incur this
initialisation overhead only once while still being able
to either launch or call the .net application frequently
from a non .net application ?

Any assistance is much appreciated.

Cheers
 
Hi ErnieJ,

Does this not sound as an always running service or a webservice.

Just a thought.

Cor
 
Back
Top