| Author Name |
Status |
Posted Time |
| Henri Teipel |
|
5/7/2008 12:17:18 AM |
| Author is Offline |
|
Hi all, I've read elsewhere that MS AJAX is going to be an integral part of .NET 3.5 (but correct me if I'm wrong).
Anyway, I'm trying to think ahead here, so lets think of the following use case:
A setup is installing a web-application that uses MS AJAX on a server.
The server happens to be running the .NET v3.5 framework (let's pretend we are in the future).
web.config maps the tagkey 'asp'
to System.Web.Extensions, version=1.0.61025.0, so the application can use the asp:ScriptManager tag.
Now what happens when this runs on v3.5? I would think that this tagkey mapping is already in place, so I don't need it in web.config. But as I see it, I will now have the same tagkey refererence to two different assembly versions, so how would the compiler know which assembly version the ScriptManager class should map to?
I tried doing this on the latest Orcas release, but the System.Web.Extensions.* wasn't included (yet?).
I'm just trying to think ahead and see if I can come up with a solution that doesn't break just because my application was written before v3.5, but it's pretty hard given I don't know what the ASP.NET team are planning. Anyone care to enlighten me on the proposed plans for ths use case? Or is it even a problem?
|
