Seattle, FLEX and .NET

I've just spent basically a week now in Seattle, WA learning all there is to learn about Microsofts latest direction, offerings and what not. All I can say is, watch this space for more.

That being said, I decided to break away for a small bit to check out the local Flex User Group meeting over at Adobe Campus. The presentation was from Mark (CEO) over at Midnight Coders and the topic was "Integrating Flex with .Net and beyond" something which sparked my curiousity (given it compliments both my skills).

Mark proceeded to provide an entertaining breakdown of how one goes about using .NET solutions talking to FLEX User Interfaces, so much so that I kept thinking that his solution, WebORB is above and beyond what Adobe themselves have on offer in such space.

You see, Mark's company has spunup a server-side solution which enables the .NET folks the same capabilities as seen in Adobe Flash Media Server (FMS) and Adobe Flex Data Services (FDS), only without the hefty price tag (combine both or individually and you still pay through the nose) and doesn't require the .NET folks out there to ditch their existing investment.

As to bring FDS into the room for a .NET team, they'll first scratch their heads and try and figure out a way to move forward in trying to connect FDS to .NET (before they even think of opening up Flex).

Not only does WebORB do this, but it tightly integrates in with Adobe Flex Builder so much so that I cast my mine back to the days when I coded in FLEX and simply thought "wow, screw the .NET piece, this should be the way we integrate FLEX with Server-Side code".

It not only integrates, but it also provides code-generation on the fly, so you don't have to sit there and spin your wheels putting together Remoting technology inside FLEX with say "Cairngorm" framework. That part comes for free (you can also override the generation templates to suite your coding style).

WebORB also is able to reflect the various database schemas available out there and creates appropriate code base to suite the CRUD (Create, Read, Update, Delete) solutions. This is great for the average punter, but for the serious developers they'll prefer to broker their data requests with pre-defined query sets, which is why I asked if Mark had plans to integrate with Visual Studio 2005 ADO.NET pieces. As to do this, would truly complete the picture in that regard.

Bottom line folks, this is a fantastic piece of technology that will enable .NET troops to play with FLEX, only without having to ditch or monkey around with their existing code base (investments).

The sad part about this story is that Mark has a great offering here, which illustrates that Adobe appear more inclined to focus on other areas of their business other then integration with existing developerbase (ie how many .NET developers use FLASH/FLEX?). The fact this solution is out there, and not being advocated as much, is truly a shame as a lot of developers could easily benefit from this with minimal investment (it would also help their Software Development Life Cycle more aswell).

If you're a .NET developer and are struggling with FLEX, try this out as I think there is an Open Source version (provided its not for commercial sale) so its free.

They also have some movement around making the same pieces work with AJAX, how it integrates with ASP.NET AJAX is yet to be determined (which I plan to follow up with).

Comments (5)

  1. Weborb in action with flex:

    I have the site driven by weborb and a .net converter running pxt mms conversion to flash. The Screen display is a .NET wrapper that downloads and queues the messages media and passes it to a flex display to display on the big screen. Lol I have even done a full Flex interface for a .NET standalone application through work. Cross comunication needs some work!

  2. Ted Patrick says:


    A few corrections:

    1. Flex SDK is FREE. Zero, Zilch, Nada on costs.

    2. Flex integrates with .NET in the FREE SDK

     – XML via HTTPService supporting REST and E4X

     – Web Services via SOAP Natively

     – Remoting via Florine (free) and WebOrb (free)

    3. Flex Data Services is for multi-user application and is fairly specialized supporting multi-user Data Synchronization, Messaging, Data Management.


    Ted Patrick

    Flex Evangelist – Adobe

  3. Garry Trinder says:

    1. I know, I was one of the many whom signed up for the $15k per CPU (bought 4) only to have Adobe panic about AJAX, release V2 Framework for Free. So yeah, Price wise I’m up to speed on it, as I was given a "please explain memo" shortly after Zorn was announced.

    2. No, Flex Integrates with SOAP/XML standalone. FLEX does not integrate with .NET unless as you put it, WebORB or other products are in place. Given that there used to be a .NET remoting bridge between FLASH and .NET? why has Adobe ditched it in FLEX?

    3. FDS has many flavours or context of use but yeah, not sure on your point here. WebORB does all of what FDS + FMS can do (and more, given that it tightly integrates with Flex Builder) so my question to you folks is, why haven’t you bought this guy or worked with him on porting it to both Java + .NET.

    Given that rumour has it you are ramping up Adobe LiveCycle Data Services? Will .NET folks get a lookin aswell?

  4. DannyT says:

    Scott, good article and refreshing to see focus on shared benefits of using Flash/Flex AND .net, a setup i’m particularly happy using.

    WebORB is an awesome setup and well worth a look for any .net developer who is interested in efficient integration with Flash/Flex.

    Would be even more refreshing to see more articles like this without the ‘handbags at dawn’ between Adobe and MS representatives though 😉

  5. I’ve just been chatting to Mark Piller (CEO) of The Midnight Coders and makers of WebORB , which is a

Skip to main content