Here is a list of MSDN CF articles:

http://msdn.microsoft.com/library/en-us/dnnetcomp/html/netcfadvinterop.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/netcfintrointerp.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/netcfwebservices.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/animationcontrol.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/ProcessManager.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/netcfuiframework.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/netcfdeployment.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/netcfPPCtoCE.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/PPCGuidGen.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/ImageButton.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/BackgroundProcess.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/CompactFXDebug.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/PPCSignatureApp.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/retrievedeviceid.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/netcfdumpbinpinvoke.asp
http://msdn.microsoft.com/library/en-us/dnnetcomp/html/messagewindow.asp

I've taken a look at the MSDN article at: http://msdn.microsoft.com/library/en-us/dnnetcomp/html/netcfuiframework.asp regarding multiple forms. I've changed the way my forms load, etc based on your example. However, I have a question regarding the "run" method of the FormStack class. After making this change to my code, I've noticed that other applications (like Calendar) are slower when my application is running. I think the application.doevents is the culprit.

Have you noticed this situation as well? Do you have any ideas as to address the performace issue? Thanks in advance for any insgith

I am looking at the formstack as described in the MSDN article. When running an application using the formstack on the full .NET framework the exception "You cannot pop the entire stack!" does not get caught which causes the application to throw the exception and does not gracefully exit (it keeps running in the background). On a pocketpc the exception is caught and there is no problem. Anyone familiar with this problem?

I see the same problem when running the sample in the public .NET CF 1.0 SP3 Beta. I have solved it by gracefully exit the app.
I've added an Exit-method to the FormStack class:

// Exit application
public void Exit()
{
Stop();
System.Windows.Forms.Application.Exit();
}

Instead of throwing a new exception, I do:

public void Pop(uint FormsToPop)
{
if(stack.Count <= FormsToPop)
{
Exit();
}

... or a cleaner way:
Alter the Run-method by adding an Application.Exit.

public void Run()
{
do
{
System.Windows.Forms.Application.DoEvents();
}
while(List.Count > 0);

// Exit application
System.Windows.Forms.Application.Exit();
}

Instead of throwing a new exception, simply call the Stop-method:

public void Pop(uint FormsToPop)
{
if(stack.Count <= FormsToPop)
{
Stop();
}



Andy Sjostrom
MS MVP - Mobile Devices
http://www.businessanyplace.net

quote:

---

Originally posted by samwise1130

I've taken a look at the MSDN article at: http://msdn.microsoft.com/library/en-us/dnnetcomp/html/netcfuiframework.asp regarding multiple forms. I've changed the way my forms load, etc based on your example. However, I have a question regarding the "run" method of the FormStack class. After making this change to my code, I've noticed that other applications (like Calendar) are slower when my application is running. I think the application.doevents is the culprit.

Have you noticed this situation as well? Do you have any ideas as to address the performace issue? Thanks in advance for any insgith

---

You are right. It is the DoEvents that causes the performance degradation. Obviously not a desired effect. In my projects this hasn't been a show stopper, though, since the user stays within my app until the user is done. Then... I exit the app. Good from a logo POV? No. But I don't care. [:)]

Andy Sjostrom
MS MVP - Mobile Devices
http://www.businessanyplace.net

An optional approach to the DoEvents message pump would be to use a normal Windows form as the application's entry point. Then use:

MyApp.fs = new FormStack();
MyApp.fs.Push(typeof(MainForm), true);
this.Hide();

in the form's constructor or on an event (button, menu, etc).
This way you get to use Chris Tacke's excellent stack ideas but without the performance bandit DoEvents.

Andy Sjostrom
MS MVP - Mobile Devices
http://www.businessanyplace.net

I am the Professional Services Recruiter for Plumtree Software. We are actively recruiting strong web developers who possess strong .net or c# or J2ee skill. www.plumtree.com for more info. (We have job postings on Hot Jobs currently.) The positions can be based anywhere in the US as long as the individual is located to an airport. 100% travel during the business week. (Nasdaq: PLUM) We are an equal opportunity employer.

I look forward to talking with you direct or hearing from your colleagues. Plumtree currently leads the enterprise portal application market (radical open architecture built on above languages makes our solution robust and cost effective)

Come talk to me.
Rebecca Munguia
Plumtree
xxopenresourcexx@yahoo.com