Have you learned anything the hard way about whether adding System.Web.Extensions to the GAC is sufficient for final deployment in lieu of using the .msi?
Hey Microsoft, could you give us a hand here with deployment instructions to a production server, not a development environment? My team uses MSBuild to script fully automated deployments for our enterprise environment.
Why does the following assemblieg get added to the web.config and where can I get an MSI that has these? I dont see why they are being included anyway. When I use Refelector on System.Web.Extensions and System.Web.Extensions.Design, I dont see any of these as dependancies. As far as where are the files other than in the GAC, look in Program Files\Microsoft ASP.NET\
Microsoft.VisualStudio.ProjectAggregator
Microsoft.VisualStudio.VSHelp
stdole
Microsoft.VisualStudio.Shell
Microsoft.VisualStudio.Shell.Interop
Microsoft.VisualStudio.TextManager.Interop.8.0
Microsoft.MSXML
Microsoft.VisualStudio.TextManager.Interop
Microsoft.VisualStudio.OLE.Interop
Microsoft.VisualStudio.Shell.Interop.8.0
ok stdole.dll I can accept, even Microsoft.MSXML.dll, but why the VS Interop stuff?
Heheh yeah... VS is a very powerfull tool
Heheh yeah... VS is a very powerfull tool
For runtime support, installing System.Web.Extensions to the gac is sufficient to add the AJAX support. You will also need the web.config entries that add the tag mapping, compilation, handlers and modules.
Much appreciated, Matt. I hope someone adds that tiny clarification to the documentation.
0 件のコメント:
コメントを投稿