.net – problem with System.Web.Extension after installing .net 3.5 sp1

net

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 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.

Note: The system has .net 1.1 installed, Visual studio 2003, and 2005.

can anyone point me to what I can do to fix this?
I know uninstalling the 3.5 sp1 update will fix it, but I'd rather keep it.

Thank you
Deb

Best Answer

Did you check the added assemblies in the web.config? Is System.Web.Extensions 3.5 added?

<compilation debug="true">
    <assemblies>
        <add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
    </assemblies>
</compilation>

Related Solutions

.net – Delivery of .Net 3.5 SP1

The .Net Framework 3.5 SP1 redistributable (the one that's around 230MB) contains everything (2.0 + SP1 + SP2, 3.0 + SP1 + SP2, 3.5 + SP1) in all supported architectures (x86, x64, ia64). This is the only download you need.

Download from here (click on .NET Framework 3.5 Service Pack 1 (Full Package)):

And then, you might want to install these updates:

IMPORTANT: After installing the .NET Framework 3.5 SP1 package (either the bootstrapper or the full package) you should immediately install the update KB959209 to address a set of known application compatibility issues.

There are 3 updates (for 2.0, 3.0, and 3.5) for 2 OS "groups" (XP/2003 or Vista/2008) for 3 architectures (x86, x64, or ia64), for a total of... 16 downloads! (I know, 3 * 2 * 3 = 18, but Server 2003 ia64 only supports up to 2.0). You need to install the 3 updates in order. Or you could run Windows Update after installing 3.5 SP1 and let it figure it out.

EDIT: To be clear, .Net 3.5 requires that 2.0 and 3.0 be installed and updated to SP1 level. .Net 3.5 SP1 requires that 2.0/3.0 be updated to SP2 level. But the 3.5(SP1) installers will do this automatically. That is, by installing 3.5 SP1, you don't need to worry about installing and updating 2.0 and 3.0 to SP1 or SP2. Just install 3.5 SP1 and you're done! (and the extra updates, 3.5 SP1.1?)

About the Client Profile, it can only be installed on x86 client machines that don't have ANY version of .Net installed, so it won't install on Vista (it already comes with .Net 3.0), any Windows Server version, nor any x64/ia64 OS. You can only install it on a Windows XP SP2+ (x86) that doesn't have any version of .Net installed, otherwise a full installation is done. The offline Client Profile installer is 255MB because it will try to do a client install first, if it can't it will fallback to a full install. Personally, I would just do a full install anyway.

.net – Dependency graph of Visual Studio projects

I needed something similar, but didn't want to pay for (or install) a tool to do it. I created a quick PowerShell script that goes through the project references and spits them out in a yuml.me friendly-format instead:

Function Get-ProjectReferences ($rootFolder)
{
    $projectFiles = Get-ChildItem $rootFolder -Filter *.csproj -Recurse
    $ns = @{ defaultNamespace = "http://schemas.microsoft.com/developer/msbuild/2003" }

    $projectFiles | ForEach-Object {
        $projectFile = $_ | Select-Object -ExpandProperty FullName
        $projectName = $_ | Select-Object -ExpandProperty BaseName
        $projectXml = [xml](Get-Content $projectFile)

        $projectReferences = $projectXml | Select-Xml '//defaultNamespace:ProjectReference/defaultNamespace:Name' -Namespace $ns | Select-Object -ExpandProperty Node | Select-Object -ExpandProperty "#text"

        $projectReferences | ForEach-Object {
            "[" + $projectName + "] -> [" + $_ + "]"
        }
    }
}

Get-ProjectReferences "C:\Users\DanTup\Documents\MyProject" | Out-File "C:\Users\DanTup\Documents\MyProject\References.txt"

Related Topic