Implications of Conflicting versions of System.Web.Extensions
<p>One of the libraries I am including in my project makes use of System.Web.Extensions 3.5.0.0, which conflicts with my Framework 2.0 application, which uses (<code>C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025\System.Web.Extensions.dll</code>).  I can think of 3 possible solutions:</p>

<ol>
<li>Ignore the warning and don't change anything.  I am not sure what the application does to handle this.</li>
<li>Add an assembly binding element to my web.config (see below)</li>
<li>Configure the application explicitly to use different assemblies (I think this is possible, but don't know how to do it).</li>
</ol>

<p>However, I am unsure of the implications of each of these decisions.  The application seems to work perfectly fine even when I ignore the warnings (solution 1), but ignoring warnings that I don't fully understand bugs me...as does having warnings like this show up at all.</p>

<pre><code>&lt;runtime&gt;
    &lt;assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"&gt;
        &lt;dependentAssembly&gt;
            &lt;assemblyIdentity name="System.Web.Extensions" publicKeyToken="31BF3856AD364E35" culture="neutral"/&gt;
            &lt;bindingRedirect oldVersion="0.0.0.0-3.5.0.0" newVersion="3.5.0.0"/&gt;
        &lt;/dependentAssembly&gt;
    &lt;/assemblyBinding&gt;
&lt;/runtime&gt;
</code></pre>

<p>Edit: I don't think #3 will work, since I'm referencing thinks like the AjaxControlToolKit, which has its own references to <code>System.Web.Extensions</code>.</p>
