>That sounds most useful, for sure. But I got to wondering how it can accomplish this.

The same we we accomplish it in old ASP.

< %
user_agent = request.servervariables("HTTP_USER_AGENT")
response.write("The browser you are using is: " & user_agent)
% >

This returns a string with browser name and version information. This is somethign that has been established for quite some time.

>1) Who writes the code responsible for doing the best rendering job for each browser?
>--- Does MS write it for IE, AOL for NetScape, etc.?

When it comes to ASP.NET controls, MS writes them. You can subclass them if you want.

>2) How does it get installed and maintained on our systems?

Just like every other class in the .NET Framework.

>3) Can the code responsible be maintained separately for each independent browser?

They're part of the same class. They may delegate, but I don't really think thats whats happening.

>---a) Can I identify separately the version/level/build of the subject code for each of IE, NetScape, Opera, etc.?

Usually.

>---b) Can I see which version of the corresponding browser each is designed for?

WHen there are major differences between versions, multiple versions are handled.

>---c) Can I have separate versions (of this 'best-render-code') for different versions of each possible browser?

ITs already done.

>---d) Can I add/update/remove separate versions of the 'best-render-code' as I see fit?

SUre, subclass the Server Controls. Or just wait for an update to the .NET Framework.

>4) Does this create a nightmare for maintenance?
>--- Is this another means to push other browsers out of the picture?

How would it be? Its the exact opposite.

>While I can see how nice the concept described by the description (quoted above) is, it looks like it could come at significant cost in terms of future flexibility to choose a browser of preference.

How so?

>I think that knowing how this is implemented would be useful information.

Sure, use IL DASM to look at the IL code for the server controls.