Adding reference to system.web.dll hanging in Visual studio 2005

Rate It (1)

Last post 02-18-2009 5:55 PM by christo_c. 12 replies.

Sort Posts:

  • Adding reference to system.web.dll hanging in Visual studio 2005

    01-17-2007, 4:50 AM
    • Member
      688 point Member
    • ajw
    • Member since 08-29-2006, 4:16 PM
    • UK
    • Posts 533

    I have just moved to a new machine and moved from visual web developer to visual studio 2005.  when I try and open any of my websites Visual studio hangs on 'adding system.web.dll' message when I try to system to design mode..   There are a few other errors in the build. 

     

    Cheers.

    Andrew

  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    01-18-2007, 12:21 AM
    • Participant
      911 point Participant
    • Nick Asiimwe
    • Member since 09-18-2006, 8:10 AM
    • Uganda
    • Posts 515

    check out arelated thread at this link

    http://forums.asp.net/thread/1522429.aspx

    --------------------------------------------------
    Sincerely,
    Nickson Asiimwe.

    Technologies
    ASP.NET, SQL Server [Development, SSIS & SSRS], C# and VB.NET
  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    01-18-2007, 5:26 AM
    • Member
      688 point Member
    • ajw
    • Member since 08-29-2006, 4:16 PM
    • UK
    • Posts 533

     I tried the stuff in that other post to no avail. Its not a problem with the intellisense and shouldnt be a problem with AJAX because thats installed on the remote server.

     Any other ideas?

  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    01-18-2007, 5:53 AM
    • Member
      688 point Member
    • ajw
    • Member since 08-29-2006, 4:16 PM
    • UK
    • Posts 533

    Let me try and be a bit clearer with my setup. 

    I was running VWD 2005 with the latest AJAX RC installation.

    A couple of the websites I am working on are on a remote server but this does have AJAX installed on it.

    I have a new development machine.  This has Visual Studio 2005 installed.  I have not yet installed AJAX on it but I am going to try this.. 

    It often comes up with the error of not being able to find reference to microsoft.web.extensions.dll.  Even though this is located in the bin folder.

    Anyway, I hope someone can help me.

    Thanks

    Andrew

  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    01-19-2007, 11:34 PM
    Answer

    You must remove old Ajax from bin. RC is installed in GAC and what you are seeing is a conflict between two different versions. Please read RC installation notes carefully:

    http://ajax.asp.net/docs/InstallingASPNETAJAX.aspx 

    http://ajax.asp.net/docs/ConfiguringASPNETAJAX.aspx 

    Thanks

    ------------------------------------------------------------

    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    01-22-2007, 8:19 AM
    • Member
      688 point Member
    • ajw
    • Member since 08-29-2006, 4:16 PM
    • UK
    • Posts 533

    I remove those dlls from the bin .  the ajaxcontroltoolkit one and the Microsoft.Web.Extensions.Design.dll.  This doesnt stop it from hanging on trying to add reference to system.web.dll.  I guess I need to remove the reference to the dlls from the web.config file??

     Thanks for being patient

    Andrew

  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    01-22-2007, 9:53 AM
    • Member
      688 point Member
    • ajw
    • Member since 08-29-2006, 4:16 PM
    • UK
    • Posts 533

    It might be easier if i post the web.config.

     <?xml version="1.0"?>
    <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
     <configSections>
      <sectionGroup name="microsoft.web" type="Microsoft.Web.Configuration.MicrosoftWebSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
       <sectionGroup name="scripting" type="Microsoft.Web.Configuration.ScriptingSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
        <sectionGroup name="webServices" type="Microsoft.Web.Configuration.ScriptingWebServicesSectionGroup, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
         <section name="jsonSerialization" type="Microsoft.Web.Configuration.ScriptingJsonSerializationSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
         <section name="profileService" type="Microsoft.Web.Configuration.ScriptingProfileServiceSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
         <section name="authenticationService" type="Microsoft.Web.Configuration.ScriptingAuthenticationServiceSection, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>
        </sectionGroup>
       </sectionGroup>
      </sectionGroup>
     </configSections>
     <connectionStrings>
     </connectionStrings>
     <system.web>
      <roleManager enabled="true" defaultProvider="CustomizedRoleProvider">
       <providers>
        <add name="CustomizedRoleProvider" type="System.Web.Security.SqlRoleProvider" applicationName="/" connectionStringName="ASPNETDBConnectionString"/>
       </providers>
      </roleManager>
      <pages>
       <controls>
        <add tagPrefix="asp" namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        <add tagPrefix="asp" namespace="Microsoft.Web.UI.Controls" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
       </controls>
       <tagMapping>
        <add tagType="System.Web.UI.WebControls.CompareValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CompareValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        <add tagType="System.Web.UI.WebControls.CustomValidator" mappedTagType="Microsoft.Web.UI.Compatibility.CustomValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        <add tagType="System.Web.UI.WebControls.RangeValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RangeValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        <add tagType="System.Web.UI.WebControls.RegularExpressionValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RegularExpressionValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        <add tagType="System.Web.UI.WebControls.RequiredFieldValidator" mappedTagType="Microsoft.Web.UI.Compatibility.RequiredFieldValidator, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        <add tagType="System.Web.UI.WebControls.ValidationSummary" mappedTagType="Microsoft.Web.UI.Compatibility.ValidationSummary, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
       </tagMapping>
       <namespaces>
        <clear/>
        <add namespace="System"/>
        <add namespace="System.Collections"/>
        <add namespace="System.Collections.Specialized"/>
        <add namespace="System.Configuration"/>
        <add namespace="System.Text"/>
        <add namespace="System.Text.RegularExpressions"/>
        <add namespace="System.Web"/>
        <add namespace="System.Web.Caching"/>
        <add namespace="System.Web.SessionState"/>
        <add namespace="System.Web.Security"/>
        <add namespace="System.Web.Profile"/>
        <add namespace="System.Web.UI"/>
        <add namespace="System.Web.UI.WebControls"/>
        <add namespace="System.Web.UI.WebControls.WebParts"/>
        <add namespace="System.Web.UI.HtmlControls"/>
       </namespaces>
      </pages>
      <!--
                Set compilation debug="true" to insert debugging
                symbols into the compiled page. Because this
                affects performance, set this value to true only
                during development.
            -->
      <compilation debug="true">
       <assemblies>
        <add assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Web.RegularExpressions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>
      </compilation>
      <httpHandlers>
       <remove verb="*" path="*.asmx"/>
       <add verb="*" path="*.asmx" validate="false" type="Microsoft.Web.Script.Services.ScriptHandlerFactory, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
       <add verb="GET" path="ScriptResource.axd" type="Microsoft.Web.Handlers.ScriptResourceHandler" validate="false"/>
      </httpHandlers>
      <httpModules>
       <add name="WebResourceCompression" type="Microsoft.Web.Handlers.WebResourceCompressionModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
       <add name="ScriptModule" type="Microsoft.Web.UI.ScriptModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
      </httpModules>
      <!--
                The <authentication> section enables configuration
                of the security authentication mode used by
                ASP.NET to identify an incoming user.
            -->
      <anonymousIdentification enabled="False"/>
      <!-- You should ALWAYS customize the Membership provider and specify an applicationName... see http://weblogs.asp.net/scottgu/archive/2006/04/22/Always-set-the-_2200_applicationName_2200_-property-when-configuring-ASP.NET-2.0-Membership-and-other-Providers.aspx for more details... -->
      <membership defaultProvider="CustomizedProvider">
       <providers>
        <add name="CustomizedProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="ASPNETDBConnectionString" applicationName="/" minRequiredPasswordLength="5" minRequiredNonalphanumericCharacters="0" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="true" passwordFormat="Clear"/>
        <add name="SqlProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="ASPNETDBConnectionString" applicationName="/" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="false" passwordFormat="Clear"/>
       </providers>
      </membership>
      <!-- You should ALWAYS customize the Profile provider and specify an applicationName... see http://weblogs.asp.net/scottgu/archive/2006/04/22/Always-set-the-_2200_applicationName_2200_-property-when-configuring-ASP.NET-2.0-Membership-and-other-Providers.aspx for more details... -->
      <profile defaultProvider="CustomProfileProvider" enabled="true">
       <providers>
        <add name="CustomProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ASPNETDBConnectionString" applicationName="/"/>
       </providers>
       <properties>
        <add name="CompanyName" type="string" serializeAs="String" defaultValue="" allowAnonymous="false"/>
        <add name="Website" type="string" serializeAs="String" defaultValue="" allowAnonymous="false"/>
        <add name="Address" type="string" serializeAs="String" defaultValue="" allowAnonymous="false"/>
        <add name="Postcode" type="string" serializeAs="String" defaultValue="" allowAnonymous="false"/>
        <add name="Telephone" type="string" serializeAs="String" defaultValue="" allowAnonymous="false"/>
        <add name="Fullname" type="string" serializeAs="String" defaultValue="" allowAnonymous="false"/>
        <add name="Email" type="string" serializeAs="String" defaultValue="" allowAnonymous="false"/>
       </properties>
      </profile>
      <!--
                The <authentication> section enables configuration
                of the security authentication mode used by
                ASP.NET to identify an incoming user.
            -->
      <authentication mode="Forms"/>
      <!--
                The <customErrors> section enables configuration
                of what to do if/when an unhandled error occurs
                during the execution of a request. Specifically,
                it enables developers to configure html error pages
                to be displayed in place of a error stack trace.

            <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
                <error statusCode="403" redirect="NoAccess.htm" />
                <error statusCode="404" redirect="FileNotFound.htm" />
            </customErrors>
            -->
     </system.web>
     <system.webServer>
      <validation validateIntegratedModeConfiguration="false"/>
      <modules>
       <add name="ScriptModule" preCondition="integratedMode" type="Microsoft.Web.UI.ScriptModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
      </modules>
      <handlers>
       <remove name="WebServiceHandlerFactory-ISAPI-2.0"/>
       <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="Microsoft.Web.Script.Services.ScriptHandlerFactory, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
       <add name="ScriptResource" verb="GET" path="ScriptResource.axd" type="Microsoft.Web.Handlers.ScriptResourceHandler"/>
      </handlers>
     </system.webServer>
    </configuration>

  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    01-24-2007, 11:37 AM
    • Member
      2 point Member
    • PabloFlag
    • Member since 10-02-2006, 4:32 PM
    • Posts 1

    I began encountering this same problem after attempting to install Microsoft's AJAX software a week or so ago (Mikhail would be very disappointed -- I did NOT read the instructions carefully prior to installing -- to my detriment).  After that, upon clicking into Design View, or upon attempting to change anything while in design view, Visual Studio 2005 would hang for several minutes before moving.  I uninstalled the three AJAX components, still to no avail.

    Here's what finally fixed it for me: I went back to the Add/Remove Programs control panel, then chose Change/Remove for the Microsoft .NET Framework 2.0.  One of the options is to Repair Microsoft .NET Framework 2.0 to its original state.  I chose this option, and after a system restart, Visual Studio is back to normal.

    Hope this helps.

    -Paul
     

  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    01-25-2007, 4:14 AM
    Answer
    • Member
      688 point Member
    • ajw
    • Member since 08-29-2006, 4:16 PM
    • UK
    • Posts 533

    I have now solved this problem with the help of Mikhail.  

     I installed the latest version of AJAX RC1.  I removed the microsoft.web.extensions.design.dll from the bin folder.  I replaced all the references to the microsoft.web.extensions with the new system.web.extensions references using the microsoft, installation of AJAX help.  Then I rebuilt the website. That sorted it.

  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    01-22-2008, 1:44 PM
    • Member
      4 point Member
    • jand
    • Member since 01-22-2008, 6:41 PM
    • Posts 2

    So you are telling me that I HAVE to install AJAX ? Because I'm getting this error, and I do not have AJAX installed. I do not have web.extensions in my web.config file. I have repaired the 2.0 Framework. But so far, no matter what I do, I continue to get the "Adding reference to 'System.Web.dll'... message in the status bar. Any other advice?

  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    08-04-2008, 4:41 PM
    • Member
      13 point Member
    • programthat
    • Member since 03-28-2007, 8:37 PM
    • Menomonie, WI
    • Posts 27

     

    I am having serious issues with this bug.  I have been down all day tring to resolve this issue.  The "Adding reference to system.web.dll" message only appears when I open 1 specific project.  I can create a new project and things are dandy.  I have removed the references to the AJAX toolkit, system.web and system.web.extensions.  Can you tell me exactly what I need to do here?  I read the pages you link to regarding a correct install and followed the instructions with no luck.  Help!!
    Programthat

    Please click "Mark as Answer" for posts that were helpful to you.
  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    09-09-2008, 4:30 AM
    • Member
      22 point Member
    • christo_c
    • Member since 11-10-2006, 2:10 AM
    • South Africa
    • Posts 8

    I had the same problem but the solution had nothing to to with AJAX.  I had references to assemblies of packages that I haven't installed yet.  Once I removed them from the web.config, all was fine.

  • Re: Adding reference to system.web.dll hanging in Visual studio 2005

    02-18-2009, 5:55 PM
    • Member
      22 point Member
    • christo_c
    • Member since 11-10-2006, 2:10 AM
    • South Africa
    • Posts 8
    sorry, dbl post.
Page 1 of 1 (13 items)