Quote from “Developing Rich Clients with Macromedia Flex” Chapter 20
“Direct Invocation on .NET Infrastructure
Macromedia announced that the roadmap for Flex will include a native .NET port of Flex. We are assured that the aim of this native port is to ensure a “write once, deploy anywhere” approach with MXML. Consult the documentation for the .NET port of Flex when it’s released, for details of how to perform tight Flex and .NET integration. We’ll endeavor to update the accompanying Web site for the book with additional notes on new product features in future versions of Flex.”
Does anyone know if this is still true?


Flex already runs on .NET. Take a look, you get full blown Remoting, Data Management and Messaging:
http://www.themidnightcoders.com/weborb/dotnet/
Is this a direct replacement for FDS? Is there full support for everything FDS does?
I would not call it a replacement, since FDS does not run on .NET. It is an implementation of the functionality you find in FDS, but on the .NET side. So far the product fully implements Remoting and Messaging(clients can use RemoteObject and Producer/Consumer MXML/API); there’s a partial implementation of DataManagement as well. We’re working on adding our own DataManagement implementation for .net (somewhat different than the FDMS approach). The new data management is based on the ideas borrowed from Rails’ ActiveRecord.
[...] Neil posted a question on his blog about the roadmap for Flex and .NET. The official answer of course, is that you can invoke .NET web services using Flex and as a result, Flex “works” with .NET. But Flash remoting and Flex Data Services functionality is missing, though WebORB provides those features. [...]
as it turns out (and the secret is no longer a secret), the Coldfusion Scorpio (CF8) team have been working on CF calling .NET assemblies as easy as it does Java.
so if you’re after doing Flash Remoting a possible alternative is to use ColdFusion’s built-in remoting capabilities that calls into your .NET code. no idea what performance would be like compared t0 natively calling .NET classes - have to wait until the new version ships before making any assumptions.