| Author |
Messages |
|
Dario Rossa
Posts:11
 |
| 06/11/2008 9:56 AM |
|
Hi All,
I googled for hours but didn't find any solution to the error I receive when trying to install on production my Silverlight 2 Beta 2 module:
DotNetNuke.Services.Exceptions.ModuleLoadException: d:\HostingSpaces\gnogna82\dariorossa.it\wwwroot\DesktopModules\BlogResume\View.ascx(5): error BC32206: The project currently contains references to more than one version of System.Web.Extensions, a direct reference to version 1.0.61025.0 and an indirect reference (through 'System.Web.UI.SilverlightControls.Silverlight') to version 3.5.0.0. Change the direct reference to use version 3.5.0.0 (or higher) of System.Web.Extensions. ---> System.Web.HttpCompileException: d:\HostingSpaces\gnogna82\dariorossa.it\wwwroot\DesktopModules\BlogResume\View.ascx(5): error BC32206: The project currently contains references to more than one version of System.Web.Extensions, a direct reference to version 1.0.61025.0 and an indirect reference (through 'System.Web.UI.SilverlightControls.Silverlight') to version 3.5.0.0. Change the direct reference to use version 3.5.0.0 (or higher) of System.Web.Extensions. 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 ---
My web.config file uses:
<assemblies>
<add assembly="Microsoft.VisualBasic, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Data.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
</assemblies>
It just works fine in my local installation. Any ideas?
Best regards,
Dario Rossa
|
|
|
|
|
Michael Washington (admin)
Posts:67
|
| 06/11/2008 10:40 AM |
|
Believe me I had the same problems trying to install the Silverlight 2 Beta 2 samples on this site.
1) You have to put ALL the assemblies and resource files in the "bin" directory on your production site.
2) There are a LOT of associated entries in the web.config to get the Silverlight control (the thing that launches the Silverlight application on the web page) to work.
So I just:
A) Made sure my dev and production site were running the same version of DotNetNuke.
B) Copied the web.config from the Dev site to production and updated the SQL, Machine key, and code sub directories entries
As you can see it works. |
|
|
|
|
Dario Rossa
Posts:11
|
| 06/11/2008 1:02 PM |
|
Hi Michael,
thanks so much for the sharing!
1) Actually I am developing a module using WSP type and Silverlight 2 Beta 2. The only assembly I uploaded was System.Web.Silverlight.dll v 2.0.5.0 All the code behind, LINQ and webservices went to App_Code and module's folder itself.
2) After targeting 3.5 I already noticed that so many changes were made to the web.config but I was scared about moving all of it to production, so I was convnced not to do so. But after reading your post I tried and it solved the issue, thanks so much! I observed A & B, and all was fine.
Now I see just a white rectangle, and the error is: "Could not download the Silverlight application. Check web server settings". I wonder if this is due to missing MIME type for .xap on production, but how can I check for this? I have no control on IIS since I'm on a shared hosting...
Best regards,
Dario Rossa |
|
|
|
|
Michael Washington (admin)
Posts:67
|
| 06/11/2008 1:10 PM |
|
| I bet it's your MIME settings. Simply email your tech support and tell them to look at: Setting .xap MIME Type for Silverlight 2.0 (http://www.adefwebserver.com/DotNetNukeHELP/Misc/Silverlight/SettingMimeType.html) |
|
|
|
|
Dario Rossa
Posts:11
|
| 06/11/2008 1:20 PM |
|
Hi All,
correction! I definitely CAN control MIME types on my shared hosting through DotNetPanel. Just added .xap and the module lives! Sooooo good...
P.S. Thank you very much Michael for your support, it took me to the right direction.
Best regards,
Dario Rossa |
|
|
|
|
|