DotNetNuke Hosting with ASPHostPortal.com

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

DotNetNuke Hosting with ASPHostPortal.com :: Integration of WSDL to DNN Modules

clock December 19, 2014 05:55 by author Ben

I had been functioning with DNN for a long time, Believed this weblog could help other DNN develops. There are two approaches to Contain WSDL files into a DNN module. Service Reference and Web Reference.
Right here I will discussing about Web References.

So to Contain them into DNN initial Correct Click On References within your Project Solution
References -> Add Service Reference -> Advanced(Left bottom Corner) -> Add Web Reference.

Paste your WSDL link towards the URL

Once you hit Add Reference button, Visual Studio will update the Web.config at the Module level.
But need to delete the Module Level Config files.
But Dont forget to take a backup of it, If anything goes wrong

And Set few parameters at Site level web.config file



Remember If you Creating DNN module package and your module uses any kind of SOAP services.
You ought to add parameters to Target Site’s Config file otherwise the site may not work.

Happy Coding



DotNetNuke Hosting with ASPHostPortal.com :: Security Actions to Safeguard Your DotNetNuke CMS

clock December 18, 2014 05:46 by author Ben

DNN Security Out Of the Box
DNN (DotNetNuke) is currently the premier CMS of the US Government as a result of it's robust security and integration with current safety functions. Nevertheless even DNN is not totally excellent out of the box, and there are numerous additional safety attributes that can be put in location depending on your particular DNN eCommerce requirements. These security suggestions variety from easy to complex and cover many various aspects of possible security risks. No guide can accurately assess your particular safety requirements. In the event you would prefer to adequately secure your DNN web site, contact Clarity these days.

Improve Password Complexity and Use Specifications

Increasing password complexity is among the easiest and most successful methods to significantly boost security. Probably the most common and successful requirements are length and complexity. eight or much more characters along with a minimum of a single capital letter, one lowercase letter and 1 number is a good begin. You are able to contemplate requiring a non-alphanumeric character as well as putting restrictions on how lengthy a password may be used. Even with powerful password needs, you might be only preventing against brute force attacks.

Modify 'Host' and 'Admin' Passwords and Limit Their Use

Altering the Host and Admin password to incredibly complicated passwords is the single most successful step for safety, as each accounts are recognized to exist and are the most vulnerable to brute force attacks as a result of that. Make sure that any password you set for these accounts exceeds the password recommendations listed above. You should also think about limiting access to these accounts, as they may be essentially the most powerful accounts and would leave your site essentially the most vulnerable if they have been compromised.

Hash Password Storage

By default DotNetNuke utilizes encryption of user passwords. This provides a good degree of protection, and enables you to retrieve your password as encryption is a reversible operation. Nonetheless, should you usually do not want to help password retrieval, or want to make certain maximum protection, you may select to utilize Hashing as an alternative. Hashing is really a non-reversible operation, so even if your database is accessed or stolen, a hacker can't reverse engineer your password.

 



DotNetNuke Hosting - ASPHostPortal :: Creating Custom Roles and Assign Custom Role To User

clock August 20, 2013 05:50 by author Mike

DotNetNuke (DNN) is a web application Open Source Platform and has grown in popularity over the years because it does a very good job of solving the problem of basic web solution. In this article, I am going to explain how we can create custom role and assign roles to the user.

Using "Roles" is one of the greatest features in DotNetNuke (DNN). Based on that, we can give rights to user to view pages, View Modules, access menus, etc. Roles can be customizable. We can restrict a user to view some page or some part of a Page based on the role only. Let's see how we can assign a role to a newly created user.

1.  Click on Edit (Pencil) icon for that user to whom we want to add a Role. Let's say I clicked on Edit icon of user "Abhijit Jana".


2. Click on "Manage Roles for this User" Link. This will redirect you to Create and Assign Role Page.


Here we can select the Roles for user. One user can have multiple Roles. We can give theeffective and Expiry date for roles too. Just Select Role from "Security Role" Dropdown and Select date if needed then click on the "Add Role to User" Link. This means selected role is now given to that user. We can also remove the added role in a similar way by clicking on Delete (Cross) Icon.

Creating new roles are very simple. Follow steps bellow:

1. From Admin Menu Clicks on "Security Roles" Link. This will open a new page with the list of all existing Roles.


2. Click on Down Arrow Icon with Security Roles (Lock Icon), and select "Add New Role" as shown in the picture given below, I am going to create a new Role:


3. Here we need to give the Role Name and Description with other details. Then we need to click on the Update button to save the Role:


5. On update, "Sales Team" roles will be added with the list of Roles. We can use the Edit (Pencil) Icon to Edit the Role.



I have already discussed how to assign a role to a user. We need to flow the same steps. Below are the sample screen shots where I am assigning the newly created "Sales Team" Role to a user.


Hope it will be helpful for those who are starting with DNN.



DotNetNuke Hosting :: Create Captcha Code in DNN Form

clock June 28, 2013 08:50 by author Ben

DotNetNuke is an open-source content management system ideal for creating and deploying projects such as commercial websites, corporate intranets and extranets, and online publishing portals. DotNetNuke is built on a Microsoft ASP.NET (VB.NET) platform, and is easily installed and hosted with all of our Windows Hosting Plans. Many things can be done by DNN, one of them to make a captcha code to protect from spam.

This is tips to guide you make a captcha code with DNN :

First important requirement is you have to add the DNN Framework control at the top code of your form.

Write the code in the user control form :



This is the quick screenshot on how the html code will looks like.

Now lets have a look at the back end code. If you see carefully, the ctlCaptcha.IsValid determines if a captcha code has been entered correctly by user or not.

The list of captcha code properties that you need to know:

  • CaptchaWidth: The width of the captcha control.
  • CaptchaHeight: The height of the captcha control.
  • CaptchaLength: The length of the characters inside the captcha control.
  • CaptchaChars: The characters that will be used in the captcha control, dont use this attribute if you want to use random characters.
  • Text: This will be the Text Introduction to notify the user to enter the captcha code.
  • Text: This will be the Text Introduction to notify the user to enter the captcha code.
  • ErrorMessage: This will be the error message when a captcha code is entered wrong. Note: you can overwrite the error message in behind code as well.


Dotnetnuke Hosting :: Step to Step to Restore Your Dotnetnuke Database With Dbo Schema to Non Dbo Environment

clock June 20, 2013 08:36 by author Ben

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 Hosting :: How to Build CatalookDotnetStore Modules for Ecommerce in DotNetNuke

clock June 7, 2013 10:28 by author Ben

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.



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