Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDNN Silverlight Module Package Nightmare!!DNN Silverlight Module Package Nightmare!!
Previous
 
Next
New Post
6/29/2010 7:58 PM
 
Hi All,
I recently Completed a silverlight application (Still on Silverlight 2) that is hosted in DNN 5.4.2.  I created a Module package and Modified the dnn5 manifest to the following:

<dotnetnuke type="Package" version="5.0">
  <packages><package name="LMS.Reservations" type="Module" version="0.0.0">
  <friendlyName>LMS Reservations</friendlyName>
  <description>This module manages LMS Reservations</description>
  <owner>
    <name>Mr Alex Masita</name>
    <organization>Data Volts Systems Enterprises</organization>
    <url />
    <email>alexmasita@hotmail.co.uk</email>
  </owner>
  <license />
  <releaseNotes />
  <components>
    <component type="Module">
      <desktopModule>
        <moduleName>LMS.Reservations</moduleName>
        <foldername>LMS.Reservations</foldername>
        <businessControllerClass />
        <supportedFeatures />
        <moduleDefinitions>
          <moduleDefinition>
            <friendlyName>LMS Reservations</friendlyName>
            <defaultCacheTime>0</defaultCacheTime>
            <moduleControls>
              <moduleControl>
                <controlKey />
                <controlSrc>DesktopModules/LMS.Reservations/ViewLMS.Reservations.ascx</controlSrc>
                <supportsPartialRendering>False</supportsPartialRendering>
                <controlTitle>View Reservation Details</controlTitle>
                <controlType>View</controlType>
                <iconFile />
                <helpUrl />
              </moduleControl>
            </moduleControls>
          </moduleDefinition>
        </moduleDefinitions>
      </desktopModule>
    </component>
    <component type="ResourceFile">
      <resourceFiles>
        <basePath>App_Code</basePath>
        <resourceFile>
          <name>App_Code.zip</name>
        </resourceFile>
      </resourceFiles>
    </component>
    <component type="Assembly">
      <assemblies>
        <basePath>bin</basePath>
        <assembly>
          <name>LMS.Reservations.dll</name>
        </assembly>
        <assembly>
          <name>System.Web.Silverlight.dll</name>
        </assembly>
      </assemblies>
    </component>
    <component type="File">
      <files>
        <basePath>DesktopModules\LMS.Reservations</basePath>
            <file>
              <path>App_LocalResources</path>
              <name>EditLMS.Reservations.ascx.resx</name>
            </file>
            <file>
              <path>App_LocalResources</path>
              <name>Settings.ascx.resx</name>
            </file>
            <file>
              <path>App_LocalResources</path>
              <name>ViewLMS.Reservations.ascx.resx</name>
            </file>
        <file>
          <name>EditLMS.Reservations.ascx</name>
        </file>
        <file>
          <name>ViewLMS.Reservations.ascx</name>
        </file>
        <file>
          <name>ReservationManagement.svc</name>
        </file>       
         <file>
           <path>..\..\ClientBin</path>
          <name>SDASL.Reservations.xap</name>
        </file>
      </files>
    </component>
  </components>
</package>
</packages>
</dotnetnuke>

All the files in this manifest are packaged properly but the Xap file as defined in the highlighted section above is not added in the created package and no errors are thrown!  Oddly, when I remove the <path>..\..\ClientBin</path> tag from the Xap file, it is now added to the zip file as expected but that would mean that on installation on the target website, the .Xap file will not be installed in the right folder which should be the ClientBin folder that resides in the root of the website.  Any suggestions anyone?

NB: Please note that I tried playing around with the <path>..\..\ClientBin</path>  tag including reversing the back slash to the forward slash and also removing both back slashes and the dots to just have the ClientBin in the path tag but the Xap file still does not get added to the Zip Package.  It is only when I remove the entire <path>..\..\ClientBin</path> tag that the Xap file gets added to the Zip Package.  I await you suggestions?

Many thanks in advance,
Alex
 
New Post
6/30/2010 8:30 AM
 
I do it a slightly different way:

                <  component type="File">
                    < files>
                        < basePath>DesktopModules/Smart-Thinker - TournamentDirector/ClientBin

                        < file>
                            < name>TournamentDirector.xap
                        < /file>
                    < /files>
                < /component>
            < /components>

this works for me (I build my .zip files manually tho). Path seemed to be the location of the .xap file in the zip and hence the installer fell over- basepath is the destination folder (which will be created if it does not exist)

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
6/30/2010 8:47 AM
 
ps - it sounds like we are doing the same thing - perhaps you can help me with my Silverlight problem ;)
http://www.dotnetnuke.com/Community/F...

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
6/30/2010 5:46 PM
 
Hi Rodney,
Many thanks for your response.  I can agree with you on the purpose of the basePath but for the path tag, I still do not understand.  I was under the impression it was to give the developer more control as to where that particular file within the tag is to be installed relative to the basePath.  The way I verified this is through the App_localresources files which have a path tag and which on installation end up installing the files in the folder specified in the path tag relative to the basePath.  Though on further reflection, the structure of the files in the zip is relatively the same.  Guess I need to play around with this more...........let me know if you have any more ideas.  I can definitely tell you that the way I did it in the dnn5 manifest used to work at least in the dnn 4.9.2 version where for example consider the definition below:

<files>
<basePath>DesktopModules\LMS.Reservations</basePath>
<file>
           <path>..\..\ClientBin</path>
          <name>SDASL.Reservations.xap</name>
</file>
<files/>

So in dnn 4.9.2 I was able to have the SDASL.Reservations.xap installed on the website root under the ClientBin folder meaning Dnn 4.9.2 was intelligent enough to go two levels up the basePath and either find or create a ClientBin folder at that level and put in the Xap file.  Don't know why Dnn5 does not do this.......I am thinking maybe it's bug.

Thanks.
 
New Post
7/1/2010 5:45 AM
 
I also started off with the PATH tag - in DNN4 I used to send my resource files to the APP_R. directory using the PATH tag. However, I could not get it to work in DNN5.x but after reading some blog posts it sounds like basePath is designed to replace that functionality in DNN 5.x - but it works at least.

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDNN Silverlight Module Package Nightmare!!DNN Silverlight Module Package Nightmare!!


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, 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 DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out