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.
So what is the roadmap for Flex and .NET? I think Adobe’s in an awkward position. WebORB has done a fantastic job of building a Flex/.NET solution. Adobe has focused on the Java market. Right now marketing and engineering efforts are both targeting Java. There has been some success, but I don’t think FDS is taking off the way Adobe hoped it would. That makes it difficult for them to think about expanding .NET support because they’ve invested a lot of time in Java and that needs to pay off before they can chase other markets.
I think it boils down to the fact that right now, the .NET support they have is enough. .NET shops aren’t clamoring for Flex Data Services, though WebORB seems to do pretty well. At this point, FDS is a tough sell. I think it’s a revolutionary product, but it may be a bit ahead of its time and selling the benefits of FDS to companies takes time. Once Adobe establishes demand for Flex Data Services, they’ll be in a position to support more platforms. Ultimately I think that’s going to be in the form of buying WebORB. But right now Adobe needs to worry about getting FDS more mindshare in the enterprise. As that expands, so will Adobe’s support for other platforms.
[tags]Flex, .NET, WebORB, Adobe[/tags]
TweetRelated posts: