config section <runtime>

[=?Utf-8?B?TUNN?=]

What does this do?

<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>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design"
publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0"
newVersion="3.5.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>

[Family Tree Mike]

I'm guessing the several questions you are asking might be better answered
in the ASP.Net group. It seems a little odd though that you are asking what
certains sections in a site do, or how to change things in code that you
see. Did you inherit some code that now you must maintain without ASP.Net
before?
"MCM" <MC*@newsgroup.nospamwrote in message
news:D2**********************************@microsof t.com...

What does this do?

<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>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design"
publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0"
newVersion="3.5.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>

[=?Utf-8?B?TUNN?=]

I'm guessing the several questions you are asking might be better answered

in the ASP.Net group.

This is a managed newsgroup and is definitely where my questions belong.

It seems a little odd though that you are asking what
certains sections in a site do, or how to change things in code that you
see. Did you inherit some code that now you must maintain without ASP.Net
before?

Most of the code sections I am asking about are auto-generated by Visual
Studio. Sometimes the auto code in VS adds things for the "average" case that
do not apply to all solutions. Just cause VS created it does not mean it
belongs. I'm trying to squeeze the maximum performance out of my site.

>

"MCM" <MC*@newsgroup.nospamwrote in message
news:D2**********************************@microsof t.com...

What does this do?

<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>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design"
publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0"
newVersion="3.5.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>

[Family Tree Mike]

I don't believe the group is managed.

I'm just suggesting more web developers hang out in the ASP.Net newsgroup,
rather than .Net.General.

"MCM" <MC*@newsgroup.nospamwrote in message
news:61**********************************@microsof t.com...

>I'm guessing the several questions you are asking might be better
answered
in the ASP.Net group.

This is a managed newsgroup and is definitely where my questions belong.

>>

[Feng Chen[MSFT]]

Hello MCM,

Although the XML is redirecting the web development related assemblies, the
question is not Asp.net specific. So dotnet.general can be suitable
newsgroup here.

In short, these XML elements redirect assembly versions using
bindingRedirection element
(http://msdn.microsoft.com/en-us/library/eftw1fys.aspx).

In this config file, they redirect the version of assembly
System.Web.Extensions and System.Web.Extensions.Design from
"1.0.0.0-1.1.0.0" to "3.5.0.0". That means if the application tries to use
the old version of the assembly specified by the "oldVersion" attribute,
CLR will load the new version of it specified by "newVersion" attribute.

For more information about this feature, please visit the following article:
Introduction to Versioning and
BindingRedirect(http://blogs.msdn.com/thottams/archi.../30/introducti
on-to-versioning-and-bindingredirect.aspx).

Hope this helps.

Best regards,
Feng Chen
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications .

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx .
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[=?Utf-8?B?TUNN?=]

Does that mean if I am not using the old version in my code, I can delete the
entire <runtimesection?
""Feng Chen[MSFT]"" wrote:

Hello MCM,

Although the XML is redirecting the web development related assemblies, the
question is not Asp.net specific. So dotnet.general can be suitable
newsgroup here.

In short, these XML elements redirect assembly versions using
bindingRedirection element
(http://msdn.microsoft.com/en-us/library/eftw1fys.aspx).

In this config file, they redirect the version of assembly
System.Web.Extensions and System.Web.Extensions.Design from
"1.0.0.0-1.1.0.0" to "3.5.0.0". That means if the application tries to use
the old version of the assembly specified by the "oldVersion" attribute,
CLR will load the new version of it specified by "newVersion" attribute.

For more information about this feature, please visit the following article:
Introduction to Versioning and
BindingRedirect(http://blogs.msdn.com/thottams/archi.../30/introducti
on-to-versioning-and-bindingredirect.aspx).

Hope this helps.

Best regards,
Feng Chen
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications .

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx .
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Feng Chen[MSFT]]

Hello MCM,

We can remove the <assemblyBindingelement and all of its child elements
if our application does not need assembly version redirection or assembly
relocation. In addition, if the <runtimeelement does not contain any
other kind of child elements (A list of its child elements can be found
here: http://msdn.microsoft.com/en-us/library/6bs4szyc.aspx), we can remove
it safely.

Could you also let me know if the xml comes from the machine.config or the
web.config file? What's the reason you want to remove them?

Please let me know the information above so that I can provide further
assistance on this problem. I look forward to your reply.

Thanks.

Best regards,
Feng Chen
Microsoft Online Community Support
=========================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.

[=?Utf-8?B?TUNN?=]

We can remove the <assemblyBindingelement and all of its child elements

if our application does not need assembly version redirection or assembly
relocation.

How can I confirm that my application is not trying to use the old version?

In addition, if the <runtimeelement does not contain any
other kind of child elements (A list of its child elements can be found
here: http://msdn.microsoft.com/en-us/library/6bs4szyc.aspx), we can remove
it safely.

Ok.

Could you also let me know if the xml comes from the machine.config or the
web.config file? What's the reason you want to remove them?

web.config. These entries were made automatically by Visual Studio - not by
me. I'm trying to understand every layer of my application and I don't
understand why I would want to include code that doesn't do anything.

[Feng Chen[MSFT]]

Hello MCM,

The two assemblies are from AJAX Control Toolkit. And versions 1.0.* of
them are for ASP.NET AJAX version 1.0 and .NET Framework 2.0, while 3.5.*
of them are for .NET Framework 3.5 and Visual Studio 2008. So this section
will make sure that the web application compiled using .net 3.5 will always
load the 3.5 version of the assemblies.

If the web project and any custom control used by the project have not
added the old version of the assemblies as reference, we can confirm the
application will not try to use the old version.

Hope this helps.

Best regards,
Feng Chen
Microsoft Online Community Support
=========================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.

[Feng Chen[MSFT]]

Hello MCM,

I haven¡¯t heard back from you so I wanted to follow up to find out if the
information that I supplied has resolved your issue. If there is anything
more I can help with, please don¡¯t hesitate to let me know.

Thanks.

Best regards,
Feng Chen
Microsoft Online Community Support
=========================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.

[=?Utf-8?B?TUNN?=]

Yes, it was helpful. That's why I marked the question as answered. Thank you.

""Feng Chen[MSFT]"" wrote:

Hello MCM,

I haven¡¯t heard back from you so I wanted to follow up to find out if the
information that I supplied has resolved your issue. If there is anything
more I can help with, please don¡¯t hesitate to let me know.

Thanks.

Best regards,
Feng Chen
Microsoft Online Community Support
=========================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.