Inserting "triggers" into a vb.net app

[Rob]

Hi,

Given I have a button on a Windows form in a VB.net app.... I would like to
know the best way to accomplish the following...

Upon clicking the button I would like to launch another VB.net application,
furthermore, I would like to send parameter data to this app, as well as
receive data from the launched app (back to the original app) upon
completion.

I would also like to ensure that the source app (the one where the new app
is launched from) is not enabled during the time frame that the "launched
app" is in use.

Thanks !

[SetonSoftware]

On Jun 5, 8:20*am, "Rob" <[e-mail]:

Hi,

Given I have a button on a Windows form in a VB.net app.... I would like to
know the best way to accomplish the following...

Upon clicking the button I would like to launch another VB.net application,
furthermore, I would like to send parameter data to this app, as well as
receive data from the launched app (back to the original app) upon
completion.

I would also like to ensure that the source app (the one where the new app
is launched from) *is not enabled during the time frame that the "launched
app" is in use.

Thanks !

Rob

You second application is still an assembly. Therefore you could add
it into your main VB project, set a reference to it, and instantiate
objects (like Forms) in it. You can pass paarmeters either by creating
properties of the form object to receive them or, even better, by
adding these parameters to the constructor (New method) of the forms
objects you need to instantiate. When your process completes the
return values can be placed in an object that is read by the main
application. Since this is being down sychronously, the process of
passing and receiving data is much simpler.

Access to the main app can be prevented by setting the main forms
Enable property to False.

Thanks

Carl

[Rob]

Thanks for responding Carl...

To add a little more complexity...

What if the 2 apps were designed that they could be run separately... (i.e.,
the second app could either have data passed from the first app, or the user
could enter data into it directly if it was run as standalone).... might the
command line be the way to go... I think I know how to get data to the
second app from the first using the command line, but not the return
data....
"SetonSoftware" <se************@verizon.netwrote in message
news:83**********************************@j22g2000 hsf.googlegroups.com...
On Jun 5, 8:20 am, "Rob" <[e-mail]:

Hi,

Given I have a button on a Windows form in a VB.net app.... I would like
to
know the best way to accomplish the following...

Upon clicking the button I would like to launch another VB.net
application,
furthermore, I would like to send parameter data to this app, as well as
receive data from the launched app (back to the original app) upon
completion.

I would also like to ensure that the source app (the one where the new app
is launched from) is not enabled during the time frame that the "launched
app" is in use.

Thanks !

Rob

You second application is still an assembly. Therefore you could add
it into your main VB project, set a reference to it, and instantiate
objects (like Forms) in it. You can pass paarmeters either by creating
properties of the form object to receive them or, even better, by
adding these parameters to the constructor (New method) of the forms
objects you need to instantiate. When your process completes the
return values can be placed in an object that is read by the main
application. Since this is being down sychronously, the process of
passing and receiving data is much simpler.

Access to the main app can be prevented by setting the main forms
Enable property to False.

Thanks

Carl