Dotnetnuke standard installs using the dbo as the default user. Some hosts however, like shared hosting service providers, do not allow you to use dbo. So in this case you have to install Dotnetnuke using your assigned username. This should work without any problems. But in case you have an existing website which was installed using the dbo user and you would like to migrate it to a hosting provider that does not allow dbo you have a problem.

The easiest way to migrate a Dotnetnuke website is by backing up the entire web and the database and restore it to the new environment. This will work fine only if your new environment allows dbo. If it does not you will find that when restoring the database all objects will have been assigned to your username and not to dbo and your web will not run.

To resolve this issue you can follow the steps outlined below after which your web will run without any problems. As this procedure requires changes to the databse please be sure to have a backup of your database and website. Note: This procedure is for a SQL server 2005 database!

Step 1:
Open your web.config file and look for "owner". Change the owner from dbo to your database username.
Open your web.config file and look for "owner". Change the owner from dbo to your database username.

Step 2:
In Microsoft SQL Server management studio select all stored procedures that DO NOT have aspnet in their name, rightclick and select "script as create to new query editor window".
In Microsoft SQL Server management studio select all stored procedures that DO NOT have aspnet in their name, rightclick and select "script as create to new query editor window".

This will create a script for all the selected stored procedures.

Step 3:
Where it says "new owner" below you should change it for your database username!
Where it says "new owner" below you should change it for your database username!

• In the just created script search and replace "create procedure" with "alter procedure"
• Search and replace "create procedure" with "alter procedure" (Note! with 2 spaces!)
• Search and replace "[dbo]" with "[new owner]"
• Search and replace "dbo." with "new owner."
• Execute the script

Step 4:
In Microsoft SQL Server management studio select all stored views that DO NOT have aspnet in their name, rightclick and select "script as create to new query editor window".
In Microsoft SQL Server management studio select all stored views that DO NOT have aspnet in their name, rightclick and select "script as create to new query editor window".

Step 5:

• Search and replace "[dbo]" with "[new owner]"
• Search and replace "dbo." with "new owner."
• Search and replace "create view" with "alter view"
• Search and replace "new owner.GetListParentKey" width "dbo.GetListParentKey"
• Execute the script

Step 6:

• Go to "functions" "Scalar-valued functions"
• rightclick and select "script as create to new query editor window" for function "fn_GetVersion"
• Search and replace "dbo." with "new owner." (including the "."!)
• Execute script

Step 7:

Open a new query window and paste the following script:

ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Applications
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Profile
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Roles
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_SchemaVersions
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Users
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_UsersInRoles
ALTER SCHEMA dbo TRANSFER [USERNAME].vw_aspnet_Applications
ALTER SCHEMA dbo TRANSFER [USERNAME].vw_aspnet_MembershipUsers
ALTER SCHEMA dbo TRANSFER [USERNAME].vw_aspnet_Profiles
ALTER SCHEMA dbo TRANSFER [USERNAME].vw_aspnet_Roles
ALTER SCHEMA dbo TRANSFER [USERNAME].vw_aspnet_Users
ALTER SCHEMA dbo TRANSFER [USERNAME].vw_aspnet_UsersInRoles
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Applications_CreateApplication
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_UnRegisterSchemaVersion
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_CheckSchemaVersion
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Users_CreateUser
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Users_DeleteUser
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_AnyDataInTables
ALTER SCHEMA dbo TRANSFER
[USERNAME].aspnet_Membership_CreateUser
ALTER SCHEMA dbo TRANSFER
[USERNAME].aspnet_Membership_GetUserByName
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_GetUserByUserId

ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_GetUserByEmail
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_GetPasswordWithFormat

ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_UpdateUserInfo
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_GetPassword
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_SetPassword
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_ResetPassword
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_UnlockUser
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_UpdateUser
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_ChangePasswordQuestionAndAnswer

ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_GetAllUsers
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_GetNumberOfUsersOnline

ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_FindUsersByName
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Membership_FindUsersByEmail
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Profile_GetProperties
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Profile_SetProperties
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Profile_DeleteProfiles
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Profile_DeleteInactiveProfiles
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Profile_GetNumberOfInactiveProfiles

ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Profile_GetProfiles
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_UsersInRoles_IsUserInRole
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_UsersInRoles_GetRolesForUser
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Roles_CreateRole
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Roles_DeleteRole
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Roles_RoleExists
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_UsersInRoles_AddUsersToRoles

ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_UsersInRoles_RemoveUsersFromRolesALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_UsersInRoles_GetUsersInRoles
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_UsersInRoles_FindUsersInRole
ALTER SCHEMA dbo TRANSFER [USERNAME].aspnet_Roles_GetAllRoles
Grant execute on aspnet_Setup_RestorePermissions to [USERNAME]
Grant execute on aspnet_Setup_RemoveAllRoleMembers to [USERNAME]
Grant execute on aspnet_RegisterSchemaVersion to [USERNAME]
Grant execute on aspnet_Applications_CreateApplication to [USERNAME]
Grant execute on aspnet_UnRegisterSchemaVersion to [USERNAME]
Grant execute on aspnet_Users_CreateUser to [USERNAME]
Grant execute on aspnet_Users_DeleteUser to [USERNAME]
Grant execute on aspnet_AnyDataInTables to [USERNAME]
Grant execute on aspnet_Membership_CreateUser to [USERNAME]
Grant execute on aspnet_Membership_GetUserByName to [USERNAME]
Grant execute on aspnet_Membership_GetUserByUserId to [USERNAME]
Grant execute on aspnet_Membership_GetUserByEmail to [USERNAME]
Grant execute on aspnet_Membership_GetPasswordWithFormat to [USERNAME]
Grant execute on aspnet_Membership_UpdateUserInfo to [USERNAME]
Grant execute on aspnet_Membership_GetPassword to [USERNAME]
Grant execute on aspnet_Membership_SetPassword to [USERNAME]
Grant execute on aspnet_Membership_ResetPassword to [USERNAME]
Grant execute on aspnet_Membership_UnlockUser to [USERNAME]
Grant execute on aspnet_Membership_UpdateUser to [USERNAME]
Grant execute on aspnet_Membership_ChangePasswordQuestionAndAnswer to [USERNAME]

