G
Guest
I see that the RTM version of ASP.NET AJAX requires installation of the
ASP.NET AJAX assemblies in the GAC. I've been through all the docs, and
deployment, per se, is never directly addressed.
1. Is installing System.Web.Extensions to the production server's GAC the
only (additional) step required to support ASP.NET AJAX? Or is the
distributed installer (.msi) doing other stuff that would be required in a
production installation? I've read elsewhere that
System.Web.Extensions.Designer must be in the GAC as well, though I suspect
that only applies to developers.
Modifying our installer to add the one assembly to the GAC is no problem; is
there any reason to run an additional .msi for production? (Of course, the
ASP.NET AJAX .msi does other useful things when it runs on a developer's box.)
2. Were Microsoft to update the assembly via Microsoft/Windows Update, would
it simply replace the RTM version? Would the assembly's reference in
web.config have to be updated, or would the app continue to work if the
reference still indicated the RTM version?
<whine>On a related note, exactly how does Microsoft expect developers to
get hold of the assembly file itself (System.Web.Extensions.dll)? Granted,
it's not terribly difficult to copy from the GAC -- it took me a couple of
tedious minutes of command-line work -- but surely there's a simpler
way.</whine>
ASP.NET AJAX assemblies in the GAC. I've been through all the docs, and
deployment, per se, is never directly addressed.
1. Is installing System.Web.Extensions to the production server's GAC the
only (additional) step required to support ASP.NET AJAX? Or is the
distributed installer (.msi) doing other stuff that would be required in a
production installation? I've read elsewhere that
System.Web.Extensions.Designer must be in the GAC as well, though I suspect
that only applies to developers.
Modifying our installer to add the one assembly to the GAC is no problem; is
there any reason to run an additional .msi for production? (Of course, the
ASP.NET AJAX .msi does other useful things when it runs on a developer's box.)
2. Were Microsoft to update the assembly via Microsoft/Windows Update, would
it simply replace the RTM version? Would the assembly's reference in
web.config have to be updated, or would the app continue to work if the
reference still indicated the RTM version?
<whine>On a related note, exactly how does Microsoft expect developers to
get hold of the assembly file itself (System.Web.Extensions.dll)? Granted,
it's not terribly difficult to copy from the GAC -- it took me a couple of
tedious minutes of command-line work -- but surely there's a simpler
way.</whine>