*this is also posted at the dotnetnuke forums but thought a wider audience would be better*
Hello,
I have dnn 3.3 (the june 20th release version) which I used to upgrade my old 3.13 dnn portal. The portal is in the root of wwwroot folder. Everything is working wonderful except for one thing. I created a web app in visual studio 2005 pro and then migrated
to the server which is running dnn 3.3. I went to IIS and after making virtual directory for the vs studio 2005 web app, I went to the ASP.NET tab and selected the 2.0.xxx framework for this web app. So I have IIS configured properly and everything in the
portal is working fine.
Now when I go to www.yourportalname/website1/default.aspx I get redirected to the portal main page. When I first created this ASP 2 web app and tried to run it under DNN 3.13, I recieved the dreaded app_globalResources map path error. I then went and researched
that bug and people were posting about filemon/regmon from sysinternals led them to give ASP.NET worker process to some crypto folder where machinekeys are stored. I did that and the app_globalResources error disappeared but now I am being redirected to the
main portal page anytime I try to access a ASP 2 web app under dnn.
I have also added the dotnetnuke dll and other dll to the ASP 2 web apps bin folder. The file siteUrls.config is also in the ASP 2 web app directory. I did some research and some suggested turning off friendly urls under host settings and well this did not
work either.
I really need to be able to run ASP 2 web apps underneath DNN 3.3 (uses asp 1.1). If you could help with this matter, then I would be most appreciative.
Running different web apps under the DNN app would be possible if you make sure you clear any http modules in the sub-apps web.config.
What is happening is DNN's UrlRewiter HTTP Module is picking up your request and trying to send it to the DNN portal based on the alias you are requesting.
Thanks for the quick reply. However, I opened the sub-app and there isnt any listing for http modules. Here is copy/paste of the sub apps web.config. It is a visual studio 2005 asp.net website web.config. The only thing omitted was the <connectionStrings>
section.
<begin copy>
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
<appSettings/>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
Visual Basic options:
Set strict="true" to disallow all data type conversions
where data loss can occur.
Set explicit="true" to force declaration of all variables.
-->
<compilation debug="false" strict="false" explicit="true" />
<pages>
<namespaces>
<clear />
<add namespace="System" />
<add namespace="System.Collections" />
<add namespace="System.Collections.Specialized" />
<add namespace="System.Configuration" />
<add namespace="System.Text" />
<add namespace="System.Text.RegularExpressions" />
<add namespace="System.Web" />
<add namespace="System.Web.Caching" />
<add namespace="System.Web.SessionState" />
<add namespace="System.Web.Security" />
<add namespace="System.Web.Profile" />
<add namespace="System.Web.UI" />
<add namespace="System.Web.UI.WebControls" />
<add namespace="System.Web.UI.WebControls.WebParts" />
<add namespace="System.Web.UI.HtmlControls" />
</namespaces>
</pages>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows" />
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
If you clear the httpmodules from the root web.config the site does not work. Could you offer some more information as to how to solve this problem. It does not seem to be as clear cut as you indicate it.
Hmm, after reading your scenario more carefully I see that you are running the new ASP.Net 2.0 site as a virtual directory under an ASP.Net 1.1 DNN install.
This should work, but maybe there is an issue there. I'll have to try it out and get back to you.
zuf
Member
95 Points
19 Posts
asp 2 website not working under dnn 3.3 (asp 1.1) root
Jun 23, 2006 03:57 PM|LINK
Hello,
I have dnn 3.3 (the june 20th release version) which I used to upgrade my old 3.13 dnn portal. The portal is in the root of wwwroot folder. Everything is working wonderful except for one thing. I created a web app in visual studio 2005 pro and then migrated to the server which is running dnn 3.3. I went to IIS and after making virtual directory for the vs studio 2005 web app, I went to the ASP.NET tab and selected the 2.0.xxx framework for this web app. So I have IIS configured properly and everything in the portal is working fine.
Now when I go to www.yourportalname/website1/default.aspx I get redirected to the portal main page. When I first created this ASP 2 web app and tried to run it under DNN 3.13, I recieved the dreaded app_globalResources map path error. I then went and researched that bug and people were posting about filemon/regmon from sysinternals led them to give ASP.NET worker process to some crypto folder where machinekeys are stored. I did that and the app_globalResources error disappeared but now I am being redirected to the main portal page anytime I try to access a ASP 2 web app under dnn.
I have also added the dotnetnuke dll and other dll to the ASP 2 web apps bin folder. The file siteUrls.config is also in the ASP 2 web app directory. I did some research and some suggested turning off friendly urls under host settings and well this did not work either.
I really need to be able to run ASP 2 web apps underneath DNN 3.3 (uses asp 1.1). If you could help with this matter, then I would be most appreciative.
cheers
~Zuf
J7Mitch
Star
13145 Points
2632 Posts
Re: asp 2 website not working under dnn 3.3 (asp 1.1) root
Jun 23, 2006 07:49 PM|LINK
Running different web apps under the DNN app would be possible if you make sure you clear any http modules in the sub-apps web.config.
What is happening is DNN's UrlRewiter HTTP Module is picking up your request and trying to send it to the DNN portal based on the alias you are requesting.
zuf
Member
95 Points
19 Posts
Re: asp 2 website not working under dnn 3.3 (asp 1.1) root
Jun 23, 2006 08:07 PM|LINK
Thanks for the quick reply. However, I opened the sub-app and there isnt any listing for http modules. Here is copy/paste of the sub apps web.config. It is a visual studio 2005 asp.net website web.config. The only thing omitted was the <connectionStrings> section.
<begin copy>
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
<appSettings/>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
Visual Basic options:
Set strict="true" to disallow all data type conversions
where data loss can occur.
Set explicit="true" to force declaration of all variables.
-->
<compilation debug="false" strict="false" explicit="true" />
<pages>
<namespaces>
<clear />
<add namespace="System" />
<add namespace="System.Collections" />
<add namespace="System.Collections.Specialized" />
<add namespace="System.Configuration" />
<add namespace="System.Text" />
<add namespace="System.Text.RegularExpressions" />
<add namespace="System.Web" />
<add namespace="System.Web.Caching" />
<add namespace="System.Web.SessionState" />
<add namespace="System.Web.Security" />
<add namespace="System.Web.Profile" />
<add namespace="System.Web.UI" />
<add namespace="System.Web.UI.WebControls" />
<add namespace="System.Web.UI.WebControls.WebParts" />
<add namespace="System.Web.UI.HtmlControls" />
</namespaces>
</pages>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows" />
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
</system.web>
</configuration>
<end copy>
My IIS directory looks like this
--DNN portal
--sub app which is a ASP 2.0 website.
Any more ideas of how to get this to work under dnn 3.3 which runs asp 1.1 and the sub app runs asp 2?? I am appreciative of the help.
cheers
~Zuf
J7Mitch
Star
13145 Points
2632 Posts
Re: asp 2 website not working under dnn 3.3 (asp 1.1) root
Jun 23, 2006 08:43 PM|LINK
That is the problem.
You have to either explicitly clear all the parent httpmodules, or remove specfic ones:
http://msdn2.microsoft.com/en-us/9b9dh535.aspx
zuf
Member
95 Points
19 Posts
Re: asp 2 website not working under dnn 3.3 (asp 1.1) root
Jun 23, 2006 09:39 PM|LINK
when you say clear, can you provide some more instructions plz. Do you mean machine.config under framework 2.0 or the DNN web.config ??
~Zuf
zuf
Member
95 Points
19 Posts
Re: asp 2 website not working under dnn 3.3 (asp 1.1) root
Jun 26, 2006 02:37 PM|LINK
If you clear the httpmodules from the root web.config the site does not work. Could you offer some more information as to how to solve this problem. It does not seem to be as clear cut as you indicate it.
cheers
~Zuf
J7Mitch
Star
13145 Points
2632 Posts
Re: asp 2 website not working under dnn 3.3 (asp 1.1) root
Jun 26, 2006 02:48 PM|LINK
Hmm, after reading your scenario more carefully I see that you are running the new ASP.Net 2.0 site as a virtual directory under an ASP.Net 1.1 DNN install.
This should work, but maybe there is an issue there. I'll have to try it out and get back to you.
zuf
Member
95 Points
19 Posts
Re: asp 2 website not working under dnn 3.3 (asp 1.1) root
Jun 28, 2006 04:00 PM|LINK
Any news?
cheers
~Zuf
zuf
Member
95 Points
19 Posts
Re: asp 2 website not working under dnn 3.3 (asp 1.1) root
Jul 06, 2006 03:14 PM|LINK
Hoping J7Mitch has had time to find out the if this works?
cheers
~Zuf
zuf
Member
95 Points
19 Posts
Re: asp 2 website not working under dnn 3.3 (asp 1.1) root
Jul 17, 2006 04:28 PM|LINK
cheers
~Zuf