Last post Feb 22, 2006 06:51 AM by yogs
Feb 24, 2005 01:11 AM|erikol|LINK
Feb 24, 2005 01:36 AM|walkerstewart|LINK
Feb 24, 2005 02:43 AM|cniknet|LINK
Mar 05, 2005 10:36 AMemail@example.com|LINK
Mar 05, 2005 11:26 AM|cniknet|LINK
Mar 05, 2005 11:31 AMfirstname.lastname@example.org|LINK
Mar 05, 2005 11:38 AM|cniknet|LINK
Mar 05, 2005 11:50 AMemail@example.com|LINK
Mar 05, 2005 12:11 PM|cniknet|LINK
Mar 05, 2005 12:24 PMfirstname.lastname@example.org|LINK
Apr 27, 2005 03:16 PM|jrblack10|LINK
I am glad to stumble upon this discussion, but saddened to see that there is not resolution posted for this problem. If you have come up with a resolution for this, please share it. Thank You.
Apr 27, 2005 04:59 PM|cniknet|LINK
What are you seeking a resolution for? Running a child app in DNN is pretty straightforward and as discussed in this thread, if the config is done correctly, it works flawlessly.
Apr 27, 2005 05:00 PMemail@example.com|LINK
Apr 27, 2005 05:18 PMfirstname.lastname@example.org|LINK
My last post wasnt 100 correct. Its not the web.config file. I followed the directions above and got it to the point that it threw the user error in the child app as I mentioned above "argument is out of valid values for username". So my hunch is it has
something to do with the cookie being passed and I'm not technical enough to figure it out.
Apr 27, 2005 05:23 PM|cniknet|LINK
There is nothing in DNN that prevents it from running in the root...just about every DNN portal I have is setup in the root. It has to be something specific to your installation, but without all the details it's not possible to troubleshoot.
Apr 27, 2005 05:44 PMemail@example.com|LINK
You are correct, DNN runs in the root directory just fine. What I was saying is, running DNN in the root and another app in a sub directroy poses a problem with passing cookies in forms. When I try to integrate the cookies to provide single sign on, the
sub app (if you will) has a problem with the cookie for some reason or another and wont recognize the username field.
May 02, 2005 01:34 PM|jrblack10|LINK
Ed and Nik,
Thank you so much for the updated and more detailed information. Seems the problem was that I was running DNN in the root of the web and tried to run another .NET app in a sub folder. Once I moved both DNN and the other .NET app (Issue Tracker) to sub-folders
of the root web, all worked fine. Thank you again.
May 03, 2005 06:29 PMfirstname.lastname@example.org|LINK
The problem with this solution is I cant use DNN as the opening page to my website.
So I wouldnt call this a closed issue, just a work around that isnt that good.
Feb 22, 2006 06:51 AM|yogs|LINK
I know this thread is from a while ago, but I used it to get my child app working and the suggestions here worked... well to some extent. My child app is an .Net Framework 2.0 application and my DNN is 3.2.2 which runs in Framework 1.1. So, my child app
is erroring when loading with a standard:
Could not load type 'MyNet2App.2App'
So for anyone looking to run a 2.0 app as a child directory, I finally found the solution. Follow the instructions in this thread first. These DLLs need to be copied from your DNN bin directory to your child apps bin directory:
Then in IIS go to the virtual directory's properties and click on the ASP.Net tab. Change the .Net Framework version from 1.1 to 2.0. Click save. Amazingly enough your application should work. I was supprised that it worked because I was half expecting
the DNN DLLs to load in 2.0 and error on me.
Hope that helps anyone with a simular issue.