DSS design considerations for a Winform orchestrator application

What is the better approach?:

1. Creating and calling a Winform from within an orchestrator service (Robotics Tutorial 4 C#)

2. Creating a winform application from scratch, hosting DSS, and orchestrating the services directly within the Winform application (similar to Hosting tutorial #4).

I'll be coordinating about a dozen or so different services.Choice 2 seems like the simpler choice.Are there any considerations?

Thanks!

[718 byte] By [TMR02] at [2008-1-8]

«« Getting "The Memory Could Not Bre Read" When trying to open note pad and Paint!! pleas
»» directx xna

# 1

i would suggest 1. Being within a service environment gives big reliability, concurrency benefits

GeorgeChrysanthakopoulos at 2007-10-2 >

top of Msdn Tech,Microsoft Robotics Studio,Microsoft Robotics - Decentralized Software Services (DSS)...

# 2

Also there is a third choice. If you have explored VPL version of Robotics Tutorial 4 you should have noticed that it uses the Dialog service (located at samples\Misc\Utility\Dialog) that simply is a WinForms service exposing operations and notifications for the actions and events on the form (here, ButtonPress and ButtonRelease). Another service (such as a VPL diagram) can then subscribe and interact with it.

OmidK.Rad at 2007-10-2 >

Microsoft Robotics Studio Hot Topic

Microsoft Robotics Studio New Topic

Microsoft Robotics Studio

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech

it's Archive about 'DSS design considerations for a Winform orchestrator application...'

DSS design considerations for a Winform orchestrator application

Microsoft Robotics Studio Hot Topic

Microsoft Robotics Studio New Topic

Microsoft Robotics Studio

Site Classified