I was involved in a project on a customers ASP.Net CMS to embed a flex application which enables the user to enter some parameters and see how they affect the results which are displayed in a stacked bar-chart. The formula's that are used to calculate the results are highly sensitive therefore the logic could not be embedded in the flex application, therefore the only alternative was to expose some .net web services to provide the functionality. Although the data that is returned by the web services is basic and fairly minimal, from my experience of using flex, I was concerned that this wouldn't be as straight forward as it seemed. One of my concerns about consuming .net web services with flex was whether Microsoft actually adhere properly to web service standards, therefore I decided to return the data as JSON. This would mean that we wouldn't be relying on Microsoft to properly adhere to web service standards and my colleague who was writing the flex application had experience of consuming JSON, albeit from web services written using Ruby.More...