Slashdot Mirror
ASP.NET Ajax Released
darrenkopp writes "Microsoft released their anticipated AJAX framework that integrates with their ASP.NET product .It is a fully supported product (24x7 phone support), but is completely free! They are releasing the source for it as well."
The word "source" doesn't even appear on the frontpage of that, nor on the "learn more" page. The Download page says the toolkit is shared-source but none of the other stuff mentions the source. Docs don't mention source at all.
Looking at the terms of use page, this is hardly a free license, and it's certainly not opensource unless they've really managed to bury it within the site somewhere.
Care about privacy? Read this!
... how innovative of them!
http://outcampaign.org/
the support center phone numbers all start in 976, and they charge $14.99 per minute.
This sucks for all those companies whose core business is making an AJAX framework.
Please correct me if I got my facts wrong.
It is a great tool in my opinion and easy to integrate with existing ASP.Net applications.
.Net 2.0 was the Ajax Control Toolkit (separately available w/ source)
s px?ProjectName=AtlasControlToolkit
But What I really like about Microsoft Ajax for
http://www.codeplex.com/Release/ProjectReleases.a
On a client-side Windows system, we have the JavaScript for the AJAX functionality running in the browser. The browser itself, depending on which one is being used, may be running on top of .NET 2.0. .NET is then running on top of the userland Windows subsystems. The userland subsystems are running on top of the NT kernel. The NT kernel is then running on hardware.
.NET. .NET is running on the userland Windows subsystems. These subsystems are running on the NT kernel. The NT kernel is then running on hardware.
The server side isn't much better. We have an ASP.NET application running on
We keep seeing layer upon layer being added. While this may make things easier for developers, the resulting application stacks end up consuming much in the way of system resources, both for clients and servers. I find we're also losing reliability as we go higher in the stack. AJAX applications and ASP.NET are highly prone to failure. Web browsers are known to crash easily enough. At least the NT kernel is becoming somewhat stable these days.
Say what you will about it, but it works really well. It's a fast easy way to develop AJAX pages: Visual Studio with Atlas. Of course, it's how Lord Vader would develop software, but it's still good stuff.
So, are they specifically targeting IE and Firefox (at least we're finally past the days when they'd just target IE and say to hell with the rest of the world) or are they building it on commonly-available JS+DOM functions that will work in Opera and Safari as well?
I've been poking around the site, and haven't found anything yet.
agreed. it actually works rather well and i hate using IE so I didn't even bother loading it up. All functionality is there, Microsoft actually did a decent job on their AJAX. Now the real question is, will they allow it to be used on apache or will they restrict it via their license? My bet is they wont allow it on an apache server so they can gain a greater market share, though its doubtful it MUST run on IIS.
Oh come on, stop exaggerating. At the time of writing, there are a total of 14 comments in this story. I can't find the 1/7th of one comment which you claim was not negative.
Chernobyl 'not a wildlife haven' - BBC News
Heh, unlikely. First of all, it's pretty tightly coupled to .NET, designed to use the .NET data binding mechanism. While ultimately it really is just a bunch of JavaScript libraries, it's the fact that a bunch of the connector functions are generated on the fly based on .NET components that tie the libraries to the server technology.
While there is some neat stuff in there, I would rather have a choice of development technologies. That, and the fact that you are relying on the framework running bug-free under the browsers you need to support. If that's not the case, good luck fixing it.
Oh, and I have tried it.
...the foaming cleanser
I wonder. Is it easy to create custom controls with ASP.NET AJAX? At the moment we're working on a ASP.NET 2.0 based web application. One of the demands of the project is that it's completely AJAX driven. We're researching to see if we can make our own custom controls using JSON. The Javascript makes calls to the server-side code which returns HTML in a string.
I looked through the source-code of the Ajax Control Toolkit. The source looks clean - Microsoft seems to have hidden all the complex JSON stuff. But I wonder if it's easy to pick up and run with....
Y
Are they eating their own dogfood?
Part of the reason I ask is I notice the MSDN site has a whole lot of new features, but I've found most of it to be horribly slow and clunky in firefox. I'm interested in whether it is using this, and whether there are other examples to look at within Microsoft?
Some of the "showcases" look decent, but most of them just seem like toy sites...
It it on the server side that everything is tied to MS.
> go ahead, mod me down suckers.
And so we did, butt-munch.
Actually you can. Obviously the server side asp.net extensions where you can mark web services as ajax servers and the functionality to raise the nice eventing model requires asp.net at the back end; but the client side libraries (the way to call web services, timers etc.) are released on their own, for use anywhere;
You can download it yourself and see.
I used to be big into PHP web programming, but this was before AJAX got popular. Now I'm thinking of revisiting web programming, changing my mentality to write code with AJAX in mind can be kind of daunting. This toolkit might be the motivation I need as the learning curve seems it might be a little easier than trying to develop in PHP given that I've been out of the loop for a while. Plus, intellisense is friggin awesome.
nothing
I've been playing with this since this last summer. It's come a long way. A few Anti-AJAX friends of mine, who honestly, have been using AJAX concepts for years, but didn't know someone had put a pretty ribbon on it and called it AJAX, really like the ASP.NET AJAX. I think what caught them was the RAD ability now.
I like it because I have customers who wanted a more Windows Forms based design for their web-based applications.
The great thing here is, it is capable of turning SharePoint into a really slick platform. I only wish it worked on SharePoint 2.0 the way it works on 3.0, since I still have customers using the older platform.
Politics is the art of looking for trouble, finding it everywhere, diagnosing it incorrectly and applying the wrong fix.
but does it run on Linux?
A fool throws a stone into a well and a thousand sages can not remove it.
Microsoft could develope zero-point energy and you guys would still find some reason why it was evil.
Sorry linux has such sorry desktop penetration. QQ some more.
TinFoilJones said:
Huh? Did he just...? Are the Obvious Police available?
Are you seriously calling them "monopolists"? How can they be a monopolist in the online, web development arena when folks out there claim that most of the web is dominated by SOTMS (Someone Other Than Microsoft)? You can't have it both ways. They cannot be monopolists if there is a sizeable or even more dominant alernative out there. Now, their philosphy may smack of monopoly, but in reality, they are just another competitor.
OS - Microsoft is a monopoly and Linux, Apple, Sun have failed, or MS is a competitor and Linux, Apple, Sun are doing fine.
Web - Microsoft .NET and IIS are a monopoly and Linux, Apache, Java, Perl, PHP...are dead, or MS is a competitor and others are dominating.
You can't have it both ways. Just admit, you've joined the "in", the "cool", the "hip" crowd of the Anti-Microsoft cult, you've stopped critical thought on the matter, and if it has MS attached, you will instantly hate it. It's o.k. to admit. Really.
Politics is the art of looking for trouble, finding it everywhere, diagnosing it incorrectly and applying the wrong fix.
From their Migrate RC to RTM doc.
The ASP.NET AJAX validator controls that were part of the RC release have been removed. You must remove the following registration entries for those controls from the section and remove any instances of these controls in your pages.
Oh goodie, let me just go back and do that and undo my previous days work. Apparently there will be a fix in the near future, but for now there's a bandaid available.
Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
I didn't say it was tied to IE, I know they are supporting other browsers, and are supporting Mac OS. If you re-read my post, I said it was tied to .NET, which is the server part of which you speak.
Let us look at what AJAX is, HTML, CSS, Javascript, XML, XSLT; And some XSD, for those of us that are washed. I prefer not to use the COM objects, because, well, I prefer not to be "Browser Locked" to an older obsolete browser. I RTFA and found nothing to indicate that Microsoft had added any more to its dotNet product than it had before. If I look for ASP in AJAX, it is not there. If I look for upgrades to maybe XSLT 2.0, or maybe CSS 3.0? Nothing is upgraded. Where am I wrong?
It doesn't bother anyone that adding a single control/extender to the page can create 8 or 9 new JS files that must be downloaded by the client? They are small, but that can really hurt performance.
Isn't the first thing Security people tell people to do to protect against a browser vulnerabilty to disable Javascript? There goes your functionality!
AJAX isn't all that new. It's just a different way of thinking about how the browser interacts with the server. You *could* make your server programming language handle all this AJAX code to call server-side functions from the client, but wouldn't it be better to see the big picture? JavaScript can be used as more of a client, and the server can be more of... well... a server. Also, people tend to be over-using AJAX, which then brings the web browsing experience to its knees.
I think it's better to just use a JavaScript library to handle a cross-browser implementation of XMLHttpRequest that accesses your server, and your server handles those requests? There's really no need for all this complexity that's being introduced.
JavaScript gets a bad wrap, but I think that's generally from people who don't understand the language. You can do very interesting things with it... you just have to know what you're doing... and what you want it to do.
For someone who's just getting into doing .NET development full time and coming from a PHP based development environment I'm really happy to see it. Nothing worse than my old employer coming at me with a different AJAX suite every week. If its as easy as everything else I've done with ASP.NET then it'll be a wonderful treat.
For some reason I refuse to use either spell check or the spacebar properly.