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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Starter Kit running problemStarter Kit running problem
Previous
 
Next
New Post
12/1/2006 11:01 PM
 

Due to the changes in DNN 4.3.7 there is no longer a need to add the key to the web.config. The updated tutorial is at:

Setting-up the Environment (without IIS)



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
12/2/2006 4:59 AM
 
nice one. what's also new?
 
New Post
12/9/2006 2:48 PM
 

michael,

i tested it today with dnn 4.3.7 ... yes, the line is no longer needed ... but there is still a porblem.
just follow your tutorial and than great a child portal and try to work in it. or just use the link module (add link). you will see, that the portnumber is lost in the url.

 
New Post
12/9/2006 6:31 PM
 
bbhermann wrote

michael,

i tested it today with dnn 4.3.7 ... yes, the line is no longer needed ... but there is still a problem.
just follow your tutorial and than great a child portal and try to work in it. or just use the link module (add link). you will see, that the portnumber is lost in the url.

I would suggest using my previous step of turning off dynamic ports and setting it to port 80. That should fix it.

Using the built in web server has it's limitations and while I do code mostly using Visual Web Developer Express, I use this set-up: Setting-up the Environment (using IIS)



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
12/9/2006 9:19 PM
 
AdefWebserver wrote

 

I would suggest using my previous step of turning off dynamic ports and setting it to port 80. That should fix it.

Yes, that's what i did. Just wanted to let you know.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Starter Kit running problemStarter Kit running problem


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