web.config required elements

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

The following sections appears in my web.config file.

<configuration>
<system.web>
<compilation>

<assemblies>
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35" />
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Web.Extensions.Design, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
<add assembly="System.Design, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
</assemblies>
What does each of these assemblies do and how do I know if I need them or if
I can delete them?

I am working on a .NET 3.5 web application which uses AJAX. It will be
hosted on Server 2008 w/ IIS 7.

[Steven Cheng [MSFT]]

Hi MCM,

As for the configuration elements you mentioned, they're those strong-named
assemblies which are referenced globally in your ASP.NET web
application(every page in the web application will be referencing them).

And here is a brief summary of these assemblies:

><assemblies>
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=B77A5C561934E089" />

<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />

=====================================

These ones are the core assemblies for the .NET 3.5 components and
services(such as LINQ)

<add assembly="System.Web.Extensions, Version=3.5.0.0,

Culture=neutral,

>PublicKeyToken=31BF3856AD364E35" />

<add assembly="System.Web.Extensions.Design, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35" />

=============================

These two ones are for ASP.NET ajax service (contains many extension
classes components which is necessary to make ASP.NET ajax work)

<add assembly="System.Design, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
</assemblies>

======================================
I'm a bit surprised that your application references the "winform"
assembly, are you using some winform class in your ASP.NET application?

Here is a blog entry which also give some general ideas on many new
asssmblies involved in ..NET 3.5

http://www.danielmoth.com/Blog/2007/...mework-35.html

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
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/en-us/subs...#notifications.

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://support.microsoft.com/select/...tance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

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

>From: =?Utf-8?B?TUNN?= <MC*@newsgroup.nospam>
Subject: web.config required elements
Date: Wed, 20 Aug 2008 12:46:42 -0700

>The following sections appears in my web.config file.

<configuration>
<system.web>
<compilation>

<assemblies>
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Web.Extensions, Version=3.5.0.0,

Culture=neutral,

>PublicKeyToken=31BF3856AD364E35" />
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Web.Extensions.Design, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
<add assembly="System.Design, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
</assemblies>
What does each of these assemblies do and how do I know if I need them or

if

>I can delete them?

I am working on a .NET 3.5 web application which uses AJAX. It will be
hosted on Server 2008 w/ IIS 7.

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

As for the configuration elements you mentioned, they're those strong-named

assemblies which are referenced globally in your ASP.NET web
application(every page in the web application will be referencing them).

First - I tried deleting all of them and my application seemed to run just
fine. So I'm not clear on why I need them? Are they just need for web "sites"
but not web "applications"?

Second - if I do need them, should I keep them matched up with the project
references? What happens if there is a mismatch between the project
references and the wbe.config? Why are these listed in 2 places anyway?

<add assembly="System.Core, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />

=====================================

These ones are the core assemblies for the .NET 3.5 components and
services(such as LINQ)

If I am not using LINQ, then I don't need the assembly right?

<add assembly="System.Web.Extensions, Version=3.5.0.0,

Culture=neutral,

PublicKeyToken=31BF3856AD364E35" />
<add assembly="System.Web.Extensions.Design, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35" />

=============================

These two ones are for ASP.NET ajax service (contains many extension
classes components which is necessary to make ASP.NET ajax work)

System.Web.Extensions.Design is part of System.Web.Extensions, so why would
I need both? Can't I just reference System.Web.Extensions?

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

An additional note:

If I delete the assembly System.Xml.Linq, my app still compiles fine and
runs fine, but I get a green underline below @Page directive that says it
can't find System.Xml.Linq. Even though I am not using Linq at all, it is
still looking for it. So it must be getting used somewhere by the
compiler/framework/iis/something? Can you tell me what it is being used for
and what the other assemblies are used for *specifically*?
"MCM" wrote:

As for the configuration elements you mentioned, they're those strong-named
assemblies which are referenced globally in your ASP.NET web
application(every page in the web application will be referencing them).

First - I tried deleting all of them and my application seemed to run just
fine. So I'm not clear on why I need them? Are they just need for web "sites"
but not web "applications"?

Second - if I do need them, should I keep them matched up with the project
references? What happens if there is a mismatch between the project
references and the wbe.config? Why are these listed in 2 places anyway?

<add assembly="System.Core, Version=3.5.0.0, Culture=neutral,
>PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0,
>Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral,
>PublicKeyToken=B77A5C561934E089" />

=====================================

These ones are the core assemblies for the .NET 3.5 components and
services(such as LINQ)

If I am not using LINQ, then I don't need the assembly right?

<add assembly="System.Web.Extensions, Version=3.5.0.0,

Culture=neutral,

>PublicKeyToken=31BF3856AD364E35" />
<add assembly="System.Web.Extensions.Design, Version=3.5.0.0,
>Culture=neutral, PublicKeyToken=31BF3856AD364E35" />

=============================

These two ones are for ASP.NET ajax service (contains many extension
classes components which is necessary to make ASP.NET ajax work)

System.Web.Extensions.Design is part of System.Web.Extensions, so why would
I need both? Can't I just reference System.Web.Extensions?

[Steven Cheng [MSFT]]

Thanks for your reply MCM,

