Tagged with AJAX
In case you didn't catch it, I participated in a webcast called geekSpeak. This webcast was hosted by Glen Gordon and Chad Brooks. The topic today was "Silverlight and Line of Business Applications". While geekSpeak's usually focus on hands-on examples of creating code, we took a different tact today and discussed the larger topic of where Silverlight fits in the development ecosystem (at least Microsoft's ecosystem).
For my money, the real benefit in Silverlight is for applications that cross the firewall. This means Line of Business applicaitons are really for B2B and B2C solutions. Unfortunately, what I hear from the community is that people see Silverlight as a solution for porting their desktop and traditional 3-tier applications to the web. Is this a good idea? I don't think so. The problem is that desktop development usually involves business objects that tend to have a direct connection to the database. Moving these sorts of applicaitons to the web means that you need to create an extra layer of communications and serialization. There is a cost both in development and performance for these extra layers.
Its been a crazy weekend. I've moved into my new servers at MaximumASP and I could not be happier. On the new server, I have full control over the box so I can make it work the way it should have. In the old system, I was doing all sort of re-routing tricks to host 8 sites under a single web site. It was a nightmare that made it difficult to use new technology (e.g. if the root site was using AJAX 1.0, I couldn't have one of the sub sites use 3.5). All that is over and hopefully you will see some new stuff on this site soon! .
Here comes the favor...there is likely some parts of the site that do not work as they did on the other server because I missed a file or two in the transfer...if you see anything that should work that doesn't, please email me at email@example.com.
One thing I noticed was that when using the VS 2008 Publish function, some files were inexplicably not transferred. It may have been the "Content" type or the Silverlight links in some of the project...I don't know. But I've attempted to find all the holes that the "Publish"'s missed but I could have skipped something.
As some of you know I am writing an appendix about WPF/E for the new revision of Chris Sells/Ian Griffith's Windows Presentation Foundation Book. While editing the appendix, Ian Griffiths noted that using agHost.js file seemed like a good temporary solution, but that there needed to be an ASP.NET control that was smarter. This has been on my mind for the last few weeks so I finally spent a sleepless night writing a first version. This first version took some ideas and code from Mike Harsh's version found here.
For those of you who know how WPF/E SDK works, it uses a script called aghost.js file to emit the right tags (object tags for IE, and embed tags for firefox). I also had some other things I wanted from an ASP.NET Server Control. Here are the features I added:
Dan Wahlin has posted the code (though not a live example) of using Amazon, WPF/E and ASP.NET AJAX to do an Album Lookup Example. He has the code, a video of it working and a talk about how he created it up on his blog. Check it out.
I am delving into WCF and AJAX (not at the same time) lately so I wanted to see if they were compatible. According to this whitepaper on ASP.NET (follow the link and scroll down to "Support for WCF Web Services"), the RTM of AJAX does not support WCF. It seems they removed it so they could make it work better in a later release. The promise is that by the Orcas release of VS, they will be compatible.
This further cements my opinion that releasing .NET 3.0 without FULL tool and compatibility is nonsense. Without a good across the platform support (e.g. WCF and ASP.NET stack working well together), a workable WPF editor (Cider is horribly broken currently...change the default editor for XAML to XML, you'll be happier), and projects that actually compile out of the box (WPF projects don't compile currently without some hand-editing of the XAML). Microsoft has always been about tools more than technology, that's why I've been with them so long. If we need to cruft together a bunch of installs to make stuff work, I'd be doing that in Java and Linux.