So, it's putting the old version in your manifest, and you want the NEW
version? Ah... I thought it was the opposite.
Which version are you referencing in your project? Do you have it set to
"specific version"?
BOb
________________________________
From: Eric Fetzer [mailto:[EMAIL PROTECTED]
Sent: Friday, February 29, 2008 3:03 PM
To: Bob Archer; Chris Snider; Gert Driesen; Nant Users
Subject: Re: [NAnt-users] 3.5 Framework Solution Build using 2.0
Actually, no, we didn't use the beta (this is 2 days ago). And the fix
didn't help, we tried it first. We had to add the following to all of
the web.config files used in apps built on the server containing 3.5 of
the framework that use 1.0 ajax extensions:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions"
publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0"
newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
That was the only thing that worked for us. So we ended up separating
the 3.5 build machine and builds.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
