Error Writing To File System.web.extensions.design.dll
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Windows installer failing with error “Error writing to file: System.Web.Extensions.dll. Verify that you have access to that directory.” up vote 0 down vote favorite I have a simple windows installer package that I created. All it does is install 2 .dll's into the GAC. This is a production machine, so as I understand it, it is a best practice to install to the GAC in this way (as opposed to using gacutil.exe, etc.) This installer works fine on another server that I have for testing. The server it works on, however, is just a plain vanilla installation of Win2k3, with nothing else installed. The production server this installer is failing on is a Win2k3 box with service packs, and a load of other software on it. I am not sure how to go about troubleshooting this. There are no events thrown in the even logs, etc. No indication of what is wrong. This question on MSDN has some hints, but I can't seem to find any real answers. windows-installer gac share|improve this question asked Apr 13 '11 at 20:18 richard 3,92385097 Come on folks, don't let this one become a tumbleweed!!! –richard Apr 13 '11 at 21:09 Can you post a link to the full installation log so we can take a look? –mrnx Apr 14 '11 at 9:11 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote Here's my guess without looking at any logfile: 1) You shouldn't even be installing this assembly as it's part of .NET 3.5. You also probably didn't tell your installer to install it. It's just one of those wonderful feature that makes Visual Studio Deployment projects, well, "special" It likes to detect dependencies and then it's up to you to "exclude" them ( right click | exclude ) 2) The machine that it's
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just http://stackoverflow.com/questions/5655082/windows-installer-failing-with-error-error-writing-to-file-system-web-extensio like you, helping each other. Join them; it only takes a minute: Sign up problem with System.Web.Extension after installing .net 3.5 sp1 up vote 2 down vote favorite I have a solution that includes several class library's and a website. The solution was built in .net 2.0 Visual Studio 2005, and later converted to .net 3.5 (all http://stackoverflow.com/questions/1770678/problem-with-system-web-extension-after-installing-net-3-5-sp1 class library's and website are targeting 3.5 framework). Before installing the update, the website functioned perfectly. After, a build fails on using System.Web.Extensions; the error message is: "The type of namespace Extensions does not exist in the namespace System.Web (are you missing an assembly reference?)". I looked in the .net 2.0 framework folder and the System.Web.Extensions .dll was indeed gone. However the C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5 folder had the .dll. the GAC shows two System.Web.Extensions, the old 1.06 version and the new 3.5 version. I have the web.config rebinding to the new version. I checked my references, deleted the old one and added a reference to the .3.5 version of System.Web.Extensions. It didn't work, the build failed at the same place. I then copied the .dll to the bin of my website, and pointed the reference there. that also did not work, the solution did not build, and when I looked at the references, it appeared to not have a reference to the file in the bin folder.
not load file or assembly ‘System.Web.Extensions…'". The Reason for the Error The application uses Microsoft ASP.NET 2.0 AJAX Extensions 1.0, but they had not been installed on the production machine. The Obvious Solution The obvious solution was to download the ‘ASPAJAXExtSetup.msi‘ installer from https://allwrong.wordpress.com/2007/07/17/aspnet-error-could-not-load-file-or-assembly-systemwebextensions/ Microsoft and run it on the live server. The required .dll files would then be https://blogs.msdn.microsoft.com/webdev/2007/07/29/using-vs-2008-to-target-asp-net-ajax-1-0/ inserted into the GAC. The Hitch The production machine is a Windows 2000 server. In order to access these files, the IIS instance on the server would need to be restarted. Unfortunately, this was not an option. The target server hosts various applications that cannot be brought down without disrupting the users. The Final Solution The development machine did not error writing exhibit the problem, so this machine obviously had the dll files present. The simple answer is to place a copy of these files in the application's ‘bin' folder on the production server. When I did this, the error message went away immediately. So, what files did I need, and where did I find them? Well, since the installer copies the dlls into the GAC, they can obviously be found there. For reference, the GAC on error writing to my machine is at: C:\WINNT\Assembly Unfortunately, you can't see the individual files using Windows Explorer. However, the files can be viewed using the command prompt. It is a bit of a messy process, but it is possible to use the Command Prompt to extract the files. The good news is that there is an easier way. A colleague pointed out that the installer also places another copy of these files outside the GAC. From this location, they can simply be copied and pasted into the bin folder of the target application. On my machine the required files are here: C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025\ The files I needed were: System.Web.Extensions.Design.dll System.Web.Extensions.dll Many thanks to GK for pointing this out to me. Like this:Like Loading... Related This entry was posted on Tuesday, July 17th, 2007 at 3:08 pm and is filed under ASP.Net, Computing, Programming. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site. Post navigation « Previous Post Next Post » 52 Responses to ASP.Net Error: Could not load file or assembly ‘System.Web.Extensions…' abdulrehman says: October 24, 2007 at 9:50 am please send me this dll i really need it Reply kramii says: October 24, 2007 at 8:04 pm abdulrehman: I am pleased that y
& Install by Heath Stewart Application Lifecycle Management Application Insights Release Management Team Foundation Server Testing Visual Studio Team Services All Languages Visual C++ Visual F# JavaScript TypeScript Python .NET .NET .NET with Beth Massi ASP.NET by Scott Hanselman OData Team WPF Platform Development Apps for Windows Bing Edge Microsoft Azure Office 365 Development Web Data Development SQL Server SQL Server Data Tools DocumentDB .NET Web Development and Tools Blog Your official information source from the .NET Web Development and Tools group at Microsoft. Using VS 2008 to target ASP.NET AJAX 1.0 ★★★★★★★★★★★★★★★ July 29, 2007 by Web Development Tools Microsoft // 60 Comments 0 0 0 8/10/2007 UPDATE: This blog post was edited to include simplified instructions to work around a known issue w/ Multitargeting support in VS 2008 Beta 2. See “Machine Prerequisites” below. In a previous post, I described the steps you can take to upgrade your existing ASP.NET AJAX 1.0-based Web sites to use the new AJAX functionality in .NET Framework 3.5. However, you may also need to maintain existing AJAX 1.0-based sites without upgrading them, or even continue creating new AJAX 1.0-based sites. Fortunately, the Multitargeting support in Visual Studio 2008 allows you do just that. Using Visual Studio 2008, you can still write and maintain applications using .NET Framework 2.0 (and AJAX 1.0), while also reaping the benefits of all the new features in VS 2008 such as the new WYSIWYG design surface, CSS management features, Jscript Intellisense, and Jscript debugging. In this post, we’ll look at the steps you can follow to either maintain an existing ASP.NET AJAX 1.0 application in VS 2008, or create a new ASP.NET AJAX 1.0-based application in VS 2008. If you decide to move forward to the AJAX functionality in .NET Framework 3.5 at a later time, you can simply follow these steps to upgrade. Machine Prerequisites: 1. Download and install Microsoft Visual Studio 2008 Beta 2 2. After the Beta 2 installation has finished, you should run this script to ensure that the installation of .NET Framework 3.5 Beta 2 will not affect the development of ASP.NET AJAX 1.0 applications. You should do this immedi