opening an application from another application in the same solution

[BillE]

I have a solution with two windows forms projects in it.

I would like to be able to execute Project B from a button or menu in
Project A.

How can I do this?

Thanks
Bill

[=?Utf-8?B?RmFtaWx5IFRyZWUgTWlrZQ==?=]

RE: opening an application from another application in the same soluti



"BillE" wrote:

I have a solution with two windows forms projects in it.
>
I would like to be able to execute Project B from a button or menu in
Project A.
>
How can I do this?
>
Thanks
Bill
>

In the handler for the button, use System.Diagnost ics.Process.Sta rt.

Process p = new Process();
p.Start("<path to an executable>");

>
>

[BillE]

Re: opening an application from another application in the same soluti

Thanks for the response Family Tree
Would that be the physical path to the compiled executable on the hard disk?
Wouldn't that vary depending on where the apps were installed on the user's
computer?

Bill
"Family Tree Mike" <FamilyTreeMike @discussions.mi crosoft.comwrot e in
message news:6B251168-4403-4E59-9079-381B76AE5B98@mi crosoft.com...

>
>
"BillE" wrote:
>

>I have a solution with two windows forms projects in it.
>>
>I would like to be able to execute Project B from a button or menu in
>Project A.
>>
>How can I do this?
>>
>Thanks
>Bill
>>

>
In the handler for the button, use System.Diagnost ics.Process.Sta rt.
>
Process p = new Process();
p.Start("<path to an executable>");
>

>>
>>

[=?Utf-8?B?RmFtaWx5IFRyZWUgTWlrZQ==?=]

Re: opening an application from another application in the same so

It can be the full or relative path. Typically when I use a solution with
two executables, I will create an installer that places the two executables
into a common bin directory. This makes the relative pathing easy, and I
just use "other.exe" , or the like. I redirect the build output to a similar
directory structure on my build machine.

"BillE" wrote:

Thanks for the response Family Tree
Would that be the physical path to the compiled executable on the hard disk?
Wouldn't that vary depending on where the apps were installed on the user's
computer?
>
Bill
"Family Tree Mike" <FamilyTreeMike @discussions.mi crosoft.comwrot e in
message news:6B251168-4403-4E59-9079-381B76AE5B98@mi crosoft.com...

"BillE" wrote:

I have a solution with two windows forms projects in it.
>
I would like to be able to execute Project B from a button or menu in
Project A.
>
How can I do this?
>
Thanks
Bill
>

In the handler for the button, use System.Diagnost ics.Process.Sta rt.

Process p = new Process();
p.Start("<path to an executable>");

>
>

>
>
>

[=?Utf-8?B?RmFtaWx5IFRyZWUgTWlrZQ==?=]

Re: opening an application from another application in the same so

I'm thinking that's not quite right. I commonly use a registry key to find
the install\bin folder, and build a filename from that. Sorry about the bad
direction.

"Family Tree Mike" wrote:

It can be the full or relative path. Typically when I use a solution with
two executables, I will create an installer that places the two executables
into a common bin directory. This makes the relative pathing easy, and I
just use "other.exe" , or the like. I redirect the build output to a similar
directory structure on my build machine.
>
"BillE" wrote:
>

Thanks for the response Family Tree
Would that be the physical path to the compiled executable on the hard disk?
Wouldn't that vary depending on where the apps were installed on the user's
computer?

Bill
"Family Tree Mike" <FamilyTreeMike @discussions.mi crosoft.comwrot e in
message news:6B251168-4403-4E59-9079-381B76AE5B98@mi crosoft.com...

>
>
"BillE" wrote:
>
>I have a solution with two windows forms projects in it.
>>
>I would like to be able to execute Project B from a button or menu in
>Project A.
>>
>How can I do this?
>>
>Thanks
>Bill
>>
>
In the handler for the button, use System.Diagnost ics.Process.Sta rt.
>
Process p = new Process();
p.Start("<path to an executable>");
>
>>
>>