Grant execute on aspnet_Membership_GetAllUsers to [USERNAME]
Grant execute on aspnet_Membership_GetNumberOfUsersOnline to [USERNAME]
Grant execute on aspnet_Membership_FindUsersByName to [USERNAME]
Grant execute on aspnet_Membership_FindUsersByEmail to [USERNAME]
Grant execute on aspnet_Profile_GetProperties to [USERNAME]
Grant execute on aspnet_Profile_SetProperties to [USERNAME]
Grant execute on aspnet_Profile_DeleteProfiles to [USERNAME]
Grant execute on aspnet_Profile_DeleteInactiveProfiles to [USERNAME]
Grant execute on aspnet_Profile_GetNumberOfInactiveProfiles to [USERNAME]
Grant execute on aspnet_Profile_GetProfiles to [USERNAME]
Grant execute on aspnet_UsersInRoles_IsUserInRole to [USERNAME]
Grant execute on aspnet_UsersInRoles_GetRolesForUser to [USERNAME]
Grant execute on aspnet_Roles_CreateRole to [USERNAME]
Grant execute on aspnet_Roles_DeleteRole to [USERNAME]
Grant execute on aspnet_Roles_RoleExists to [USERNAME]
Grant execute on aspnet_UsersInRoles_AddUsersToRoles to [USERNAME]
Grant execute on aspnet_UsersInRoles_RemoveUsersFromRoles to [USERNAME]
Grant execute on aspnet_UsersInRoles_GetUsersInRoles to [USERNAME]
Grant execute on aspnet_UsersInRoles_FindUsersInRole to [USERNAME]
Grant execute on aspnet_Roles_GetAllRoles to [USERNAME]
Grant execute on aspnet_CheckSchemaVersion to [USERNAME]
Grant execute on GetListParentKey to [USERNAME]

Search and replace [USERNAME] for your database username and execute the script.

Step 8:
Refresh your database manager window and you should now see that all AspNet tables and storedprocedures belong to the dbo user/schema. Open your website in your browser. Your website should now load as normal.

DotNetNuke equips developers with some of the most robust and powerful frameworks; crucial for building effectual Web applications desirable for eCommerce in DotNetNuke. Once these prerequisite components, especially the templates for Visual Studio and the framework for source edition are effectively installed, the actual process of development for DotNetNuke (DNN) modules becomes exceedingly fast and repeatable, as well as ready for instant use.

Furthermore, no or very little cost is involved in development of eCommerce in DotNetNuke modules as the templates, express editions and framework of the Visual Studio are commonly available free of cost. All you actually need for your eCommerce in DotNetNuke is Visual Studio, either Express or some other licensed edition; DotNetNuke Starter Kit which is available on the website of DotNetNuke; SQL Server, again either Express or some other licensed edition; and a working installation of DotNetNuke for your eCommerce in DotNetNuke.

Building an Ecommerce in DotNetNuke Module
To start with, you will need to open the DotNetNuke website development copy in your Visual Studio. Then simply add a plain file to your eCommerce in DotNetNuke project by making use of a DotNetNuke Dynamic Module template, which comes fully installed with your DotNetNuke Starter Kit package. Open your web.config file to trace the compilation node. Then simply proceed to add a node titled codeSubDirectories under compilation. Add one more item under the codeSubDirectories by using name of your module entered by you in the last step, in the following format: <add directoryName="ModuleName"/>.

