Hi;

Just to let you know, I was trialing a blog module that was compiled in .net 3.5. The module required changes to the web.config to allow it to run .net 3.5.

This resulted in an error for the DUD. it was complaining UpdatePanel is ambigous across the namespace. Don't have the exact error message anymore and I uninstalled the other module and changed web.config back.

Just something you may test for in future as none of my other 3rd party modules caused any problems.

Thomas

HI Thomas, thanks for the heads up on this. -- David

Hi there;
Just a quick follow up on the post above, just wondering if you are working on a fix for this and what the situation is for your other modules.

I would like to purchase another module that requires .net 3.5 on the server and need a solution for this.
Thanks
Thomas

Thomas,

Hi. In general DNN doesn't come delivered with the 3.5 framework so you might run into more and more of these situations. Do you know the specific error message that its reporting? Was it the Nuke Press Blog module (I think its the only one I know of that directly changes the web.config for this). This is somewhat of a difficult scenerio as some modules will use one version of the framework and others will use another. Our module doesn't actually use the AJAX Toolkit at all because of this reason (moved to jQuery as much as possible). The module still uses the ASP.NET Update Panel but its not dependent on the AJAX Toolkit / version at all. So if you let me know the specific error I can do some testing, it would have to be related to the ASP.NET Update Panel because none of our modules use the control toolkit for either version specifically because of the difficulties you mentioned.

-Chad