Using only parts of the release of the community of mobile applications for developing WM 6.x

I am planning an architecture for a distributed business process system in which many different devices of different types should be supported in very similar use cases.

In particular, I will need to support

• Windows Mobile 6.x PDA
• PC workstations

These applications will serve a fairly simple business logic, so I do not want to use a supercharged architecture for it. However, I need to support:

• remote updates
• disabled client scenario for PDAs (and possibly for PCs)

While researching the correct link architecture, I came across the Mobile Application Developer Community and Mobile Contribute for this version. I was interested in the following:

• Disconnected agent and connection monitor to support the script of mostly disconnected clients
• Mobile update application block for update support

I also know about the SCSF compiler for the desktop platform.

Now, here are my questions

• In your experience, is the MCSF extension for VS2008 / WM6.x / .NET CF 3.5 mature and stable enough for production use? I do not want to be a victim of the knowledge that it is not suitable for use in business, while I am in the center of the project.
• , MVP CAB. . Community Community Release MCSF ( , , MVP ..)? , , .
• . , CAB/SCSF , , , , , , . ( WinForms ). ?

, / , , MCSF/SCSF.

, :)