October 2006 - Posts
It looks like deploying ASP.NET AJAX sites won't be as easy as we thought. Beta 1 of the ASP.NET AJAX Extensions now installs in the Web server's Global Assembly Cache (GAC). You can't just copy the DLLs into the bin folder anymore. Apparently, this change is because some operations require Full Trust.
Yes, using the GAC makes patches and updates easier: You can replace only one copy per server rather than multiple copies of the DLL scattered in the bin folders of individual webs.
However, this is real downer for people using shared hosting. Understandably, ISPs don't want to install beta software on production machines. That means sites that want to feature ASP.NET AJAX right away - or have deployed the CTPs - have to wait until the release version. (Microsoft keeps release dates close to the vest, so who knows how long the delay will be.)
Even after the release, ISPs can be slow (or refuse!) to install new components. It's unfortunate that these wonderful client-side enhancements can get mired in server-side issues and delays.
BTW, I'm still angry that I had to abandon an interesting Visual Studio Tools for Office (VSTO) project because the software requires Full Trust in my public web site. For security reasons, ISPs limit individual webs on shared servers to Partial Trust.
Just saw this comment from Scott Guthrie indicating we're in for some ASP.NET 2.0 AJAX Extensions goodies - perhaps next week:
"We are hoping to have a major release next week with a lot of major updates and bug fixes (lots of good things coming).
"The team has been pretty heads-down working on it the last few months. It is almost there...
"P.S. All features from the past CTP will be in the drop next week. Some will be in the "core" supported 1.0 files, while some will be in the add-on on top which we aren't marking as supported just yet. But they will all work together."
This week, I'm finally getting around to exploring Windows Presentation Foundation (WPF) more deeply. As a starting point, I went through the online course, Developing Rich Experiences with Microsoft® .NET Framework 3.0 and Visual Studio® 2005.
ASP.NET developers will find themselves in familiar territory because WPF uses XAML and declarative syntax that's much like the XHTML markup in Web forms. I was curious as to whether it will be possible to use an ASP.NET-style single-page model in WPF to keep the code with the markup. I find that very convenient in ASP.NET - especially when creating samples to post in the newsgroups.
The next step is to start building a little XAML application of my own. I absorb new stuff faster by poking about in trial and error mode once someone gives me a general idea as to what the technology can do.
BTW, someone at MS eLearning might want to check the transcripts for Parimal Deshpande's "Voice of the Expert" bits in the course. Unless Microsoft is developing a new agriculture platform, Parimal probably wasn't referring to Windows Farms applications. (But thanks for the smile!)
I guess there are going to be a lot of these posts today, but it really is quite an honour to be chosen as an MVP.
I'm in the Visual Developer - ASP.NET category. See you at the MVP Summit!
"The Microsoft MVP Award is our way of saying thank you and to honor and support the significant contributions you make to communities worldwide. As a recipient of Microsoft’s Most Valuable Professional award, you join an elite group of technical community leaders from around the world who foster the free and objective exchange of knowledge by actively sharing your real world expertise with users and Microsoft. Microsoft salutes all MVPs for promoting the spirit of community and enhancing people’s lives and the industry’s success everyday."
More Posts