Now, go to the Solution Explorer and proceed by locating the DesktopModules directory. Here, you will find a fresh directory that has been created by Dynamic Module template, below your DesktopModules directory. Rename the directory with the same module name used by you in your previous steps. You must next log-in into the DotNetNuke website, opened previously by you in the Visual Studio, by using the facility of a host account provided for the purpose. Under the main menu of this host account, select the Module Definitions option, and then select the Create New Module option. Now, you will need to fill-up this module form by making use of the same module name used by you in the steps followed earlier.

After that is done, click on the Add Control of the form for Create New Module. From the drop-down list, click select on the file that has been added to it by Dynamic Module template. This file represents module name that was specified in your previous steps; only with the extension:.ascx added to it. You now need to open this.ascx file in the Visual Studio. It will display both a code-behind view and design created by the module template. You can add functionality to this code-behind file as deemed suitable to your eCommerce in DotNetNuke. Visual and layout elements may also be added to your design view, if desired. Before making an attempt to create the module, it is advisable to verify DotNetNuke portal installation functionality.

Have a robust, full-featured site deployed in no time with DotNetNuke, one of the world's most trusted content management systems (CMS). While most other CMS's offer limited functionality, DotNetNuke's (DNN) free community version provides even more functions, such as events content, announcements, discussions, FAQ's and various customizable forms. This simply means much more power-packed features and options to complement your aggressive business.

Choose DNN for your new website, be it a corporate intranet, extranet or online store. It is one of the longest-running web development platforms, and indeed one of the most popular in the web development community. It is based on Microsoft's own robust web development framework, ASP.Net, which is one of the reasons why DNN-based sites and applications are fully customizable, SEO-friendly, stable and scalable.

The DotNetNuke development edge
DNN is an open-source CMS. This entails a lot of key advantages for both developers and clients. Easy administration. Site administration is highly intuitive thanks to a user-friendly administrative interface. There is no technical programming knowledge required when managing your website. You can create, edit and publish content instantly and seamlessly.

Advanced features. A DNN page consists of modules, skins and other kinds of attachments. Many of them are packaged with the initial download. If what you need is not there, however, chances are one or more members of the online DotNetNuke development community has it. They may be downloadable for free or a minimal amount.

Features are constantly evolving thanks to this active online community.
Round-the-clock support. Although a core team of developers is always on hand to support users and programmers, there is an abundance of information and help references available through blogs, forums, online help, journals and other websites.

Fast development. DotNetNuke developers are able to finish projects in a short time due to the following reasons:

- The full application source code is open and accessible;

- Modules, applications and skins are readily available;

- Online support is always on hand, whether for technical assistance or looking for features.

Highly secure. Sites are safe and secure thanks to the validation, encryption and bug and potential threat tracking capabilities.

Completely customizable. To satisfy whatever need you may have, a DNN site is easily customizable on all levels, from font type, color, skin and modules. The best thing about it is that changes do not affect content at all.

DotNetNuke gets the job done affordably and in a short time You can liven up your online store or support your thriving business community through wide-access web portals built on this robust CMS. Contact a DotNetNuke developer today.

DNN or DotNetNuke web hosting is a type of an open sourced application of web framework that is used in building websites. The ability of DNN is going ahead of its capabilities of making websites but they focus mainly in developing and managing websites. Because it is an open source product, DNN products are free and distributed cost free on the internet. DNN developers do require to the users to give them credits by forming a link to the main website of Dot Net Nuke main website.

DNN could be used for creating different kinds of web layout without the user knowing much on scripting or coding. Since it has an open-source environment and able to attract huge numbers of devoted users that are pleased to answers to the questions of the new users.

DNN is not working with Linux Web-hosting settings because it is using the ASP coding for operation. As earlier said, there is no need of knowing the how to's in writing codes before you use DNN because the product is already ASP based. The ASP can function by the support of Window-based hosting providers. There is no need of installing the DNN to the local computers because it will be installed to the directory of the website.

The ways to install the Dot Net Nuke is depending to the policies of the hosting provider. There are some cases that the user is asked to install it by them, as others can be installed automatically through the control panel. There are also some cases that you need to email the hosting provider and request for their staff to perform the installation for you.

DNN or Dot Net Nuke is powerful and flexible process of making website and its default installation do includes larger numbers of features. The options to add hundreds of more are available through modules as well as updates hat are available in the net.

Here, I am using DotNetNuke 6.01.04 and Blog module 4.1.1. The DotNetNuke Blog set of modules provide blogging functionality for your DotNetNuke website. Different modules in the package provide a variety of function. The Blog package provides each of your authorized users with their own blog.

