Automatic Add-ins of .Net 2.0 assemblies in Web.Config

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
1/15/2013 11:00:49 PM
Gravatar
Total Posts 57
Web Platform Evangelist.

Automatic Add-ins of .Net 2.0 assemblies in Web.Config

Hi Joe,

Warm Greetings to you and Community members after the beginning of another New Year with mighty changes kicking-out the false beliefs of the world being ended last month/year.


I've been facing an issue with ver.2.3.9.4, where the Web.config keeps adding a seperate area for .Net 2.0 assemblies, despite I, adding them in the Compilation area. It keeps adding everytime as mentioned below

<system.web>
    <compilation>
      <assemblies>
        <add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
      </assemblies>
    </compilation>
  </system.web>


Finally confusing the Web.config when it runs during the development.
Any Hot Fix for this?

I'm using IIS 8.0 on a Windows 8 machine.

Regards,

Guruprasad

1/16/2013 7:34:31 AM
Gravatar
Total Posts 18439

Re: Automatic Add-ins of .Net 2.0 assemblies in Web.Config

Why don't you use .NET 4 or better yet .NET 4.5?

Web.config is not capable of modifying itself, maybe the runtime or IIS could be doing that but it never happens to me and I have no idea why it would need those. Maybe if you installed .NET 2 on your win 8 dev machine it needs to add those because they are so old but the deployment server running an older OS doesn't need them.

.NET 3.5 is a superset of 2.0 but still those assemblies don't generally need to be listed in web.config.

I assume you are using .NET 3.5 because for sure .NET 4 would not add those assemblies. 

My recommendation to everyone is stop using .NET 3.5 and migrate to 4.5 and using the 4.0 package of mojoPortal. We may drop support for .NET 3.5 in the not too distant future, it is time for .NET 3.5 to be retired. Time and progress march on.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.