| |
|
|
|
|
|
|
|
|
|
 |    |  |
 | |  |
 | |  |
 | |  |
 | |  |
 |
|
|
| How to upload a module writen in .net 3.5 to an existing Portal with DNN 4.8.4 |
|
|
Hi,
how can I upload a DNN module writen in .net 3.5 with linq and AjaxControlToolkit for 3.5 to an existing Portal with DNN 4.8.4.
I always got this mistake:
Error: TestModule is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: (0): error CS1705: Assembly 'AjaxControlToolkit, Version=3.0.20229.20843, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' uses 'System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ---> System.Web.HttpCompileException: (0): error CS1705: Assembly 'AjaxControlToolkit, Version=3.0.20229.20843, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' uses 'System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' at System.Web.Compilation.AssemblyBuilder.Compile() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() 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 System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---
If I change the System.Web.Extensions from Version=1.0.61025.0 to Version=3.5.0.0 manually, then the modules are running, but other thing from the DNN Framework are out of order (e.g. the host settings from the host menue or I can´t open the module definitions for the modules with the pen on the left site of each module.)
Does anybody knows the answer?
Best regards,
Alex
|
|
|
|
 |  |
|
|
| Re: How to upload a module writen in .net 3.5 to an existing Portal with DNN 4.8.4 |
|
|
You will need to upgrade your site to use the 3.5 libraries.
|
|
|
|
 |  |
|
|
| Re: How to upload a module writen in .net 3.5 to an existing Portal with DNN 4.8.4 |
|
|
Yes, but how can I do this?
I found a description from Michael at dotnetnuke.adefwebserver.com
and I modify the web.config as he wrote, but I still got the following error when I try to put his demo mdoule on a page with DNN 4.8.4:
Fehler: LinqThings4Sale ist zur Zeit nicht verfügbar.
DotNetNuke.Services.Exceptions.ModuleLoadException: Unknown server tag 'asp:LinqDataSource'. ---> System.Web.HttpParseException: Unknown server tag 'asp:LinqDataSource'. ---> System.Web.HttpParseException: Unknown server tag 'asp:LinqDataSource'. ---> System.Web.HttpException: Unknown server tag 'asp:LinqDataSource'. at System.Web.UI.TagPrefixTagNameToTypeMapper.System.Web.UI.ITagNameToTypeMapper.GetControlType(String tagName, IDictionary attribs) at System.Web.UI.MainTagNameToTypeMapper.GetControlType2(String tagName, IDictionary attribs, Boolean fAllowHtmlTags) at System.Web.UI.MainTagNameToTypeMapper.GetControlType(String tagName, IDictionary attribs, Boolean fAllowHtmlTags) at System.Web.UI.RootBuilder.GetChildControlType(String tagName, IDictionary attribs) at System.Web.UI.ControlBuilder.CreateChildBuilder(String filter, String tagName, IDictionary attribs, TemplateParser parser, ControlBuilder parentBuilder, String id, Int32 line, VirtualPath virtualPath, Type& childType, Boolean defaultProperty) at System.Web.UI.TemplateParser.ProcessBeginTag(Match match, String inputText) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() 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 System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---
How can I check if my Provider has installed the .net 3.5 framework correct?
What can I do?
I have no idea.
Best regards,
Alex
|
|
|
|
 |  |
|
| |
 |  |
|
|
| Re: How to upload a module writen in .net 3.5 to an existing Portal with DNN 4.8.4 |
|
|
As others mentioned it is pretty difficult to determine the version of framework running without access to the server or full trust (see this article... pretty interesting, but you probably wouldn't be able to do it in a hosting environment: http://www.codeproject.com/KB/cs/frameworkversiondetection.aspx)
You'll need to just contact your hosting provider and ask them.
One thing that I have found useful on my instances of DNN is to ensure all the modules will use the latest version of the framework and AJAXControlToolkit (this is unrelated to your error... but a "good tidbit"). You can use the assembly binding to remap older versions to newer versions. Insert the following tags just before the closing tag in your web.config:
EDIT: ok, it stripped out all those tags... nice. I repasted and replaced all the less than with <_ and all the greater than with >_ -- copy out into notepad and replace them with their appropriate symbols.
<_runtime>_
<_assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">_
<_dependentAssembly>_
<_assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>_
<_bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>_
<_/dependentAssembly>_
<_dependentAssembly>_
<_assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>_
<_bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>_
<_/dependentAssembly>_
<_dependentAssembly>_
<_assemblyIdentity name="AjaxControlToolkit" publicKeyToken="28f01b0e84b6d53e" />_
<_bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.0.20229.0"/>_
<_/dependentAssembly>_
<_/assemblyBinding>_
<_/runtime>_ -- Fooberichu
http://www.seeleyware.com |
|
|
|
|  |
 | |  |
 | |  |
 | |  |
|  |
| |
 |
|
These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.
For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.
|
| |
 |
|
|
|
|
|
|
|