________
http://horsebetting-tips.com

LaTex - I studied Maths many years ago and we were shown Latex. I just thought I'd stick with paper and pen ;)

So far, the best available solution seems to auto-generate documentations based on XML comment markup. Yet, this approach has significant limitations:
- editing basic HTML without wysiwyg is a pain.
- no graphics allowed.
- documentation structure is rigidly bound to the code structure.

Then, I think part of the problem lies in the way we access the documentation. I am no big fan of PDF, except when the document is really formatted as an eBook with the possibility to print. Then, HTML is somewhat OK, but going back and from from Visual Studio to the browser is tedious.

To some extend, I think a better solution would be to have a Visual Studio extension that would render (real-time) the document of any browsed item, either local code (with the possibility to edit it) or 3rd party libraries (docs being embedded into the XML file along the assembly).

Just to clarify: END to END = Best recommended route.
(Client shell with CONFIG OPTIONS explained and Service Scenario)
Like you mentioned here there are few things that you are recommending
that I think make sense (like protoBuf)

In Any case we are very excited to explore this.
Thank you very much for your excellent work!

Sorry about the name. Fixed and will never happen again!

We are currently using latest public v1 (just to be on the safe side), hence the empty constructors and attribute bindings. I definitely look forward to decoupling and the other v2 enhancements!

Re Windows Service: Yes you can easily do that and don't need to create worker role. Just build the cloud engine with the builder class and start the created host on service start, while stopping it, when service stops. All threads and specifics will be handled internally.

This is not greedy at all. As long as you stick to the design guidelines and recommendations recommended by CQRS, even more interesting possibilities are enabled for the future. That's by the design.

Re your sample:

InAssemblyOf<> just tells the domain about the assemblies, where the commands are located. You don't need to point domain at every command. I would also recommend to start protoBuf serialization instead of data contracts, as shown in the last sample - it will help you to avoid many problems down the road (aside from better performance and cross-platform support).

Otherwise, your code just looks fine.

What exactly do you mean by END to END sample?

Re Trace log: I'll try to expose the configuration to change logger today. There will probably be a blog post on that later.

Any Ideas?

class WorkflowService : ServiceBase
{
private WorkerRole worker;

public WorkflowService()
{
InitializeComponent();

worker = new WorkerRole();

}
}