Comments on: Build your own modded System.Web.Extensions.dll

By: rewrq

rewrq — Tue, 29 Jul 2008 22:04:09 +0000

rere gfdg
sdfg
dfgdfg
fdgdfg

By: Dll Weed

Dll Weed — Tue, 24 Jul 2007 19:31:30 +0000

I’ve got a headache and blood is coming out my ears. lol

Thanks for the article this is going to take me some time to digest.

By: Prof. Dark

Prof. Dark — Fri, 20 Jul 2007 22:24:35 +0000

You can remove the need to change all of the Resource References to the fully qualified names if you change the <RootNamespace> tag in the project that you create to be blank. This will make the resources created by the project not have the namespace pre-pended. If you plan on the using the default System.Web.Extensions namespace then you shouldn’t have to make any code changes.

By: Robert Hope

Robert Hope — Thu, 22 Feb 2007 23:39:27 +0000

One other thing on this, be aware that if you replace “system.web” with your own namespace there are also hardcoded references to configuration sections you will need to change that won’t break the build but will break at runtime…and that you will need to change all of the references to System.Web.Extensions in the web.config to your own version…

thanks for putting this out there!

By: theGooley

theGooley — Wed, 31 Jan 2007 07:42:02 +0000

The client-side code and server-side code were released under seperate licenses. Client side was under the Permissive License which is great. The way Microsoft released the server source basically forces it to be for reference only (under the Reference License). By posting – essentially redistributing – a compileable version it would not be used for reference purposes, people would download it and use it in the their projects which would violate the “specifically excludes the right to distribute the software outside of your company” clause of the Reference License… but IANAL either. So that’s just my take.

By: Jody

Jody — Wed, 31 Jan 2007 07:35:31 +0000

Thanks for posting it and being so informative – glad at least you found a resolution to the issues that you documented and followed-up on the other thread…

I may be incorrect – but there is nothing I believe that prohibits re-distribution or including a project download of it (project solution) – as it is for reference use. Further more – I am no lawyer however – the license does state as long as you are not using Microsoft’s name to promote it then you can pretty much do as what you wish and there is not an issue with modifying it redistributing as you see fit as long as you do not use any of Microsoft’s name, copyrights, logos etc…