I know this issue was touched on in another thread (http://tiny.cc/0C7CG) but I am not clear on what I should really do.  My 5.0.1 web.config has about 10+ lines that refer to version 3.5.0.0 including:

• module/scriptmodule
• handler/AJAX_ScriptResourceHandler
• handler/AJAX_AppServiceHandler
• handler/AJAX_AppServiceHandler
• httpmodules/scriptmodule
• htthandlers/.asmx
• httphandlers/_appservice.axd
• httphandlers/scriptresource.axd
• controls/system.web.ui

Also the item controls/system.web.ui.webcontrols was removed completely (it was also 3.5.0.0).

The thread mentioned above says to add the assemblybinding section referencing 3.5 and remove the System.Web.Extensions.dll from the bin directory.

Obviously I'm hesitant to do all these changes without someone from DNN saying that this is in fact the recommended approach but thus far I have not seen anything to that effect.  FYI, I am trying to use NukePress and they have found that this is an issue with using their module so I'm in somewhat of a bind here.

Reccomendations?

Kevin

Kevin_at_matice.com

A little more info that is even more perplexing.  I installed DataSprings Opt In Email and goofed and put the 32 bit version in when I am running Windows 2008 x64 (as a HyperV image), fully patched (including ASP3.5 SP1 and 2 automatic hotfixes for asp3.5) .  Installing that module "broke" my site but what I noticed on the error page at the bottom that it said "ASP.NET Version:2.0.50727.4016".  I would have expected that to be 3.5.  My host settings shows .Net framework 3.5.  My DNN version is 05.01.01 (98).  FYI, I was able to easily uninstall that module and install the 64 bit version, no problem.

But after all this, I am not really sure what ASP library DNN is using. I'm hoping that someone can compare my web.config with a working 5.1 config.  Mine is here with the machine key and user/password info wiped: http://admin.delmarvainteractive.com/LinkClick.aspx?fileticket=ZPvRMamIA4s%3d&tabid=359.

FYI, NukePress did provide an updated module (v5.2) and it works fine now (as long as I don't remove the web.config line containing System.Web.UI.WebControls).

And for what it's worth, LinqPrep which was recommended by NukePress to make sure that Linq was setup properly gives this error (which could be by design now that Linq is built in?):

Error: LinqPrep is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: c:\inetpub\wwwroot\DNNProduction\DesktopModules\LinqPrep\View.ascx.cs(194): error CS1061: 'AssemblyInfo' does not contain a definition for 'Assembly' and no extension method 'Assembly' accepting a first argument of type 'AssemblyInfo' could be found (are you missing a using directive or an assembly reference?) ---> System.Web.HttpCompileException: c:\inetpub\wwwroot\DNNProduction\DesktopModules\LinqPrep\View.ascx.cs(194): error CS1061: 'AssemblyInfo' does not contain a definition for 'Assembly' and no extension method 'Assembly' accepting a first argument of type 'AssemblyInfo' could be found (are you missing a using directive or an assembly reference?) at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

Any help is appreciated.

Kevin

.Net 3.0 and .Net 3.5 just added capabilities to .Net (WCF, WWF, etc) but as far as the the version that is runs under it is .Net 2.0 (take a look at IIS, there is not options to run a site under anything higher than 3.5. The libraries needed to support Ajax was an addin for .Net 2.0 when it first came out (1.0.0.0), but when 3.5 was release it installed all the AJAX libraries (3.5.0.0) and that is the reason the version number needs to be changed,  One of the biggest differences is the version that come with 3.5.0 is registered in the GAC, while the original 1.0.0.0 version was not.  So really all DNN 5.0.1 does is support 3.5.0 out of the box so that the latest version of AJAX is supported.