DotNetNuke Hosting with ASPHostPortal.com

BLOG about DotNetNuke CMS, latest technology and Special DotNetNuke Hosting Package with ASPHostPortal.com

DotNetNuke 7.3 Hosting with ASPHostPortal.com :: Develop a Compiled DotNetNuke Module Utilizing the Visual Studio Starter Kit

clock Oktober 30, 2014 06:09 by author Ben

The Visual Studio Starter Kit enables you to create a compiled DotNetNuke module that can be much more compact, more quickly, and hide your supply code from prying eyes. The subsequent instructions can get you started and well in your approach to creating compiled DotNetNuke Modules.


  1. Download the Starter Kit
  2. Open Visual Studio  and create a new project (File -> New Project)

    From the dialogue follow these steps

    • Select Web from the Installed Templates. I use of VB.Net, but they are available in C# too.
    • Pick DotNetNuke Compile Module from your Project Type list.
    • Enter your Module Name
    • Enter the path for your DotNetNuke installation. Your project will be installed within the current set up within the DesktopModules folder and also the dll will likely be place in the bin folder.
    • Click OK
  3. Visual Studio will load up the venture within the Solution Explorer and open the Documentation.html in the editor. You’re not however ready to set up the module so don’t keep to the DotNetNuke documentation but.
  4. In the Solution Explorer right click on My Project and select Open.

  5. Within the Application tab delete the entry in Root Namespace except if this is your only module, otherwise you will not be sharing code with other modules. I have a undertaking that spans numerous modules and i want them all inside the identical identify space. So, I delete the basis Namespace entry to ensure that I am able to put within the appropriate namespace from the code driving. (Edit regarding Root Namespace; in C# you do not need to clear the namespace, but in VB.Net you are doing).

  6. Switch towards the Compile tab. Verify the Build output path and make sure its pointing towards the proper bin folder. Now simply click the Advance Compile Option on the button of the tab. Around the dialogue make certain the target framework is correct. You’ll see the environment on the base of the dialogue. At this point the dialogue will immediately near.
  7. Repeat step 4 (open the project properties) then go to step 8
  8. Switch to the References tab.  You should see a reference to DotNetNuke.Library version 0.0.0.0.  Remove it.

  9. Nonetheless around the References tab, now click the Add button. Inside the Add Reference dialogue switch to the Browse tab and navigate for the DotNetNuke set up bin folder. Choose the DotNetNuke.dll, DotNetNuke.Web.dll, as well as the Telerik.Web.UI.dll. Should you do not hold the Telerik.Web.UI.dll then you definitely should not be making use of those controls and you also will not want the dll. Click Okay. These references are necessary to obtain access to the DotNetNuke methods and properties. In any other case you are code powering will be crammed with inexperienced and blue underlines, missing references, and, oh yeah, it won’t compile. Sort of defeats the aim, proper?



    Intellisense; this step is optional, but if you want Intellisense you’ll want to do this.  Switch to the Web tab. Under Servers select the “Use Local IIS Web server” option.  Change the Project URL to the full URL of your project (eg http://{domain}/DesktopModules/{project folder}).  Check “Override application root URL” and set it to the domain of your DotNetNuke install (eg http://{domain})
  10. Save the Project Properties and close it.
  11. Inside the Solution Explorer increase the Components folder and open up the ModuleNameController.vb (or .cs) file. Check the Namespace declaration and you’ll see that it states “YourCompany”. Change this to your customized namespace identifier and after that do the identical in each of the code powering documents. You will also need to change it inside the .ascx files because they’ll be reference the namespace inside the handle declaration at the best of the webpage.
  12. At this point you can Build your project and you will see the new dll in your DotNetNuke install bin folder.
  13. Now follow the instructions in the documentation.html to install the module in DotNetNuke.  Once the module is installed you don’t really need the documentation folder, or it’s files.  I usually delete it.



DotNetNuke 7.3 Hosting with ASPHostPortal.com :: Using the new Module Improvement Templates for DotNetNuke 7

clock Oktober 17, 2014 06:18 by author Ben

Obtaining up and operating with all the templates is really pretty straightforward, but you must stick to some really certain measures, not subsequent the measures tends to make it hard for anyone else in order to assist you as you can configure issues any number of ways that might cause difficulties.

 


Configuring your Development Atmosphere

This really is 1 from the most significant steps from the procedure, the templates are configured to operate in a site You'll find a couple of assets for placing up your environment. The crucial thing for your new release of the templates is you need to have DotNetNuke 7.3 operating at dnndev.me, unless of course needless to say you modify the templates your self, but that's outside of the scope of this weblog post.

Putting in the Templates

Installation in the templates is pretty simple, you'll find numerous techniques to complete this, select one in the a few choices beneath and carry out the actions outlined for the option you decide on. You simply have to do one of those choices, not all three.

  1. Put in utilizing the Tools\Extensions and Updates menu in Visible Studio 2012
    • Mouse more than the Tool menu
    • Click on Extensions and Updates
    • Search for DotNetNuke
    • Select the Put in button to the DotNetNuke Project Templates option
  2. Install manually by downloading the VSIX file from the online gallery
    • Pay a visit to the Visual Studio Gallery - DotNetNuke Project Templates page
    • Download the VSIX file via the Obtain website link.
    • Double click the downloaded file to install the templates.
  3. Set up manually by downloading from Codeplex
    • Down load the VSIX file from Codeplex
    • Updated - Right Click the downloaded VSIX and choose Properties
    • Click the UNBLOCK button before proceeding
    • Double click the downloaded file to install the templates.

Making your Visual Studio Project

As soon as you have put in the templates, you can set up a project based on the templates. To do so you need to stick to the steps under

  1. Set up Visual Studio 2012 (you need to have this done presently)
  2. Install the undertaking templates as instructed above
  3. Setup your DotNetNuke Advancement Environment as instructed over
  4. Operate Visual Studio 2012 as an Administrator (correct click on the shortcut to do so)
  5. File -> New Project
  6. Choose possibly C# or VB.Net from your Languages segment of the new Project dialog
  7. Pick the DotNetNuke Folder under your preferred language (C# or Visual Basic)
  8. Choose possibly DotNetNuke C# Compiled Module, DotNetNuke VB.Net Compiled Module, DotNetNuke 7 C# DAL2 Compiled Module or DotNetNuke 7 VB.Net DAL2 Compiled Module for the project template.
  9. For the new project creation screen using the following settings
    • Title: ModuleName (something distinctive here, instance MyModule)
    • Place: c:\websites\dnndev.me\desktopmodules\ (this assumes you set up your improvement surroundings as instructed in Step 3)
    • Solution: Create new solution (this option might not be exhibited, that's okay)
    • Create directory for solution : Unchecked (this may trigger route issues if checked, the templates presume the SLN is inside the same folder since the project file)
    • Add to source control: Unchecked (I typically get my undertaking operating before incorporating it to supply control)
  10. Click Ok
  11. In certain cases Visual Studio will change the DesktopModules folder in into a Digital Listing, this will cause problems with your DNNDEV.me environment, load IIS Supervisor (start>run>INETMGR) and take away the Virtual Directory if it appears as a single there.

Installing your Module in Improvement

Once you create your project in Visual Studio 2012 the module will exist within the c:\websites\dnndev.me\desktopmodules\MyModule folder, but it is not technically installed and registered with DotNetNuke. To complete that you need to execute the follow steps.

  1. Develop your Project in DEBUG mode.
  2. Modify to Release mode and build again.
  3. Login to your improvement website within a browser, using a HOST/SuperUser account.
  4. Navigate for the Host/Extensions web page
  5. Pick the Install Extension Wizard option
  6. Simply click Choose File
  7. Browse to your c:\websites\dnndev.me\desktopmodules\MyModule\Install\ choose either the INSTALL or SOURCE package to upload.
  8. Go through the measures for the installation wizard (if the module fails to install, attempt closing Visual Studio very first, then set up the module)
  9. Location your module on a page (I usually produce a fresh webpage for each module in my development environment for tests reasons).

 

Setting up your Module in Production

To install your module in production you'll keep to the same actions as installing it inside your improvement environment, other than you will nearly Never utilize the Source package of the module in creation, it just is not essential.

What’s Subsequent?

So I lastly received the 7.0 (7.3) templates out the door, what is subsequent? Reworking the DNNTaskManager module which i created a module advancement tutorial for back in 2011. The program is to actually rewrite that module from the ground up utilizing DNN seven.0, in a few distinct iterations. 1) Utilizing the unique DAL design in DotNetNuke, 2) Using the new DAL2 template, 3) Utilizing ContentItems in DotNetNuke 7. Keep tuned to my weblogs to learn more as those tutorials are produced.



DotNetNuke 7.3 Hosting with ASPHostPortal.com :: How To Get Your DotNetNuke Websites To Run So Fast

clock Oktober 14, 2014 06:14 by author Ben

Certainly one of the commonest queries which i get by way of the community forums on this website, or via e-mail is "How does one get your websites to operate so fast". Although not excellent, my web sites normally operate somewhat more quickly than your typical DotNetNuke 7.3 websites. Formerly I have stored the exact particulars of my changes to myself, nevertheless, with a litle encouragement from the neighborhood I've chose to share the full context of the changes that i make into a default DotNetNuke set up to acquire better baseline performance, as well as added products that i do to aid when i actually want that "boost".

 


Overview

To begin with I want to begin out by declaring that a great deal in the details that's shown listed here could be located in previous website postings. Posts this sort of as DotNetNuke Host Options Explained, DotNetNuke Scheduler Explained, DotNetNuke Overall performance Options Defined, and straightforward DotNetNuke Performance Enhancements. Are good beginning factors for a few of the element driving my recommended adjustments.

The subsequent changes are merely the configurations that i have found for being the very best "baseline" configurations. Consideration is required in regards to the web site setup, update frequency, traffic, hosting environment and users to ensure that you have the correct set up for your particular atmosphere. I'll talk about the options section by segment, merely noting the modifications which can be created. Remember to reference the specific "Detail" doc for more information.

DISCLAIMER: Adhere to these suggestions as a manual only, I am not responsible for any results of employing these adjustments.

Host -> Host Options Changes
The first place I pay a visit to may be the Host Options page. There are a selection of key updates and adjustments required on this segment. Again, only changes are noted right here.

Appearance
In this segment I uncheck the "Show Copyright Credits" box

Advanced -> Authentication Settings
Within this segment I uncheck "Enabled" for almost any provider that will not be utilized in the portal, normally the LiveId and OpenId companies

Advanced -> Performance Settings
On this area I change the "Module Caching Method" to Memory. the "Performance Setting" to HeavyCaching. As well as the "Compression Setting" to GZip Compression.

Advanced -> Other Options
In this section I modify the "Scheduler Mode" to Timer. I enable the "Event Log Buffer" and i disable the "Auto-Sync File System" alternative

They are the commonest Host Options adjustments which i total. Based within the website I'll make a couple of other little edits.

Host -> Scheduler Changes
The largest alter that i make right here would be to modify the "SearchEngineScheduler" task to run normally as soon as every 12/24 several hours. This reduces a big load around the server.

Other Modifications
From a DotNetNuke configuration alter which is all that I modify. Overall these adjustments typically outcome in extremely noticable efficiency advancements, but often times it just isn't adequate to maintain the web sites operating as smooth as possible. So according to the specific situation I have numerous other things which i function with.

Normal Purging of Occasion Log
As a lot of people which have utilized DotNetNuke have identified the EventLog table could become a very troublesome hinderance within the performance facet of a web site. Enabling the Event Log Buffer helps reduce the consequences of the huge EventLog, nonetheless, the most effective policy is always to thoroughly clean the EventLog on a normal foundation.

I try this one of two methods. By myself sites I have an SSIS package deal inside of SQL Server that truncates the desk each 24 hrs. On customer web sites I make use of my Scheduled SQL Employment module to keep a seven working day rolling historical past of the EventLog information. The key here is the fact that we must keep the occasion log tiny.


Skin Choice and Menu Provider
The next item of thought is actually a multi-part thought. I target on finding CSS primarily based pores and skin layouts that use 3rd party menu parts this sort of as Telerik and Css NavMenu. With a straightforward pores and skin modify to sites I've seen webpage load occasions which have decreased by more than 50%.

Discovering an excellent designer that creates well laid-out skins with 3rd get together menu suppliers is a crucial overall performance enhancement, a minimum of in the page. I've NOT benchmarked these numbers although because DNN 4.six.2, so the core menu company might have much better performance.

Compression/Caching Modules

Like a last stage, if I actually need to get the most performance out of a website I will often lean towards Snapsis PageBlaster as being a good alternative. I at present use PageBlaster on this website only and also have had really excellent luck with it, though when configuring the module you have to be cautious to test all functionality very first. This was another change that after applied I seen really noticeable efficiency advancements.



DotNetNuke 7.3 Hosting with ASPHostPortal.com :: Skinning Responsively The DDR Menu with Bootstrap for DotNetNuke

clock Oktober 7, 2014 06:01 by author Ben

With all the introduction of the DDRMenu to DotNetNuke, we've experienced much more manage above what is rendered from the menu. This has authorized for a a lot more semantic menu and custom made styling for easy menus to mega menus. There are numerous methods to create the template that the DDR makes use of but we'll be using the token primarily based templating because it is quite easy.


Menu Template (Bootstrap Nav)

I copied the easy folder from your Gravity pores and skin that will come with DNN 7, which incorporates a manifest file “menudef.xml” and the “SimpleToken.txt” file. I updated the SimpleToken.txt file as follows:
Notice: this isn’t a tutorial on DDRMenu, just how to apply Bootstrap.

<ul class="nav nav-pills">
    [*>NODE]
    </ul>
    [>NODE]
        <li class="[?NODE]dropdown [/?][?SELECTED]active[/?]">
        [?ENABLED]
            <a href="[=URL]">[=TEXT] [?NODE]<b class="caret"></b>[/?]</a>
        [?ELSE]
            <a href="#">[=TEXT] [?NODE]<b class="caret"></b>[/?]</a>
        [/?]
        [?NODE]
            <ul class="dropdown-menu">
            [*>NODE]
            </ul>
        [/?]
        </li>
    [/>]

  1. Add the classes nav and nav-pills to the outer ul. Individually, I favor the simplicity in the Simple tablets nav that bootstrap gives. This appears to be the easiest to override with my own custom design and style as I have a tendency to use more flat UI’s in my style.
  2. Include the category “dropdown” for the list merchandise if it's youngsters using the [?NODE] examination.
  3. Add the category “active” for the listing product whether it is selected utilizing the [?SELECTED] examination.
  4. Add a caret to the merchandise if it's a baby item.

Up coming, we are able to include the HTML and pores and skin object within the pores and skin as follows:


Logo and Menu pores and skin objects (Bootstrap Navbar)

<div class="navbar">
        <div class="navbar-inner">
            <span class="brand">
                <dnn:LOGO runat="server" id="dnnLOGO" />
            </span><!--/Logo-->
            <dnn:MENU MenuStyle="Simple" runat="server"></dnn:MENU>
        </div><!-- END navbar-inner -->
    </div><!-- END navbar -->


  1. add link with class “btn” and btn-navbar”. Also, requires markup for collapse. You are able to use either JavaScript or information attributes.
  2. Wrap dnn:MENU pores and skin item using a div using the adhering to class
    “nav-collapse” and “collapse” - this permits the menu to break down at smaller display screen sizes
    “pull-right” to drift the menu to the correct side, if you so desire.

 

Note: making use of this process will disable a menu merchandise which has children. In order that this is a click to open up motion. This can be to make things function much better for contact units.



About ASPHostPortal.com

We’re a company that works differently to most. Value is what we output and help our customers achieve, not how much money we put in the bank. It’s not because we are altruistic. It’s based on an even simpler principle. "Do good things, and good things will come to you".

Success for us is something that is continually experienced, not something that is reached. For us it is all about the experience – more than the journey. Life is a continual experience. We see the Internet as being an incredible amplifier to the experience of life for all of us. It can help humanity come together to explode in knowledge exploration and discussion. It is continual enlightenment of new ideas, experiences, and passions


Author Link


Corporate Address (Location)

ASPHostPortal
170 W 56th Street, Suite 121
New York, NY 10019
United States

Tag cloud

Sign in