If you haven't used any LINQ feature, you can certainly remove the
reference. As for the green line warning, I think it is likely a
design-time error producted by IDE, I cannot get the exact cause from the
general appearnce.

If you want to get the usage of each of those assemblies, I recommend you
use the reflector utility to inspect those assemblies and you can clearly
get all the available classes in the assembly.

Also, one means for checking whether your application can work
correctly(with the current assembly reference list) is perform a
"precompilation" on your web application(project). In visual studio, you
can use "Build --Publish Web Site" to do precompilation"

precompilation just predo the dynamic compilation before you publish/deploy
the web application:

#Precompilation In ASP.NET 2.0
http://www.odetocode.com/Articles/417.aspx

it will report error if there is any assembly reference problem(you should
choose "nonupdatable" mode when precompile the site).

BTW, I've also replied you in another thread mentioned some information
about different project type of ASP.NET 2.0 application which is also
helpful to you.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
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/en-us/subs...#notifications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

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

>From: =?Utf-8?B?TUNN?= <MC*@newsgroup.nospam>
References: <6A**********************************@microsoft.co m>

<TN**************@TK2MSFTNGHUB02.phx.gbl>
<3D**********************************@microsoft.co m>

>Subject: RE: web.config required elements
Date: Thu, 21 Aug 2008 15:02:05 -0700

>
An additional note:

If I delete the assembly System.Xml.Linq, my app still compiles fine and
runs fine, but I get a green underline below @Page directive that says it
can't find System.Xml.Linq. Even though I am not using Linq at all, it is
still looking for it. So it must be getting used somewhere by the
compiler/framework/iis/something? Can you tell me what it is being used

for

>and what the other assemblies are used for *specifically*?
"MCM" wrote:

As for the configuration elements you mentioned, they're those

strong-named

assemblies which are referenced globally in your ASP.NET web
application(every page in the web application will be referencing

them).

>>
First - I tried deleting all of them and my application seemed to run

just

>fine. So I'm not clear on why I need them? Are they just need for web

"sites"

>but not web "applications"?

Second - if I do need them, should I keep them matched up with the

project

>references? What happens if there is a mismatch between the project
references and the wbe.config? Why are these listed in 2 places anyway?

<add assembly="System.Core, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
=====================================

These ones are the core assemblies for the .NET 3.5 components and
services(such as LINQ)

If I am not using LINQ, then I don't need the assembly right?

<add assembly="System.Web.Extensions, Version=3.5.0.0,
Culture=neutral,
PublicKeyToken=31BF3856AD364E35" />
<add assembly="System.Web.Extensions.Design, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
=============================

These two ones are for ASP.NET ajax service (contains many extension
classes components which is necessary to make ASP.NET ajax work)

System.Web.Extensions.Design is part of System.Web.Extensions, so why

would

>I need both? Can't I just reference System.Web.Extensions?

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

If you haven't used any LINQ feature, you can certainly remove the

reference. As for the green line warning, I think it is likely a
design-time error producted by IDE, I cannot get the exact cause from the
general appearnce.

The exact warning message is:

Namespace or type specified in the Imports ‘System.Xml.Linq’ doesn’t contain
any public member or cannot be found. Make sure the namespace or the type is
defined and containes at least one public member. Make sure the imported
element name doesn’t use any aliases.

I would like to remove the assembly since I don't use it, but I want to find
the source of the warning and correct it - not just ignore it.

Also, for the assemblies I do need, should they be exactly matched between
web.config and My Project? Why are there 2 places to configure this?

System.Web.Extensions.Design is part of System.Web.Extensions, so why would
I need both? Can't I just reference System.Web.Extensions?

[Steven Cheng [MSFT]]

Thanks for your reply MCM,

The reason there're two setting for assemblies is probabaly due to the
project type. As I mentioned ealier there are two project types, and for
the "Web Application Project", it can let you configure assemblies at both
project level and in web.config.

In such case, the two configuration will help on the following parts:

1. The project level assemblies are used for building assemblies that is
generated (from code behind and other source file) at design-time in IDE

2. the web.config assemblies are still used for dynamic compilation occurs
at runtime.

They're different and not duplicatad.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
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.
--------------------

>References: <6A**********************************@microsoft.co m>

<TN**************@TK2MSFTNGHUB02.phx.gbl>
<3D**********************************@microsoft.co m>
<9E**********************************@microsoft.co m>
<80**************@TK2MSFTNGHUB02.phx.gbl>

>Subject: RE: web.config required elements
Date: Fri, 22 Aug 2008 00:18:00 -0700

>
The exact warning message is:

Namespace or type specified in the Imports ‘System.Xml.Linq�doesn’t

contain

>any public member or cannot be found. Make sure the namespace or the type

is

>defined and containes at least one public member. Make sure the imported
element name doesn’t use any aliases.

I would like to remove the assembly since I don't use it, but I want to

find

>the source of the warning and correct it - not just ignore it.

Also, for the assemblies I do need, should they be exactly matched between
web.config and My Project? Why are there 2 places to configure this?

System.Web.Extensions.Design is part of System.Web.Extensions, so why

would

>I need both? Can't I just reference System.Web.Extensions?