I have SBS2003 premium R2
It is running a sharepoint site that is installed "out of the box" that we
have begun to work with. I am attempting to install a DotNetNuke website on
the server also. The share point server is using ASP 1.x and the DNN site is
using ASP2.0.
Shouldn't I be able to run both of these at the same time?
If Yes what am I missing because it seems to run 1 or the other based on the
asp settings being set to 1 or 2.
We would like to be able to navigate at any point even the same time from
diffeernt browsers in house to :
http://companyweb/default.aspx
or
http://DNNweb/default.aspx.

[quoted text, click to view]

It is possible to run ASP.Net 1.x and ASP.Net 2.0 "side-by-side" on
IIS6 within SBS2003.

I recommend you search for how to do "side-by-side" installations of
ASP.Net.

The basic idea is to:
1. Install both ASP.Net 1.1 and ASP.Net 2.0
2. Create one IIS6 Application Pool to run ASP.Net 1.1 applications
and another Application Pool for ASP.Net 2.0 applications
3. Assign the ASP.Net 1.1 application to the ASP.Net 1.1 application
and ASP.Net 2.0 application to ASP.Net 2.0 application pool
4. Configure the ASP.Net 1.1 application to use ASP.Net v1.1 and
ASP.Net 2.0 application to use ASP.Net v2.0. This translates into the
right version of scriptmaps to be configured at the application's
metabase node.

Of course, there are details involved with the general idea, and
misconfiguring at any step can lead to bizarre failures -- you may be
running applications on SBS2003 that may not work side-by-side.

The most common user misunderstanding is that you can only run
one .Net version within a single process. This is why the UI only
changes versions globally - because there is no safe way to change
versions per-application. And if you want to do this, you have to
control which ASP.Net version runs in which process -- that is why you
create different Application Pools, assign different application pools
to applications, then configure different version of scriptmaps per
application such that everything is aligned. Any misalignment can
cause multiple .Net versions in the same process and bizarre failure
can occur.

I'm just trying to say that it is technically possible, but whether it
is actually possible in your current configuration, few can promise.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//