A blog is simply a set of posts grouped by author in order by date. Each blogger can have child blogs to divide that authors posts by subject. You can set up categories to organize posts by subject across authors. You can create tags for each post as another means of filtering the posts.

Open the DotNetNuke Blogs page, listed above, so you can refer back to it for reference.

I. Install the Blog Module
First download the DotNetNuke Blog module from the codeplex link listed above. You should back up your database and website code before installing a new module, so you can revert back if things go badly.
Add the Blog Module to your DotNetNuke installation.
On DNN 6, you install modules by going to Host, Extensions.

II. Create a Role for Bloggers
You will probably want to restrict who can blog on your website. Go to Admin, Security Roles and set up a new role, say Bloggers. Do not check Auto nor Public, as you will want to assign each blogger individually.

III. Create a Blog Page and Add the Blog Module
Create a new page to display your blogs. Add the Blog module to your page. I titled my module Blog. Blog adds several modules to your page, giving all of them the same title, so they are a little hard to tell apart. You need to configure each one. Each Blog module has settings you can use to configure the Blog. All the Blog modules have the regular Settings link that all DotNetNuke modules have. Some of the Blog modules have an extra tab with additional settings. A few Blog modules have additional functionality under module management at the top under Edit options. On DNN 6, you can see the Edit options by pointing your mouse at the Manage button overlaying each Blog title. You can get to each module's settings by pointing your mouse at the Manage button and finding the Settings link under Admin options. You can also get to Settings by clicking the gear symbol on the right edge of the module. From top to bottom, these are the nine modules Blog added to my page.

1. Main Blog Module
The first blog module has the bolg configuration options. This module also displays the blog entries. Keep this module at the top of the Content section of your page. This module has two places to change settings. The first is under Settings, where you can change the title for your Blog. On DotNetNuke.com, they title this module DNN Blog. To get to the main configure options, under Manage click Module Options. The top part of his module, which is only visible to administrators, lets you add any of the other eight modules to the page. Since the other eight modules are already on the page, we do not need to add any now. If we deleted some, this would be a way to add them back.

The eight blog module parts are:
1. Blog List
2. New Blog
3. Search Blog
4. Blog Archive
5. Recent Entries
6. Recent Comments
7. Blog Categories
8. Blog Tags

2. Blog List
The next module lists all the Blogs. Go into Settings and change the title. On DotNetNuke.com, they title this module DNN Bloggers. Since this is a list of Blogs, you will want to put this module on the side. Point your mouse at Manage, under Move click To Left Pane. Under Manage, Edit this module also has two functions, one to update the settings of your individual blog and one for you to add an post to your blog. We have not created your blog yet, so these are not of any use right now.

3. New Blog
This module lets you create your blog. Under Settings change the title to My Blog. You want to restrict this module to Bloggers. Under Settings, Permissions, uncheck Inherit View permissions from Page. Next to Bloggers check both View Module and Edit Module. Under Manage, under Move, move this module to the left pane. If you are going to be one of the Bloggers, go ahead and click Create My Blog. Fill out the information about your blog as you feel appropriate.

4. Search Blog
The Search Blog module lets you search the blog posts, surprise. Change the title of the module. On DotNetNuke.com they use the title Search DNN Blogs. Move this module to the left pane, your choice as to where to position the blog. You can use the DotNetNuke Blogs page as a model.

5. Blog Archive
The next module is the Blog Archive, which is organized by date, which I find completely useless, but the calendar looks cool. Change the title, DotNetNuke.com uses Archive. Move to the left pane.

6. Recent Entries
The next module lists the title of Recent Blog Entries. Change the title to something like Recent Blog Entries. Leave this module where it is, or move to the top of the page or to the left pane. Under Settings there is an extra tab Recent Blog Entries Settings, which lets you configure how to display the entries. You can show the whole post, if you like. Point your mouse at the blue ? box to get a list of the control variables you can use. Here is how I configure mine.

<div class="Blog_RecentEntries">
<a href="/Blogs/tabid/281/BlogID/[BLOGID]/Default.aspx">[USERFULLNAME]</a>:
<a href="[PERMALINK]" class="Blog_RecentEntries_Title">[TITLE]</a>
-
<span class="Blog_RecentEntries_Dateline"> [ADDEDDATE]</span>
</div>

This displays the author, title and date. The author links to the author's blog. If you use this code, you will need to change the tabid to whatever tabid your blog page is on.

7. Recent Comments
This is similar to the Recent Entries module. You should know enough now to decide for yourself what you want to do with this module. I changed the titel and left the rest as is.

8. Blog Categories and Blog Tags
Their use is self explanatory. Change the titels and move both of these to the left pane.