Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not entirely sure about what you're looking to do, but I'll answer as much as I can.</p> <p>I would suggest setting up a DotNetNuke website on your local machine, using the Source package. You can then create a new module (starting it either through the website itself, or by using a <a href="http://www.engagesoftware.com/Blog/EntryId/162/C-Compiled-DotNetNuke-Module-Template.aspx" rel="nofollow noreferrer">Visual Studio template</a>). I strongly suggest <a href="http://weblogs.asp.net/ianrobinson/archive/2008/10/15/creating-dotnetnuke-modules-using-a-web-application-project-wap.aspx" rel="nofollow noreferrer">using a Web Application Project for the module</a>, keeping it in the website's <code>DesktopModules</code> folder (so that you're only dealing with the module's code, and don't have the entire website open in your project). Also, make sure you use the module and any other extension points to implement your functionality, rather than making changes to the actual DNN core code (since any changes to the core will make it that much more difficult to upgrade to newer versions of DNN).</p> <p>I strongly suggest getting some automated packaging in place (the template that I linked to has a <a href="http://nant.sourceforge.net/" rel="nofollow noreferrer">NAnt</a> build script with it that you can use to package your module). It is so much easier to deploy modules as installable packages than trying to migrate individual files.</p> <p>You can get the source version of the Documents module from <a href="http://dnndocuments.codeplex.com/" rel="nofollow noreferrer">its Codeplex project</a>. It's licensed under the MIT license (like DNN itself), so you're free to use it as a starting point for your own module. Just download the source package and install it into your development site. The install will include all of the source and also includes a Visual Studio project that you can use. After installing, I would suggest that your first step be to rename the namespace (so that you're differentiated from the core module).</p> <p><strong>UPDATE</strong><br> To deploy the website, I would suggest installing DNN on the server using the main DNN Install package. Then, once that is installed, you can install the module into the website using the package that you have created. A default installation of DNN will only have the Text/HTML module, in addition to administrative modules, so you shouldn't have very many extra, unused functionality present in the site.</p> <p>Leave me a comment &amp; update your question (or start a new question) if there's anything else you need to know.</p>
    singulars
    1. This table or related slice is empty.
    1. POdotnetnuke doubts
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USbdukes
    1. USbdukes
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POdotnetnuke doubts
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COthanks for d comment.regarding package, i have created packages for modules, but how would this be deployed at client side, if the client doesn't have dnn installed, lets assume. And if it has, do i need to install this in dnn pre-installed website with other default dnn modules present it (which may be of no use if its not needed by client)
      singulars
      1. PO
      1. USRomil N
    2. COthanks for the comment. As of now all my doubts are cleared. If i face some another doubt in DNN,i would ping you again
      singulars
      1. PO
      1. USRomil N
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload