On Tue, Dec 6, 2011 at 4:44 AM, David Kean wrote:
> Using SOAP (default protocol for Web Services) can be hard to consume by
> other languages when its produced by .NET (and in general its hard unless you
> have tools to help you generate code).
>
> REST seems to be the way to go these days, WCF
Do it with JSON/XML over HTTP. Most client platforms will have support for
this.
If you're starting from scratch I'd start with the new ASP.NET WebAPI
http://www.asp.net/web-api
I've also heard very good things about http://www.servicestack.net/
Don't go the SOAP route unless you really have to.
I'm pretty sure there is an open source biz logic engine...i was once
looking for this type of functionality...biztalk does this but pretty
expensive and maybe a over-kill.
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Rob Andrew
Thanks Greg
Regards Peter Maddin
Applications Development Officer
PathWest Laboratory Medicine WA
Phone : +618 6396 4285 (Monday, Wednesday,Friday)
Phone : +618 9346 4372 (Tuesday, Thursday)
Mobile: 0423 540 825
E-Mail : petermad...@iinet.net.au; peter.mad...@health.wa.gov.au
The contents of
Folks, I get irritated by the way resources (mainly styles) can accumulate
inside the XAML for controls and windows, often making a huge mess. I ran an
experiment to evaluate a possible way of pulling most of the resources out
controls and putting them in separate xaml files. My choice was to have
