Re: Tricky form problem

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Alex Feinman [MVP] (public_news_at_alexfeinman.com)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 11:19:23 -0700

I concur with Paul - a separate dialer is the best solution in this case.
The memory overhead is not going to be a killer - most likely an extra 500 K
or so. As for interprocess communication, there are numerous ways to handle
it and none of them is more complex than the problem with forms you are
having. 

-- 
Alex Feinman
---
Visit http://www.opennetcf.org
"Christian Schwarz" <nospam@microsoft.com> wrote in message 
news:2s0bpgF1g2i3jU1@uni-berlin.de...
>> Why does it have to be a single application?  Couldn't you start a
> separate
>> phone application at an appropriate time to handle dialing or whatever?
>
> I've already thought about this.
>
> There are at least the following two reason against this solution. First, 
> it
> would greatly complicate the communication between the Phone class and the
> rest of our application. For instance, calling a special phone number or
> sending a short message automatically would require inter-process
> communication. Second, the additional memory overhead required for running
> another .NET CF application could be the overkill.
>
> If there's really no other solution, I'll have to split it into two 
> seperate
> applications ...
>
> Greetings, Christian
>
>
Quantcast