By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,422 Members | 1,615 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,422 IT Pros & Developers. It's quick & easy.

Website set as application?

P: n/a
I'm trying to get an existing VS.NET project up on my Win2003 server and I
get the following error (on the actual website page):

"It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This error
can be caused by a virtual directory not being configured as an application
in IIS."

I've been told by the previous developer that the website needs to be set as
a "application". I assume this means what process it runs under? I've created
a virtual directory to the location and the site can be seen. but I get that
error listed above?
The application pools are:

DEFAULTAPPPOOL (default)
MSSHAREPOINTAPPPOOL
What does this developer mean? Thanx.

Nov 19 '05 #1
Share this Question
Share on Google+
21 Replies


P: n/a
To create an Application using a Virtual Directory
as its starting point, open the IIS Manager, scroll
down to the virtual directory, select it, and rght-click it.

From the pop-up menu, select "Properties".

Then, click on the "Create" button.
That will make your virtual directory an Application.

If you do that, your error message should disappear.
Please let us know how you do.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
I'm trying to get an existing VS.NET project up on my Win2003 server and I
get the following error (on the actual website page):

"It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This
error
can be caused by a virtual directory not being configured as an
application
in IIS."

I've been told by the previous developer that the website needs to be set
as
a "application". I assume this means what process it runs under? I've
created
a virtual directory to the location and the site can be seen. but I get
that
error listed above?
The application pools are:

DEFAULTAPPPOOL (default)
MSSHAREPOINTAPPPOOL
What does this developer mean? Thanx.


Nov 19 '05 #2

P: n/a
No, it does not, the page error is this:

"Server Error in '/' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This error
can be caused by a virtual directory not being configured as an application
in IIS.

Source Error:
Line 48: Using Form authentication and the users=? means to deny anonymous
users
Line 49: -->
Line 50: <authentication mode="Forms">
Line 51: <forms name="TecTrackAuth" loginUrl="default.htm"
protection="All" path="/" />
Line 52: </authentication>
"

"Juan T. Llibre" wrote:
To create an Application using a Virtual Directory
as its starting point, open the IIS Manager, scroll
down to the virtual directory, select it, and rght-click it.

From the pop-up menu, select "Properties".

Then, click on the "Create" button.
That will make your virtual directory an Application.

If you do that, your error message should disappear.
Please let us know how you do.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
I'm trying to get an existing VS.NET project up on my Win2003 server and I
get the following error (on the actual website page):

"It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This
error
can be caused by a virtual directory not being configured as an
application
in IIS."

I've been told by the previous developer that the website needs to be set
as
a "application". I assume this means what process it runs under? I've
created
a virtual directory to the location and the site can be seen. but I get
that
error listed above?
The application pools are:

DEFAULTAPPPOOL (default)
MSSHAREPOINTAPPPOOL
What does this developer mean? Thanx.


Nov 19 '05 #3

P: n/a
The standard format is :

<forms name=".ASPXAUTH" loginUrl="MyLoginForm.aspx" />

..HTM files are not processed by ASP.NET

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:84**********************************@microsof t.com...
No, it does not, the page error is this:

"Server Error in '/' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration
file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This
error
can be caused by a virtual directory not being configured as an
application
in IIS.

Source Error:
Line 48: Using Form authentication and the users=? means to deny anonymous
users
Line 49: -->
Line 50: <authentication mode="Forms">
Line 51: <forms name="TecTrackAuth" loginUrl="default.htm"
protection="All" path="/" />
Line 52: </authentication>
"

"Juan T. Llibre" wrote:
To create an Application using a Virtual Directory
as its starting point, open the IIS Manager, scroll
down to the virtual directory, select it, and rght-click it.

From the pop-up menu, select "Properties".

Then, click on the "Create" button.
That will make your virtual directory an Application.

If you do that, your error message should disappear.
Please let us know how you do.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
> I'm trying to get an existing VS.NET project up on my Win2003 server
> and I
> get the following error (on the actual website page):
>
> "It is an error to use a section registered as
> allowDefinition='MachineToApplication' beyond application level. This
> error
> can be caused by a virtual directory not being configured as an
> application
> in IIS."
>
> I've been told by the previous developer that the website needs to be
> set
> as
> a "application". I assume this means what process it runs under? I've
> created
> a virtual directory to the location and the site can be seen. but I get
> that
> error listed above?
> The application pools are:
>
> DEFAULTAPPPOOL (default)
> MSSHAREPOINTAPPPOOL
>
>
> What does this developer mean? Thanx.
>


Nov 19 '05 #4

P: n/a
this page 'default.htm' is where the prevoius developer created a frames
page. One of the frames is the .aspx page that control login.

<frameset framespacing="0" border="1" rows="135,*,35" frameborder="0">
<frame name="header" scrolling="no" noresize target="header"
src="main\frame_top.htm" marginwidth="0" marginheight="0">
<frameset framespacing="0" border="1" cols="200,*" frameborder="0">
<frame name="main_nav" scrolling="no" target="main_nav"
src="main\frame_nav.aspx" marginwidth="0" marginheight="0">
<frame name="main_body" scrolling="yes" target="main_body"
src="main\frame_home.htm" marginwidth="0" marginheight="0">
</frameset>
<frame name="footer" scrolling="no" noresize target="footer"
src="main\frame_bottom.htm" marginwidth="0" marginheight="0">

Any ideas? Thanx for your help.

"Juan T. Llibre" wrote:
The standard format is :

<forms name=".ASPXAUTH" loginUrl="MyLoginForm.aspx" />

..HTM files are not processed by ASP.NET

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:84**********************************@microsof t.com...
No, it does not, the page error is this:

"Server Error in '/' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration
file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This
error
can be caused by a virtual directory not being configured as an
application
in IIS.

Source Error:
Line 48: Using Form authentication and the users=? means to deny anonymous
users
Line 49: -->
Line 50: <authentication mode="Forms">
Line 51: <forms name="TecTrackAuth" loginUrl="default.htm"
protection="All" path="/" />
Line 52: </authentication>
"

"Juan T. Llibre" wrote:
To create an Application using a Virtual Directory
as its starting point, open the IIS Manager, scroll
down to the virtual directory, select it, and rght-click it.

From the pop-up menu, select "Properties".

Then, click on the "Create" button.
That will make your virtual directory an Application.

If you do that, your error message should disappear.
Please let us know how you do.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
> I'm trying to get an existing VS.NET project up on my Win2003 server
> and I
> get the following error (on the actual website page):
>
> "It is an error to use a section registered as
> allowDefinition='MachineToApplication' beyond application level. This
> error
> can be caused by a virtual directory not being configured as an
> application
> in IIS."
>
> I've been told by the previous developer that the website needs to be
> set
> as
> a "application". I assume this means what process it runs under? I've
> created
> a virtual directory to the location and the site can be seen. but I get
> that
> error listed above?
> The application pools are:
>
> DEFAULTAPPPOOL (default)
> MSSHAREPOINTAPPPOOL
>
>
> What does this developer mean? Thanx.
>


Nov 19 '05 #5

P: n/a
I'm not sure if this is the issue; they're running this app on a Window 2K
box and I'mnot sure but the VS.NET project file has reference to Framework
1.0, see below:

<Reference Name = "System.Web.Services"
AssemblyName = "System.Web.Services"
HintPath =
"..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll" />

My Win2003 server only has accepted to run v1.1, is that the issue? If so,
do I need to install v1.0? I moved the folder over to my server for the
framework.

Thanx.

"Juan T. Llibre" wrote:
To create an Application using a Virtual Directory
as its starting point, open the IIS Manager, scroll
down to the virtual directory, select it, and rght-click it.

From the pop-up menu, select "Properties".

Then, click on the "Create" button.
That will make your virtual directory an Application.

If you do that, your error message should disappear.
Please let us know how you do.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
I'm trying to get an existing VS.NET project up on my Win2003 server and I
get the following error (on the actual website page):

"It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This
error
can be caused by a virtual directory not being configured as an
application
in IIS."

I've been told by the previous developer that the website needs to be set
as
a "application". I assume this means what process it runs under? I've
created
a virtual directory to the location and the site can be seen. but I get
that
error listed above?
The application pools are:

DEFAULTAPPPOOL (default)
MSSHAREPOINTAPPPOOL
What does this developer mean? Thanx.


Nov 19 '05 #6

P: n/a
Hmmm...that is a problem.

If you take a look at
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config

you'll see that the references to v1.1.4322's
System.Web.Services are completely different.

I'm not even sure that you can *run*
..Net Framework v1.0.3705 in W2K3.

Windows Server 2003 is the first OS which runs
the .Net Framework 1.1.4322 "out of the box".

It doesn't even come with the
..Net Framework v1.0.3705 installed.

You could try to register the .Net Framework v1.0.3705,
if you copied the whole directory structure from the W2K box,
by running aspnet_regiis -i from the
drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
quite frankly, this might screw up your system.

It's bound to be quite a complicated, and risky, task
to run a deprecated version of the .Net Framework
in an OS which doesn't even come with it, but comes
with a later version.

About the best thing I'd recommend is that VS.NET 2003
be installed in the *original* W2K box, and then that the
application be recompiled and debugged for the .Net 1.1 Framework.

Then, you could copy the *Application*
to your W2K3 box and run it under .Net 1.1.

best regards,


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:AD**********************************@microsof t.com...
I'm not sure if this is the issue; they're running this app on a Window 2K
box and I'mnot sure but the VS.NET project file has reference to Framework
1.0, see below:

<Reference Name = "System.Web.Services"
AssemblyName = "System.Web.Services"
HintPath =
"..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
/>

My Win2003 server only has accepted to run v1.1, is that the issue? If so,
do I need to install v1.0? I moved the folder over to my server for the
framework.

Thanx.

"Juan T. Llibre" wrote:
To create an Application using a Virtual Directory
as its starting point, open the IIS Manager, scroll
down to the virtual directory, select it, and rght-click it.

From the pop-up menu, select "Properties".

Then, click on the "Create" button.
That will make your virtual directory an Application.

If you do that, your error message should disappear.
Please let us know how you do.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
> I'm trying to get an existing VS.NET project up on my Win2003 server
> and I
> get the following error (on the actual website page):
>
> "It is an error to use a section registered as
> allowDefinition='MachineToApplication' beyond application level. This
> error
> can be caused by a virtual directory not being configured as an
> application
> in IIS."
>
> I've been told by the previous developer that the website needs to be
> set
> as
> a "application". I assume this means what process it runs under? I've
> created
> a virtual directory to the location and the site can be seen. but I get
> that
> error listed above?
> The application pools are:
>
> DEFAULTAPPPOOL (default)
> MSSHAREPOINTAPPPOOL
>
>
> What does this developer mean? Thanx.


Nov 19 '05 #7

P: n/a
Thanx for all your help, you should know right.
I went ahead and downloaded the Framework 1.0 redistributable (and SP3) and
installed it on my Win 2003 server. But I'm not sure if I was supposed to do
that becuase I don't see it in IIS? The area for Application Pools doesn't
even see it, and if I try to add it by locating the asp.net file in the 1.0
directory it makes it available but it doesn't know for what????
How do others run websites on Win2003 with older Framework code? Are they
all required to stay on Win2K?
I thought that developers were still using 1.0 and 1.1 together on their
development projects (thought I saw an article on the need to develop in
both, switching back and forth).
And the developer states, not sure if true or not, that he runs this on his
Win2003 Server. How? He's been less than helpful to me, the old story of
seeing another developer as a threat.

Another question, if I look at the VS.NET project file I see that all the
ref's are to 1.0, is there an easier way to determine what framework an app
was written under, maybe in VS.NET???

Thanx!!!!!!!

"Juan T. Llibre" wrote:
Hmmm...that is a problem.

If you take a look at
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config

you'll see that the references to v1.1.4322's
System.Web.Services are completely different.

I'm not even sure that you can *run*
..Net Framework v1.0.3705 in W2K3.

Windows Server 2003 is the first OS which runs
the .Net Framework 1.1.4322 "out of the box".

It doesn't even come with the
..Net Framework v1.0.3705 installed.

You could try to register the .Net Framework v1.0.3705,
if you copied the whole directory structure from the W2K box,
by running aspnet_regiis -i from the
drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
quite frankly, this might screw up your system.

It's bound to be quite a complicated, and risky, task
to run a deprecated version of the .Net Framework
in an OS which doesn't even come with it, but comes
with a later version.

About the best thing I'd recommend is that VS.NET 2003
be installed in the *original* W2K box, and then that the
application be recompiled and debugged for the .Net 1.1 Framework.

Then, you could copy the *Application*
to your W2K3 box and run it under .Net 1.1.

best regards,


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:AD**********************************@microsof t.com...
I'm not sure if this is the issue; they're running this app on a Window 2K
box and I'mnot sure but the VS.NET project file has reference to Framework
1.0, see below:

<Reference Name = "System.Web.Services"
AssemblyName = "System.Web.Services"
HintPath =
"..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
/>

My Win2003 server only has accepted to run v1.1, is that the issue? If so,
do I need to install v1.0? I moved the folder over to my server for the
framework.

Thanx.

"Juan T. Llibre" wrote:
To create an Application using a Virtual Directory
as its starting point, open the IIS Manager, scroll
down to the virtual directory, select it, and rght-click it.

From the pop-up menu, select "Properties".

Then, click on the "Create" button.
That will make your virtual directory an Application.

If you do that, your error message should disappear.
Please let us know how you do.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
> I'm trying to get an existing VS.NET project up on my Win2003 server
> and I
> get the following error (on the actual website page):
>
> "It is an error to use a section registered as
> allowDefinition='MachineToApplication' beyond application level. This
> error
> can be caused by a virtual directory not being configured as an
> application
> in IIS."
>
> I've been told by the previous developer that the website needs to be
> set
> as
> a "application". I assume this means what process it runs under? I've
> created
> a virtual directory to the location and the site can be seen. but I get
> that
> error listed above?
> The application pools are:
>
> DEFAULTAPPPOOL (default)
> MSSHAREPOINTAPPPOOL
>
>
> What does this developer mean? Thanx

Nov 19 '05 #8

P: n/a
Also, looked at my Win2003 server in the directory you list below /CONFIG/
and I found:

in v1.0....
Version=1.0.3300.0

in v1.1...
Version=1.0.5000.0

Is this right, I assume 1.0.5 is 1.1???? Where do you find the reference to
1.1 as the framework?

thanx.
"Juan T. Llibre" wrote:
Hmmm...that is a problem.

If you take a look at
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config

you'll see that the references to v1.1.4322's
System.Web.Services are completely different.

I'm not even sure that you can *run*
..Net Framework v1.0.3705 in W2K3.

Windows Server 2003 is the first OS which runs
the .Net Framework 1.1.4322 "out of the box".

It doesn't even come with the
..Net Framework v1.0.3705 installed.

You could try to register the .Net Framework v1.0.3705,
if you copied the whole directory structure from the W2K box,
by running aspnet_regiis -i from the
drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
quite frankly, this might screw up your system.

It's bound to be quite a complicated, and risky, task
to run a deprecated version of the .Net Framework
in an OS which doesn't even come with it, but comes
with a later version.

About the best thing I'd recommend is that VS.NET 2003
be installed in the *original* W2K box, and then that the
application be recompiled and debugged for the .Net 1.1 Framework.

Then, you could copy the *Application*
to your W2K3 box and run it under .Net 1.1.

best regards,


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:AD**********************************@microsof t.com...
I'm not sure if this is the issue; they're running this app on a Window 2K
box and I'mnot sure but the VS.NET project file has reference to Framework
1.0, see below:

<Reference Name = "System.Web.Services"
AssemblyName = "System.Web.Services"
HintPath =
"..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
/>

My Win2003 server only has accepted to run v1.1, is that the issue? If so,
do I need to install v1.0? I moved the folder over to my server for the
framework.

Thanx.

"Juan T. Llibre" wrote:
To create an Application using a Virtual Directory
as its starting point, open the IIS Manager, scroll
down to the virtual directory, select it, and rght-click it.

From the pop-up menu, select "Properties".

Then, click on the "Create" button.
That will make your virtual directory an Application.

If you do that, your error message should disappear.
Please let us know how you do.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
> I'm trying to get an existing VS.NET project up on my Win2003 server
> and I
> get the following error (on the actual website page):
>
> "It is an error to use a section registered as
> allowDefinition='MachineToApplication' beyond application level. This
> error
> can be caused by a virtual directory not being configured as an
> application
> in IIS."
>
> I've been told by the previous developer that the website needs to be
> set
> as
> a "application". I assume this means what process it runs under? I've
> created
> a virtual directory to the location and the site can be seen. but I get
> that
> error listed above?
> The application pools are:
>
> DEFAULTAPPPOOL (default)
> MSSHAREPOINTAPPPOOL
>
>
> What does this developer mean? Thanx

Nov 19 '05 #9

P: n/a
Version 1.1 should be 1.1.4322, not 1.0.5000.0

If you right-click aspnet_isapi.dll in the
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
directory and select "properties", and then select
the "Version" tab, doesn't it have the version number
"1.1.4322.2032" ?


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:A7**********************************@microsof t.com...
Also, looked at my Win2003 server in the directory you list below /CONFIG/
and I found:

in v1.0....
Version=1.0.3300.0

in v1.1...
Version=1.0.5000.0

Is this right, I assume 1.0.5 is 1.1???? Where do you find the reference
to
1.1 as the framework?

thanx.
"Juan T. Llibre" wrote:
Hmmm...that is a problem.

If you take a look at
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config

you'll see that the references to v1.1.4322's
System.Web.Services are completely different.

I'm not even sure that you can *run*
..Net Framework v1.0.3705 in W2K3.

Windows Server 2003 is the first OS which runs
the .Net Framework 1.1.4322 "out of the box".

It doesn't even come with the
..Net Framework v1.0.3705 installed.

You could try to register the .Net Framework v1.0.3705,
if you copied the whole directory structure from the W2K box,
by running aspnet_regiis -i from the
drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
quite frankly, this might screw up your system.

It's bound to be quite a complicated, and risky, task
to run a deprecated version of the .Net Framework
in an OS which doesn't even come with it, but comes
with a later version.

About the best thing I'd recommend is that VS.NET 2003
be installed in the *original* W2K box, and then that the
application be recompiled and debugged for the .Net 1.1 Framework.

Then, you could copy the *Application*
to your W2K3 box and run it under .Net 1.1.

best regards,


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:AD**********************************@microsof t.com...
> I'm not sure if this is the issue; they're running this app on a Window
> 2K
> box and I'mnot sure but the VS.NET project file has reference to
> Framework
> 1.0, see below:
>
> <Reference Name = "System.Web.Services"
> AssemblyName = "System.Web.Services"
> HintPath =
> "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
> />
>
> My Win2003 server only has accepted to run v1.1, is that the issue? If
> so,
> do I need to install v1.0? I moved the folder over to my server for the
> framework.
>
> Thanx.
>
> "Juan T. Llibre" wrote:
>
>> To create an Application using a Virtual Directory
>> as its starting point, open the IIS Manager, scroll
>> down to the virtual directory, select it, and rght-click it.
>>
>> From the pop-up menu, select "Properties".
>>
>> Then, click on the "Create" button.
>> That will make your virtual directory an Application.
>>
>> If you do that, your error message should disappear.
>> Please let us know how you do.
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:73**********************************@microsof t.com...
>> > I'm trying to get an existing VS.NET project up on my Win2003 server
>> > and I
>> > get the following error (on the actual website page):
>> >
>> > "It is an error to use a section registered as
>> > allowDefinition='MachineToApplication' beyond application level.
>> > This
>> > error
>> > can be caused by a virtual directory not being configured as an
>> > application
>> > in IIS."
>> >
>> > I've been told by the previous developer that the website needs to
>> > be
>> > set
>> > as
>> > a "application". I assume this means what process it runs under?
>> > I've
>> > created
>> > a virtual directory to the location and the site can be seen. but I
>> > get
>> > that
>> > error listed above?
>> > The application pools are:
>> >
>> > DEFAULTAPPPOOL (default)
>> > MSSHAREPOINTAPPPOOL
>> >
>> >
>> > What does this developer mean? Thanx


Nov 19 '05 #10

P: n/a
I right click on that file and I do get: 1.1.4322.2032.

In the file you listed before:
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
on my win2003 server:
<section name="webServices"
type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
System.Web.Services, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a"/>

On local development box (VS.net on win2k):
I get the same.

I do have, on my 2003 server, a v1.0.3705 framework build now that I
installed 1.0. This is where I tried to create a new pooling choice using
it's 'aspnet_isapi.dll' file.

what about my other question? Any of this make sense? I use updater service
on both the server and workstation to keep updated.

thanx.
I get:

"Juan T. Llibre" wrote:
Version 1.1 should be 1.1.4322, not 1.0.5000.0

If you right-click aspnet_isapi.dll in the
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
directory and select "properties", and then select
the "Version" tab, doesn't it have the version number
"1.1.4322.2032" ?


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:A7**********************************@microsof t.com...
Also, looked at my Win2003 server in the directory you list below /CONFIG/
and I found:

in v1.0....
Version=1.0.3300.0

in v1.1...
Version=1.0.5000.0

Is this right, I assume 1.0.5 is 1.1???? Where do you find the reference
to
1.1 as the framework?

thanx.
"Juan T. Llibre" wrote:
Hmmm...that is a problem.

If you take a look at
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config

you'll see that the references to v1.1.4322's
System.Web.Services are completely different.

I'm not even sure that you can *run*
..Net Framework v1.0.3705 in W2K3.

Windows Server 2003 is the first OS which runs
the .Net Framework 1.1.4322 "out of the box".

It doesn't even come with the
..Net Framework v1.0.3705 installed.

You could try to register the .Net Framework v1.0.3705,
if you copied the whole directory structure from the W2K box,
by running aspnet_regiis -i from the
drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
quite frankly, this might screw up your system.

It's bound to be quite a complicated, and risky, task
to run a deprecated version of the .Net Framework
in an OS which doesn't even come with it, but comes
with a later version.

About the best thing I'd recommend is that VS.NET 2003
be installed in the *original* W2K box, and then that the
application be recompiled and debugged for the .Net 1.1 Framework.

Then, you could copy the *Application*
to your W2K3 box and run it under .Net 1.1.

best regards,


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:AD**********************************@microsof t.com...
> I'm not sure if this is the issue; they're running this app on a Window
> 2K
> box and I'mnot sure but the VS.NET project file has reference to
> Framework
> 1.0, see below:
>
> <Reference Name = "System.Web.Services"
> AssemblyName = "System.Web.Services"
> HintPath =
> "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
> />
>
> My Win2003 server only has accepted to run v1.1, is that the issue? If
> so,
> do I need to install v1.0? I moved the folder over to my server for the
> framework.
>
> Thanx.
>
> "Juan T. Llibre" wrote:
>
>> To create an Application using a Virtual Directory
>> as its starting point, open the IIS Manager, scroll
>> down to the virtual directory, select it, and rght-click it.
>>
>> From the pop-up menu, select "Properties".
>>
>> Then, click on the "Create" button.
>> That will make your virtual directory an Application.
>>
>> If you do that, your error message should disappear.
>> Please let us know how you do.
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:73**********************************@microsof t.com...
>> > I'm trying to get an existing VS.NET project up on my Win2003 server
>> > and I
>> > get the following error (on the actual website page):
>> >
>> > "It is an error to use a section registered as
>> > allowDefinition='MachineToApplication' beyond application level.
>> > This
>> > error
>> > can be caused by a virtual directory not being configured as an
>> > application
>> > in IIS."
>> >
>> > I've been told by the previous developer that the website needs to
>> > be
>> > set
>> > as
>> > a "application". I assume this means what process it runs under?
>> > I've
>> > created
>> > a virtual directory to the location and the site can be seen. but I
>> > get
>> > that
>> > error listed above?
>> > The application pools are:
>> >
>> > DEFAULTAPPPOOL (default)
>> > MSSHAREPOINTAPPPOOL
>> >
>> >
>> > What does this developer mean? Thanx


Nov 19 '05 #11

P: n/a
If you've gotten that far, maybe you can get
v1.0.3705 to work by running aspnet_regiis -i
from the v1.0.3705 directory.

Then, you could switch the application's version,
so it runs under v1.0.3705, by running Denis Bauer's
"ASP.NET Version Switcher" to change the .net
version the Application will runs as.

http://www.denisbauer.com/NETTools/A...nSwitcher.aspx

When you run the "ASP.NET Version Switcher"
check the .net version your Application is running as.

If it's listed as running under v1.1, change it to v1.0.
( *after* you run aspnet_regiis -i ).

To do that, select ASP.NET version 1.0,
and click the "Switch .Net Framework Version" button.

I don't guarantee you results,
but if it works you owe me a virtual beer !

;-)

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C0**********************************@microsof t.com...
I right click on that file and I do get: 1.1.4322.2032.

In the file you listed before:
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
on my win2003 server:
<section name="webServices"
type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
System.Web.Services, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a"/>

On local development box (VS.net on win2k):
I get the same.

I do have, on my 2003 server, a v1.0.3705 framework build now that I
installed 1.0. This is where I tried to create a new pooling choice using
it's 'aspnet_isapi.dll' file.

what about my other question? Any of this make sense? I use updater
service
on both the server and workstation to keep updated.

thanx.
I get:

"Juan T. Llibre" wrote:
Version 1.1 should be 1.1.4322, not 1.0.5000.0

If you right-click aspnet_isapi.dll in the
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
directory and select "properties", and then select
the "Version" tab, doesn't it have the version number
"1.1.4322.2032" ?


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:A7**********************************@microsof t.com...
> Also, looked at my Win2003 server in the directory you list below
> /CONFIG/
> and I found:
>
> in v1.0....
> Version=1.0.3300.0
>
> in v1.1...
> Version=1.0.5000.0
>
> Is this right, I assume 1.0.5 is 1.1???? Where do you find the
> reference
> to
> 1.1 as the framework?
>
> thanx.
> "Juan T. Llibre" wrote:
>
>> Hmmm...that is a problem.
>>
>> If you take a look at
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>>
>> you'll see that the references to v1.1.4322's
>> System.Web.Services are completely different.
>>
>> I'm not even sure that you can *run*
>> ..Net Framework v1.0.3705 in W2K3.
>>
>> Windows Server 2003 is the first OS which runs
>> the .Net Framework 1.1.4322 "out of the box".
>>
>> It doesn't even come with the
>> ..Net Framework v1.0.3705 installed.
>>
>> You could try to register the .Net Framework v1.0.3705,
>> if you copied the whole directory structure from the W2K box,
>> by running aspnet_regiis -i from the
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
>> quite frankly, this might screw up your system.
>>
>> It's bound to be quite a complicated, and risky, task
>> to run a deprecated version of the .Net Framework
>> in an OS which doesn't even come with it, but comes
>> with a later version.
>>
>> About the best thing I'd recommend is that VS.NET 2003
>> be installed in the *original* W2K box, and then that the
>> application be recompiled and debugged for the .Net 1.1 Framework.
>>
>> Then, you could copy the *Application*
>> to your W2K3 box and run it under .Net 1.1.
>>
>> best regards,
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:AD**********************************@microsof t.com...
>> > I'm not sure if this is the issue; they're running this app on a
>> > Window
>> > 2K
>> > box and I'mnot sure but the VS.NET project file has reference to
>> > Framework
>> > 1.0, see below:
>> >
>> > <Reference Name = "System.Web.Services"
>> > AssemblyName = "System.Web.Services"
>> > HintPath =
>> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> > />
>> >
>> > My Win2003 server only has accepted to run v1.1, is that the issue?
>> > If
>> > so,
>> > do I need to install v1.0? I moved the folder over to my server for
>> > the
>> > framework.
>> >
>> > Thanx.
>> >
>> > "Juan T. Llibre" wrote:
>> >
>> >> To create an Application using a Virtual Directory
>> >> as its starting point, open the IIS Manager, scroll
>> >> down to the virtual directory, select it, and rght-click it.
>> >>
>> >> From the pop-up menu, select "Properties".
>> >>
>> >> Then, click on the "Create" button.
>> >> That will make your virtual directory an Application.
>> >>
>> >> If you do that, your error message should disappear.
>> >> Please let us know how you do.
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:73**********************************@microsof t.com...
>> >> > I'm trying to get an existing VS.NET project up on my Win2003
>> >> > server
>> >> > and I
>> >> > get the following error (on the actual website page):
>> >> >
>> >> > "It is an error to use a section registered as
>> >> > allowDefinition='MachineToApplication' beyond application level.
>> >> > This
>> >> > error
>> >> > can be caused by a virtual directory not being configured as an
>> >> > application
>> >> > in IIS."
>> >> >
>> >> > I've been told by the previous developer that the website needs
>> >> > to
>> >> > be
>> >> > set
>> >> > as
>> >> > a "application". I assume this means what process it runs under?
>> >> > I've
>> >> > created
>> >> > a virtual directory to the location and the site can be seen. but
>> >> > I
>> >> > get
>> >> > that
>> >> > error listed above?
>> >> > The application pools are:
>> >> >
>> >> > DEFAULTAPPPOOL (default)
>> >> > MSSHAREPOINTAPPPOOL
>> >> >
>> >> >
>> >> > What does this developer mean? Thanx


Nov 19 '05 #12

P: n/a
thanx, I saw his application but before I do that, can anyone at MS answer
what do other developers do about Win2003 and Framework 1.0, I can't be the
only person who has experinced this? What is the official MS word on the use
of 1.0 and win2003?

"Juan T. Llibre" wrote:
If you've gotten that far, maybe you can get
v1.0.3705 to work by running aspnet_regiis -i
from the v1.0.3705 directory.

Then, you could switch the application's version,
so it runs under v1.0.3705, by running Denis Bauer's
"ASP.NET Version Switcher" to change the .net
version the Application will runs as.

http://www.denisbauer.com/NETTools/A...nSwitcher.aspx

When you run the "ASP.NET Version Switcher"
check the .net version your Application is running as.

If it's listed as running under v1.1, change it to v1.0.
( *after* you run aspnet_regiis -i ).

To do that, select ASP.NET version 1.0,
and click the "Switch .Net Framework Version" button.

I don't guarantee you results,
but if it works you owe me a virtual beer !

;-)

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C0**********************************@microsof t.com...
I right click on that file and I do get: 1.1.4322.2032.

In the file you listed before:
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
on my win2003 server:
<section name="webServices"
type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
System.Web.Services, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a"/>

On local development box (VS.net on win2k):
I get the same.

I do have, on my 2003 server, a v1.0.3705 framework build now that I
installed 1.0. This is where I tried to create a new pooling choice using
it's 'aspnet_isapi.dll' file.

what about my other question? Any of this make sense? I use updater
service
on both the server and workstation to keep updated.

thanx.
I get:

"Juan T. Llibre" wrote:
Version 1.1 should be 1.1.4322, not 1.0.5000.0

If you right-click aspnet_isapi.dll in the
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
directory and select "properties", and then select
the "Version" tab, doesn't it have the version number
"1.1.4322.2032" ?


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:A7**********************************@microsof t.com...
> Also, looked at my Win2003 server in the directory you list below
> /CONFIG/
> and I found:
>
> in v1.0....
> Version=1.0.3300.0
>
> in v1.1...
> Version=1.0.5000.0
>
> Is this right, I assume 1.0.5 is 1.1???? Where do you find the
> reference
> to
> 1.1 as the framework?
>
> thanx.
> "Juan T. Llibre" wrote:
>
>> Hmmm...that is a problem.
>>
>> If you take a look at
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>>
>> you'll see that the references to v1.1.4322's
>> System.Web.Services are completely different.
>>
>> I'm not even sure that you can *run*
>> ..Net Framework v1.0.3705 in W2K3.
>>
>> Windows Server 2003 is the first OS which runs
>> the .Net Framework 1.1.4322 "out of the box".
>>
>> It doesn't even come with the
>> ..Net Framework v1.0.3705 installed.
>>
>> You could try to register the .Net Framework v1.0.3705,
>> if you copied the whole directory structure from the W2K box,
>> by running aspnet_regiis -i from the
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
>> quite frankly, this might screw up your system.
>>
>> It's bound to be quite a complicated, and risky, task
>> to run a deprecated version of the .Net Framework
>> in an OS which doesn't even come with it, but comes
>> with a later version.
>>
>> About the best thing I'd recommend is that VS.NET 2003
>> be installed in the *original* W2K box, and then that the
>> application be recompiled and debugged for the .Net 1.1 Framework.
>>
>> Then, you could copy the *Application*
>> to your W2K3 box and run it under .Net 1.1.
>>
>> best regards,
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:AD**********************************@microsof t.com...
>> > I'm not sure if this is the issue; they're running this app on a
>> > Window
>> > 2K
>> > box and I'mnot sure but the VS.NET project file has reference to
>> > Framework
>> > 1.0, see below:
>> >
>> > <Reference Name = "System.Web.Services"
>> > AssemblyName = "System.Web.Services"
>> > HintPath =
>> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> > />
>> >
>> > My Win2003 server only has accepted to run v1.1, is that the issue?
>> > If
>> > so,
>> > do I need to install v1.0? I moved the folder over to my server for
>> > the
>> > framework.
>> >
>> > Thanx.
>> >
>> > "Juan T. Llibre" wrote:
>> >
>> >> To create an Application using a Virtual Directory
>> >> as its starting point, open the IIS Manager, scroll
>> >> down to the virtual directory, select it, and rght-click it.
>> >>
>> >> From the pop-up menu, select "Properties".
>> >>
>> >> Then, click on the "Create" button.
>> >> That will make your virtual directory an Application.
>> >>
>> >> If you do that, your error message should disappear.
>> >> Please let us know how you do.
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:73**********************************@microsof t.com...
>> >> > I'm trying to get an existing VS.NET project up on my Win2003
>> >> > server
>> >> > and I
>> >> > get the following error (on the actual website page):
>> >> >
>> >> > "It is an error to use a section registered as
>> >> > allowDefinition='MachineToApplication' beyond application level.
>> >> > This
>> >> > error
>> >> > can be caused by a virtual directory not being configured as an
>> >> > application
>> >> > in IIS."
>> >> >
>> >> > I've been told by the previous developer that the website needs
>> >> > to
>> >> > be
>> >> > set
>> >> > as
>> >> > a "application". I assume this means what process it runs under?
>> >> > I've
>> >> > created
>> >> > a virtual directory to the location and the site can be seen. but
>> >> > I
>> >> > get
>> >> > that
>> >> > error listed above?
>> >> > The application pools are:
>> >> >
>> >> > DEFAULTAPPPOOL (default)
>> >> > MSSHAREPOINTAPPPOOL
>> >> >
>> >> >
>> >> > What does this developer mean? Thanx


Nov 19 '05 #13

P: n/a
If you were able to install v1.0
( as apparently you've been able to)
running it should be no problem.

There's lot's of documentation stating tha
side-by-side running of v1.0 and v1.1 is OK.

When you *add* v1.1 to a v1.0 installation
it certainly runs OK.

I just didn't know whether running v1.0 in
W2K3 ( which runs 1.1 natively ) is OK.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:ED**********************************@microsof t.com...
thanx, I saw his application but before I do that, can anyone at MS answer
what do other developers do about Win2003 and Framework 1.0, I can't be
the
only person who has experinced this? What is the official MS word on the
use
of 1.0 and win2003?

"Juan T. Llibre" wrote:
If you've gotten that far, maybe you can get
v1.0.3705 to work by running aspnet_regiis -i
from the v1.0.3705 directory.

Then, you could switch the application's version,
so it runs under v1.0.3705, by running Denis Bauer's
"ASP.NET Version Switcher" to change the .net
version the Application will runs as.

http://www.denisbauer.com/NETTools/A...nSwitcher.aspx

When you run the "ASP.NET Version Switcher"
check the .net version your Application is running as.

If it's listed as running under v1.1, change it to v1.0.
( *after* you run aspnet_regiis -i ).

To do that, select ASP.NET version 1.0,
and click the "Switch .Net Framework Version" button.

I don't guarantee you results,
but if it works you owe me a virtual beer !

;-)

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C0**********************************@microsof t.com...
>I right click on that file and I do get: 1.1.4322.2032.
>
> In the file you listed before:
> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
> on my win2003 server:
> <section name="webServices"
> type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
> System.Web.Services, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b03f5f7f11d50a3a"/>
>
> On local development box (VS.net on win2k):
> I get the same.
>
> I do have, on my 2003 server, a v1.0.3705 framework build now that I
> installed 1.0. This is where I tried to create a new pooling choice
> using
> it's 'aspnet_isapi.dll' file.
>
> what about my other question? Any of this make sense? I use updater
> service
> on both the server and workstation to keep updated.
>
> thanx.
>
>
> I get:
>
> "Juan T. Llibre" wrote:
>
>> Version 1.1 should be 1.1.4322, not 1.0.5000.0
>>
>> If you right-click aspnet_isapi.dll in the
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>> directory and select "properties", and then select
>> the "Version" tab, doesn't it have the version number
>> "1.1.4322.2032" ?
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:A7**********************************@microsof t.com...
>> > Also, looked at my Win2003 server in the directory you list below
>> > /CONFIG/
>> > and I found:
>> >
>> > in v1.0....
>> > Version=1.0.3300.0
>> >
>> > in v1.1...
>> > Version=1.0.5000.0
>> >
>> > Is this right, I assume 1.0.5 is 1.1???? Where do you find the
>> > reference
>> > to
>> > 1.1 as the framework?
>> >
>> > thanx.
>> > "Juan T. Llibre" wrote:
>> >
>> >> Hmmm...that is a problem.
>> >>
>> >> If you take a look at
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> >>
>> >> you'll see that the references to v1.1.4322's
>> >> System.Web.Services are completely different.
>> >>
>> >> I'm not even sure that you can *run*
>> >> ..Net Framework v1.0.3705 in W2K3.
>> >>
>> >> Windows Server 2003 is the first OS which runs
>> >> the .Net Framework 1.1.4322 "out of the box".
>> >>
>> >> It doesn't even come with the
>> >> ..Net Framework v1.0.3705 installed.
>> >>
>> >> You could try to register the .Net Framework v1.0.3705,
>> >> if you copied the whole directory structure from the W2K box,
>> >> by running aspnet_regiis -i from the
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
>> >> quite frankly, this might screw up your system.
>> >>
>> >> It's bound to be quite a complicated, and risky, task
>> >> to run a deprecated version of the .Net Framework
>> >> in an OS which doesn't even come with it, but comes
>> >> with a later version.
>> >>
>> >> About the best thing I'd recommend is that VS.NET 2003
>> >> be installed in the *original* W2K box, and then that the
>> >> application be recompiled and debugged for the .Net 1.1 Framework.
>> >>
>> >> Then, you could copy the *Application*
>> >> to your W2K3 box and run it under .Net 1.1.
>> >>
>> >> best regards,
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:AD**********************************@microsof t.com...
>> >> > I'm not sure if this is the issue; they're running this app on a
>> >> > Window
>> >> > 2K
>> >> > box and I'mnot sure but the VS.NET project file has reference to
>> >> > Framework
>> >> > 1.0, see below:
>> >> >
>> >> > <Reference Name = "System.Web.Services"
>> >> > AssemblyName = "System.Web.Services"
>> >> > HintPath =
>> >> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> >> > />
>> >> >
>> >> > My Win2003 server only has accepted to run v1.1, is that the
>> >> > issue?
>> >> > If
>> >> > so,
>> >> > do I need to install v1.0? I moved the folder over to my server
>> >> > for
>> >> > the
>> >> > framework.
>> >> >
>> >> > Thanx.
>> >> >
>> >> > "Juan T. Llibre" wrote:
>> >> >
>> >> >> To create an Application using a Virtual Directory
>> >> >> as its starting point, open the IIS Manager, scroll
>> >> >> down to the virtual directory, select it, and rght-click it.
>> >> >>
>> >> >> From the pop-up menu, select "Properties".
>> >> >>
>> >> >> Then, click on the "Create" button.
>> >> >> That will make your virtual directory an Application.
>> >> >>
>> >> >> If you do that, your error message should disappear.
>> >> >> Please let us know how you do.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Juan T. Llibre
>> >> >> ASP.NET MVP
>> >> >> ===========
>> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> news:73**********************************@microsof t.com...
>> >> >> > I'm trying to get an existing VS.NET project up on my Win2003
>> >> >> > server
>> >> >> > and I
>> >> >> > get the following error (on the actual website page):
>> >> >> >
>> >> >> > "It is an error to use a section registered as
>> >> >> > allowDefinition='MachineToApplication' beyond application
>> >> >> > level.
>> >> >> > This
>> >> >> > error
>> >> >> > can be caused by a virtual directory not being configured as
>> >> >> > an
>> >> >> > application
>> >> >> > in IIS."
>> >> >> >
>> >> >> > I've been told by the previous developer that the website
>> >> >> > needs
>> >> >> > to
>> >> >> > be
>> >> >> > set
>> >> >> > as
>> >> >> > a "application". I assume this means what process it runs
>> >> >> > under?
>> >> >> > I've
>> >> >> > created
>> >> >> > a virtual directory to the location and the site can be seen.
>> >> >> > but
>> >> >> > I
>> >> >> > get
>> >> >> > that
>> >> >> > error listed above?
>> >> >> > The application pools are:
>> >> >> >
>> >> >> > DEFAULTAPPPOOL (default)
>> >> >> > MSSHAREPOINTAPPPOOL
>> >> >> >
>> >> >> >
>> >> >> > What does this developer mean? Thanx
>>
>>
>>
>>


Nov 19 '05 #14

P: n/a
don't take this the wrong way but I don't have a warm and fuzzy feeling about
this. You thought before that they shouldn't work together, I did get them
installed together but can't get IIS to see the v1.0 structure. Then there is
a chance to use Denis Bauer's app to switch them, but we're not really sure
if running on win2003 is sucj a good and stable thing. I can't get the
application I started out with to work on my win2003 server, and I'm not
feeling to sure of MS's position. I'd love to know:

1.) Is it MS's position to leave 2003 at 1.1 and not to use 1.0?
2.) Is win2K used for 1.0 only?
3.) Is there a MS article on using multple frameworks on a win2003 server,
not win2000?
4.) Would it be better, theorically, to just update this asp.net v1.0 app to
1.1? And what does that entail?
5.) Is there a simply way to determine if an asp.net app is v1.0 or 1.1?
Check the VS.NET project file for referance paths? Anything with VS.net, or a
file?

Please don't take offense, I appreciate your help but need to know, thanx.

"Juan T. Llibre" wrote:
If you were able to install v1.0
( as apparently you've been able to)
running it should be no problem.

There's lot's of documentation stating tha
side-by-side running of v1.0 and v1.1 is OK.

When you *add* v1.1 to a v1.0 installation
it certainly runs OK.

I just didn't know whether running v1.0 in
W2K3 ( which runs 1.1 natively ) is OK.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:ED**********************************@microsof t.com...
thanx, I saw his application but before I do that, can anyone at MS answer
what do other developers do about Win2003 and Framework 1.0, I can't be
the
only person who has experinced this? What is the official MS word on the
use
of 1.0 and win2003?

"Juan T. Llibre" wrote:
If you've gotten that far, maybe you can get
v1.0.3705 to work by running aspnet_regiis -i
from the v1.0.3705 directory.

Then, you could switch the application's version,
so it runs under v1.0.3705, by running Denis Bauer's
"ASP.NET Version Switcher" to change the .net
version the Application will runs as.

http://www.denisbauer.com/NETTools/A...nSwitcher.aspx

When you run the "ASP.NET Version Switcher"
check the .net version your Application is running as.

If it's listed as running under v1.1, change it to v1.0.
( *after* you run aspnet_regiis -i ).

To do that, select ASP.NET version 1.0,
and click the "Switch .Net Framework Version" button.

I don't guarantee you results,
but if it works you owe me a virtual beer !

;-)

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C0**********************************@microsof t.com...
>I right click on that file and I do get: 1.1.4322.2032.
>
> In the file you listed before:
> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
> on my win2003 server:
> <section name="webServices"
> type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
> System.Web.Services, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b03f5f7f11d50a3a"/>
>
> On local development box (VS.net on win2k):
> I get the same.
>
> I do have, on my 2003 server, a v1.0.3705 framework build now that I
> installed 1.0. This is where I tried to create a new pooling choice
> using
> it's 'aspnet_isapi.dll' file.
>
> what about my other question? Any of this make sense? I use updater
> service
> on both the server and workstation to keep updated.
>
> thanx.
>
>
> I get:
>
> "Juan T. Llibre" wrote:
>
>> Version 1.1 should be 1.1.4322, not 1.0.5000.0
>>
>> If you right-click aspnet_isapi.dll in the
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>> directory and select "properties", and then select
>> the "Version" tab, doesn't it have the version number
>> "1.1.4322.2032" ?
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:A7**********************************@microsof t.com...
>> > Also, looked at my Win2003 server in the directory you list below
>> > /CONFIG/
>> > and I found:
>> >
>> > in v1.0....
>> > Version=1.0.3300.0
>> >
>> > in v1.1...
>> > Version=1.0.5000.0
>> >
>> > Is this right, I assume 1.0.5 is 1.1???? Where do you find the
>> > reference
>> > to
>> > 1.1 as the framework?
>> >
>> > thanx.
>> > "Juan T. Llibre" wrote:
>> >
>> >> Hmmm...that is a problem.
>> >>
>> >> If you take a look at
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> >>
>> >> you'll see that the references to v1.1.4322's
>> >> System.Web.Services are completely different.
>> >>
>> >> I'm not even sure that you can *run*
>> >> ..Net Framework v1.0.3705 in W2K3.
>> >>
>> >> Windows Server 2003 is the first OS which runs
>> >> the .Net Framework 1.1.4322 "out of the box".
>> >>
>> >> It doesn't even come with the
>> >> ..Net Framework v1.0.3705 installed.
>> >>
>> >> You could try to register the .Net Framework v1.0.3705,
>> >> if you copied the whole directory structure from the W2K box,
>> >> by running aspnet_regiis -i from the
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
>> >> quite frankly, this might screw up your system.
>> >>
>> >> It's bound to be quite a complicated, and risky, task
>> >> to run a deprecated version of the .Net Framework
>> >> in an OS which doesn't even come with it, but comes
>> >> with a later version.
>> >>
>> >> About the best thing I'd recommend is that VS.NET 2003
>> >> be installed in the *original* W2K box, and then that the
>> >> application be recompiled and debugged for the .Net 1.1 Framework.
>> >>
>> >> Then, you could copy the *Application*
>> >> to your W2K3 box and run it under .Net 1.1.
>> >>
>> >> best regards,
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:AD**********************************@microsof t.com...
>> >> > I'm not sure if this is the issue; they're running this app on a
>> >> > Window
>> >> > 2K
>> >> > box and I'mnot sure but the VS.NET project file has reference to
>> >> > Framework
>> >> > 1.0, see below:
>> >> >
>> >> > <Reference Name = "System.Web.Services"
>> >> > AssemblyName = "System.Web.Services"
>> >> > HintPath =
>> >> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> >> > />
>> >> >
>> >> > My Win2003 server only has accepted to run v1.1, is that the
>> >> > issue?
>> >> > If
>> >> > so,
>> >> > do I need to install v1.0? I moved the folder over to my server
>> >> > for
>> >> > the
>> >> > framework.
>> >> >
>> >> > Thanx.
>> >> >
>> >> > "Juan T. Llibre" wrote:
>> >> >
>> >> >> To create an Application using a Virtual Directory
>> >> >> as its starting point, open the IIS Manager, scroll
>> >> >> down to the virtual directory, select it, and rght-click it.
>> >> >>
>> >> >> From the pop-up menu, select "Properties".
>> >> >>
>> >> >> Then, click on the "Create" button.
>> >> >> That will make your virtual directory an Application.
>> >> >>
>> >> >> If you do that, your error message should disappear.
>> >> >> Please let us know how you do.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Juan T. Llibre
>> >> >> ASP.NET MVP
>> >> >> ===========
>> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> news:73**********************************@microsof t.com...
>> >> >> > I'm trying to get an existing VS.NET project up on my Win2003
>> >> >> > server
>> >> >> > and I
>> >> >> > get the following error (on the actual website page):
>> >> >> >
>> >> >> > "It is an error to use a section registered as
>> >> >> > allowDefinition='MachineToApplication' beyond application
>> >> >> > level.
>> >> >> > This
>> >> >> > error
>> >> >> > can be caused by a virtual directory not being configured as
>> >> >> > an
>> >> >> > application
>> >> >> > in IIS."
>> >> >> >
>> >> >> > I've been told by the previous developer that the website
>> >> >> > needs
>> >> >> > to
>> >> >> > be
>> >> >> > set
>> >> >> > as
>> >> >> > a "application". I assume this means what process it runs
>> >> >> > under?
>> >> >> > I've
>> >> >> > created
>> >> >> > a virtual directory to the location and the site can be seen.
>> >> >> > but
>> >> >> > I
>> >> >> > get
>> >> >> > that
>> >> >> > error listed above?
>> >> >> > The application pools are:
>> >> >> >
>> >> >> > DEFAULTAPPPOOL (default)
>> >> >> > MSSHAREPOINTAPPPOOL
>> >> >> >
>> >> >> >
>> >> >> > What does this developer mean? Thanx
>>
>>
>>
>>


Nov 19 '05 #15

P: n/a
I don't know what I was thinking, becuase I read that v1.1 is backward
compatible to v1.0, so I don't need 1.0 on my Win2003 server. If I move to
2.0 then it will have to updated on the server. The assumption is that the
highest revision of the framework is always backward compatible correct?

thanx.

"Juan T. Llibre" wrote:
If you've gotten that far, maybe you can get
v1.0.3705 to work by running aspnet_regiis -i
from the v1.0.3705 directory.

Then, you could switch the application's version,
so it runs under v1.0.3705, by running Denis Bauer's
"ASP.NET Version Switcher" to change the .net
version the Application will runs as.

http://www.denisbauer.com/NETTools/A...nSwitcher.aspx

When you run the "ASP.NET Version Switcher"
check the .net version your Application is running as.

If it's listed as running under v1.1, change it to v1.0.
( *after* you run aspnet_regiis -i ).

To do that, select ASP.NET version 1.0,
and click the "Switch .Net Framework Version" button.

I don't guarantee you results,
but if it works you owe me a virtual beer !

;-)

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C0**********************************@microsof t.com...
I right click on that file and I do get: 1.1.4322.2032.

In the file you listed before:
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
on my win2003 server:
<section name="webServices"
type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
System.Web.Services, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a"/>

On local development box (VS.net on win2k):
I get the same.

I do have, on my 2003 server, a v1.0.3705 framework build now that I
installed 1.0. This is where I tried to create a new pooling choice using
it's 'aspnet_isapi.dll' file.

what about my other question? Any of this make sense? I use updater
service
on both the server and workstation to keep updated.

thanx.
I get:

"Juan T. Llibre" wrote:
Version 1.1 should be 1.1.4322, not 1.0.5000.0

If you right-click aspnet_isapi.dll in the
drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
directory and select "properties", and then select
the "Version" tab, doesn't it have the version number
"1.1.4322.2032" ?


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:A7**********************************@microsof t.com...
> Also, looked at my Win2003 server in the directory you list below
> /CONFIG/
> and I found:
>
> in v1.0....
> Version=1.0.3300.0
>
> in v1.1...
> Version=1.0.5000.0
>
> Is this right, I assume 1.0.5 is 1.1???? Where do you find the
> reference
> to
> 1.1 as the framework?
>
> thanx.
> "Juan T. Llibre" wrote:
>
>> Hmmm...that is a problem.
>>
>> If you take a look at
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>>
>> you'll see that the references to v1.1.4322's
>> System.Web.Services are completely different.
>>
>> I'm not even sure that you can *run*
>> ..Net Framework v1.0.3705 in W2K3.
>>
>> Windows Server 2003 is the first OS which runs
>> the .Net Framework 1.1.4322 "out of the box".
>>
>> It doesn't even come with the
>> ..Net Framework v1.0.3705 installed.
>>
>> You could try to register the .Net Framework v1.0.3705,
>> if you copied the whole directory structure from the W2K box,
>> by running aspnet_regiis -i from the
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
>> quite frankly, this might screw up your system.
>>
>> It's bound to be quite a complicated, and risky, task
>> to run a deprecated version of the .Net Framework
>> in an OS which doesn't even come with it, but comes
>> with a later version.
>>
>> About the best thing I'd recommend is that VS.NET 2003
>> be installed in the *original* W2K box, and then that the
>> application be recompiled and debugged for the .Net 1.1 Framework.
>>
>> Then, you could copy the *Application*
>> to your W2K3 box and run it under .Net 1.1.
>>
>> best regards,
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:AD**********************************@microsof t.com...
>> > I'm not sure if this is the issue; they're running this app on a
>> > Window
>> > 2K
>> > box and I'mnot sure but the VS.NET project file has reference to
>> > Framework
>> > 1.0, see below:
>> >
>> > <Reference Name = "System.Web.Services"
>> > AssemblyName = "System.Web.Services"
>> > HintPath =
>> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> > />
>> >
>> > My Win2003 server only has accepted to run v1.1, is that the issue?
>> > If
>> > so,
>> > do I need to install v1.0? I moved the folder over to my server for
>> > the
>> > framework.
>> >
>> > Thanx.
>> >
>> > "Juan T. Llibre" wrote:
>> >
>> >> To create an Application using a Virtual Directory
>> >> as its starting point, open the IIS Manager, scroll
>> >> down to the virtual directory, select it, and rght-click it.
>> >>
>> >> From the pop-up menu, select "Properties".
>> >>
>> >> Then, click on the "Create" button.
>> >> That will make your virtual directory an Application.
>> >>
>> >> If you do that, your error message should disappear.
>> >> Please let us know how you do.
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:73**********************************@microsof t.com...
>> >> > I'm trying to get an existing VS.NET project up on my Win2003
>> >> > server
>> >> > and I
>> >> > get the following error (on the actual website page):
>> >> >
>> >> > "It is an error to use a section registered as
>> >> > allowDefinition='MachineToApplication' beyond application level.
>> >> > This
>> >> > error
>> >> > can be caused by a virtual directory not being configured as an
>> >> > application
>> >> > in IIS."
>> >> >
>> >> > I've been told by the previous developer that the website needs
>> >> > to
>> >> > be
>> >> > set
>> >> > as
>> >> > a "application". I assume this means what process it runs under?
>> >> > I've
>> >> > created
>> >> > a virtual directory to the location and the site can be seen. but
>> >> > I
>> >> > get
>> >> > that
>> >> > error listed above?
>> >> > The application pools are:
>> >> >
>> >> > DEFAULTAPPPOOL (default)
>> >> > MSSHAREPOINTAPPPOOL
>> >> >
>> >> >
>> >> > What does this developer mean? Thanx


Nov 19 '05 #16

P: n/a
re:
I don't need 1.0 on my Win2003 server.
The assumption is that the highest revision of
the framework is always backward compatible correct?
No.

Your 1.0 application may call assemblies which don't exist any more,
or whose functions have been changed in later versions.

That's why .Net versions run "side-by-side",
instead of the latest version just replacing the "old" version.

You need the *particular* version of .Net for which the application
was compiled for to be installed, and enabled, in order to be assured
of being able to run a .Net application compiled for a previous
version of the .Net Framework you've got installed.

Also, the assembly versioning in machine.config is different
for different versions of the .Net framework.

For example, see the differences between v1.1 and v2.0 :

1.1 :
<section name="webServices" type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler, System.Web.Services, Version=1.0.5000.0,

2.0 :
<section name="webServices" type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler, System.Web.Services, Version=2.0.3600.0,

Notice the difference between the Version numbers.
It's a different one for .Net 1.0, too.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message news:4A**********************************@microsof t.com...I don't know what I was thinking, becuase I read that v1.1 is backward
compatible to v1.0, so I don't need 1.0 on my Win2003 server. If I move to
2.0 then it will have to updated on the server. The assumption is that the
highest revision of the framework is always backward compatible correct?

thanx. "Juan T. Llibre" wrote:
If you've gotten that far, maybe you can get
v1.0.3705 to work by running aspnet_regiis -i
from the v1.0.3705 directory.

Then, you could switch the application's version,
so it runs under v1.0.3705, by running Denis Bauer's
"ASP.NET Version Switcher" to change the .net
version the Application will runs as.

http://www.denisbauer.com/NETTools/A...nSwitcher.aspx

When you run the "ASP.NET Version Switcher"
check the .net version your Application is running as.

If it's listed as running under v1.1, change it to v1.0.
( *after* you run aspnet_regiis -i ).

To do that, select ASP.NET version 1.0,
and click the "Switch .Net Framework Version" button.

I don't guarantee you results,
but if it works you owe me a virtual beer !

;-)



Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C0**********************************@microsof t.com...
>I right click on that file and I do get: 1.1.4322.2032.
>
> In the file you listed before:
> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
> on my win2003 server:
> <section name="webServices"
> type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
> System.Web.Services, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b03f5f7f11d50a3a"/>
>
> On local development box (VS.net on win2k):
> I get the same.
>
> I do have, on my 2003 server, a v1.0.3705 framework build now that I
> installed 1.0. This is where I tried to create a new pooling choice using
> it's 'aspnet_isapi.dll' file.
>
> what about my other question? Any of this make sense? I use updater
> service
> on both the server and workstation to keep updated.
>
> thanx.
>
>
> I get:
>
> "Juan T. Llibre" wrote:
>
>> Version 1.1 should be 1.1.4322, not 1.0.5000.0
>>
>> If you right-click aspnet_isapi.dll in the
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>> directory and select "properties", and then select
>> the "Version" tab, doesn't it have the version number
>> "1.1.4322.2032" ?
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:A7**********************************@microsof t.com...
>> > Also, looked at my Win2003 server in the directory you list below
>> > /CONFIG/
>> > and I found:
>> >
>> > in v1.0....
>> > Version=1.0.3300.0
>> >
>> > in v1.1...
>> > Version=1.0.5000.0
>> >
>> > Is this right, I assume 1.0.5 is 1.1???? Where do you find the
>> > reference
>> > to
>> > 1.1 as the framework?
>> >
>> > thanx.
>> > "Juan T. Llibre" wrote:
>> >
>> >> Hmmm...that is a problem.
>> >>
>> >> If you take a look at
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> >>
>> >> you'll see that the references to v1.1.4322's
>> >> System.Web.Services are completely different.
>> >>
>> >> I'm not even sure that you can *run*
>> >> ..Net Framework v1.0.3705 in W2K3.
>> >>
>> >> Windows Server 2003 is the first OS which runs
>> >> the .Net Framework 1.1.4322 "out of the box".
>> >>
>> >> It doesn't even come with the
>> >> ..Net Framework v1.0.3705 installed.
>> >>
>> >> You could try to register the .Net Framework v1.0.3705,
>> >> if you copied the whole directory structure from the W2K box,
>> >> by running aspnet_regiis -i from the
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
>> >> quite frankly, this might screw up your system.
>> >>
>> >> It's bound to be quite a complicated, and risky, task
>> >> to run a deprecated version of the .Net Framework
>> >> in an OS which doesn't even come with it, but comes
>> >> with a later version.
>> >>
>> >> About the best thing I'd recommend is that VS.NET 2003
>> >> be installed in the *original* W2K box, and then that the
>> >> application be recompiled and debugged for the .Net 1.1 Framework.
>> >>
>> >> Then, you could copy the *Application*
>> >> to your W2K3 box and run it under .Net 1.1.
>> >>
>> >> best regards,
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:AD**********************************@microsof t.com...
>> >> > I'm not sure if this is the issue; they're running this app on a
>> >> > Window
>> >> > 2K
>> >> > box and I'mnot sure but the VS.NET project file has reference to
>> >> > Framework
>> >> > 1.0, see below:
>> >> >
>> >> > <Reference Name = "System.Web.Services"
>> >> > AssemblyName = "System.Web.Services"
>> >> > HintPath =
>> >> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> >> > />
>> >> >
>> >> > My Win2003 server only has accepted to run v1.1, is that the issue?
>> >> > If
>> >> > so,
>> >> > do I need to install v1.0? I moved the folder over to my server for
>> >> > the
>> >> > framework.
>> >> >
>> >> > Thanx.
>> >> >
>> >> > "Juan T. Llibre" wrote:
>> >> >
>> >> >> To create an Application using a Virtual Directory
>> >> >> as its starting point, open the IIS Manager, scroll
>> >> >> down to the virtual directory, select it, and rght-click it.
>> >> >>
>> >> >> From the pop-up menu, select "Properties".
>> >> >>
>> >> >> Then, click on the "Create" button.
>> >> >> That will make your virtual directory an Application.
>> >> >>
>> >> >> If you do that, your error message should disappear.
>> >> >> Please let us know how you do.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Juan T. Llibre
>> >> >> ASP.NET MVP
>> >> >> ===========
>> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> news:73**********************************@microsof t.com...
>> >> >> > I'm trying to get an existing VS.NET project up on my Win2003
>> >> >> > server
>> >> >> > and I
>> >> >> > get the following error (on the actual website page):
>> >> >> >
>> >> >> > "It is an error to use a section registered as
>> >> >> > allowDefinition='MachineToApplication' beyond application level.
>> >> >> > This
>> >> >> > error
>> >> >> > can be caused by a virtual directory not being configured as an
>> >> >> > application
>> >> >> > in IIS."
>> >> >> >
>> >> >> > I've been told by the previous developer that the website needs
>> >> >> > to
>> >> >> > be
>> >> >> > set
>> >> >> > as
>> >> >> > a "application". I assume this means what process it runs under?
>> >> >> > I've
>> >> >> > created
>> >> >> > a virtual directory to the location and the site can be seen. but
>> >> >> > I
>> >> >> > get
>> >> >> > that
>> >> >> > error listed above?
>> >> >> > The application pools are:
>> >> >> >
>> >> >> > DEFAULTAPPPOOL (default)
>> >> >> > MSSHAREPOINTAPPPOOL
>> >> >> >
>> >> >> >
>> >> >> > What does this developer mean? Thanx


Nov 19 '05 #17

P: n/a
re:
don't take this the wrong way
I'm not.

re:You thought before that they shouldn't work together
They don't. See below.

re: I did get them installed together but can't
get IIS to see the v1.0 structure.
I warned you about potential problems, didn't I ?

re: Please don't take offense,
I haven't taken offense.

re: I appreciate your help but need to know, thanx.
You should know, now.

re: 1.) Is it MS's position to leave 2003 at 1.1 and not to use 1.0?
See below.

re: 2.) Is win2K used for 1.0 only?
No. You can install any version of the .Net Framework on W2K.

re: 3.) Is there a MS article on using multple frameworks
on a win2003 server, not win2000?
The closest I could find is :
http://support.microsoft.com/default...b;en-us;830714

"On a Windows Server 2003 system, you must use .NET Framework 1.1."

re: 4.) Would it be better, theorically, to just update this
asp.net v1.0 app to 1.1? And what does that entail?
I already told you that was what you needed to do and how to do that.
About the best thing I'd recommend is that VS.NET 2003
be installed in the *original* W2K box, and then that the
application be recompiled and debugged for the .Net 1.1 Framework.

Then, you could copy the *Application*
to your W2K3 box and run it under .Net 1.1.


Good luck!

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:30**********************************@microsof t.com... don't take this the wrong way but I don't have a warm and fuzzy feeling
about
this. You thought before that they shouldn't work together, I did get them
installed together but can't get IIS to see the v1.0 structure. Then there
is
a chance to use Denis Bauer's app to switch them, but we're not really
sure
if running on win2003 is sucj a good and stable thing. I can't get the
application I started out with to work on my win2003 server, and I'm not
feeling to sure of MS's position. I'd love to know:

1.) Is it MS's position to leave 2003 at 1.1 and not to use 1.0?
2.) Is win2K used for 1.0 only?
3.) Is there a MS article on using multple frameworks on a win2003 server,
not win2000?
4.) Would it be better, theorically, to just update this asp.net v1.0 app
to
1.1? And what does that entail?
5.) Is there a simply way to determine if an asp.net app is v1.0 or 1.1?
Check the VS.NET project file for referance paths? Anything with VS.net,
or a
file?

Please don't take offense, I appreciate your help but need to know, thanx.

"Juan T. Llibre" wrote:
If you were able to install v1.0
( as apparently you've been able to)
running it should be no problem.

There's lot's of documentation stating tha
side-by-side running of v1.0 and v1.1 is OK.

When you *add* v1.1 to a v1.0 installation
it certainly runs OK.

I just didn't know whether running v1.0 in
W2K3 ( which runs 1.1 natively ) is OK.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:ED**********************************@microsof t.com...
> thanx, I saw his application but before I do that, can anyone at MS
> answer
> what do other developers do about Win2003 and Framework 1.0, I can't be
> the
> only person who has experinced this? What is the official MS word on
> the
> use
> of 1.0 and win2003?
>
> "Juan T. Llibre" wrote:
>
>> If you've gotten that far, maybe you can get
>> v1.0.3705 to work by running aspnet_regiis -i
>> from the v1.0.3705 directory.
>>
>> Then, you could switch the application's version,
>> so it runs under v1.0.3705, by running Denis Bauer's
>> "ASP.NET Version Switcher" to change the .net
>> version the Application will runs as.
>>
>> http://www.denisbauer.com/NETTools/A...nSwitcher.aspx
>>
>> When you run the "ASP.NET Version Switcher"
>> check the .net version your Application is running as.
>>
>> If it's listed as running under v1.1, change it to v1.0.
>> ( *after* you run aspnet_regiis -i ).
>>
>> To do that, select ASP.NET version 1.0,
>> and click the "Switch .Net Framework Version" button.
>>
>> I don't guarantee you results,
>> but if it works you owe me a virtual beer !
>>
>> ;-)
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:C0**********************************@microsof t.com...
>> >I right click on that file and I do get: 1.1.4322.2032.
>> >
>> > In the file you listed before:
>> > drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> > on my win2003 server:
>> > <section name="webServices"
>> > type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
>> > System.Web.Services, Version=1.0.5000.0, Culture=neutral,
>> > PublicKeyToken=b03f5f7f11d50a3a"/>
>> >
>> > On local development box (VS.net on win2k):
>> > I get the same.
>> >
>> > I do have, on my 2003 server, a v1.0.3705 framework build now that I
>> > installed 1.0. This is where I tried to create a new pooling choice
>> > using
>> > it's 'aspnet_isapi.dll' file.
>> >
>> > what about my other question? Any of this make sense? I use updater
>> > service
>> > on both the server and workstation to keep updated.
>> >
>> > thanx.
>> >
>> >
>> > I get:
>> >
>> > "Juan T. Llibre" wrote:
>> >
>> >> Version 1.1 should be 1.1.4322, not 1.0.5000.0
>> >>
>> >> If you right-click aspnet_isapi.dll in the
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>> >> directory and select "properties", and then select
>> >> the "Version" tab, doesn't it have the version number
>> >> "1.1.4322.2032" ?
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:A7**********************************@microsof t.com...
>> >> > Also, looked at my Win2003 server in the directory you list below
>> >> > /CONFIG/
>> >> > and I found:
>> >> >
>> >> > in v1.0....
>> >> > Version=1.0.3300.0
>> >> >
>> >> > in v1.1...
>> >> > Version=1.0.5000.0
>> >> >
>> >> > Is this right, I assume 1.0.5 is 1.1???? Where do you find the
>> >> > reference
>> >> > to
>> >> > 1.1 as the framework?
>> >> >
>> >> > thanx.
>> >> > "Juan T. Llibre" wrote:
>> >> >
>> >> >> Hmmm...that is a problem.
>> >> >>
>> >> >> If you take a look at
>> >> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> >> >>
>> >> >> you'll see that the references to v1.1.4322's
>> >> >> System.Web.Services are completely different.
>> >> >>
>> >> >> I'm not even sure that you can *run*
>> >> >> ..Net Framework v1.0.3705 in W2K3.
>> >> >>
>> >> >> Windows Server 2003 is the first OS which runs
>> >> >> the .Net Framework 1.1.4322 "out of the box".
>> >> >>
>> >> >> It doesn't even come with the
>> >> >> ..Net Framework v1.0.3705 installed.
>> >> >>
>> >> >> You could try to register the .Net Framework v1.0.3705,
>> >> >> if you copied the whole directory structure from the W2K box,
>> >> >> by running aspnet_regiis -i from the
>> >> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
>> >> >> quite frankly, this might screw up your system.
>> >> >>
>> >> >> It's bound to be quite a complicated, and risky, task
>> >> >> to run a deprecated version of the .Net Framework
>> >> >> in an OS which doesn't even come with it, but comes
>> >> >> with a later version.
>> >> >>
>> >> >> About the best thing I'd recommend is that VS.NET 2003
>> >> >> be installed in the *original* W2K box, and then that the
>> >> >> application be recompiled and debugged for the .Net 1.1
>> >> >> Framework.
>> >> >>
>> >> >> Then, you could copy the *Application*
>> >> >> to your W2K3 box and run it under .Net 1.1.
>> >> >>
>> >> >> best regards,
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Juan T. Llibre
>> >> >> ASP.NET MVP
>> >> >> ===========
>> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> news:AD**********************************@microsof t.com...
>> >> >> > I'm not sure if this is the issue; they're running this app on
>> >> >> > a
>> >> >> > Window
>> >> >> > 2K
>> >> >> > box and I'mnot sure but the VS.NET project file has reference
>> >> >> > to
>> >> >> > Framework
>> >> >> > 1.0, see below:
>> >> >> >
>> >> >> > <Reference Name = "System.Web.Services"
>> >> >> > AssemblyName = "System.Web.Services"
>> >> >> > HintPath =
>> >> >> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> >> >> > />
>> >> >> >
>> >> >> > My Win2003 server only has accepted to run v1.1, is that the
>> >> >> > issue?
>> >> >> > If
>> >> >> > so,
>> >> >> > do I need to install v1.0? I moved the folder over to my
>> >> >> > server
>> >> >> > for
>> >> >> > the
>> >> >> > framework.
>> >> >> >
>> >> >> > Thanx.
>> >> >> >
>> >> >> > "Juan T. Llibre" wrote:
>> >> >> >
>> >> >> >> To create an Application using a Virtual Directory
>> >> >> >> as its starting point, open the IIS Manager, scroll
>> >> >> >> down to the virtual directory, select it, and rght-click it.
>> >> >> >>
>> >> >> >> From the pop-up menu, select "Properties".
>> >> >> >>
>> >> >> >> Then, click on the "Create" button.
>> >> >> >> That will make your virtual directory an Application.
>> >> >> >>
>> >> >> >> If you do that, your error message should disappear.
>> >> >> >> Please let us know how you do.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> Juan T. Llibre
>> >> >> >> ASP.NET MVP
>> >> >> >> ===========
>> >> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> >> news:73**********************************@microsof t.com...
>> >> >> >> > I'm trying to get an existing VS.NET project up on my
>> >> >> >> > Win2003
>> >> >> >> > server
>> >> >> >> > and I
>> >> >> >> > get the following error (on the actual website page):
>> >> >> >> >
>> >> >> >> > "It is an error to use a section registered as
>> >> >> >> > allowDefinition='MachineToApplication' beyond application
>> >> >> >> > level.
>> >> >> >> > This
>> >> >> >> > error
>> >> >> >> > can be caused by a virtual directory not being configured
>> >> >> >> > as
>> >> >> >> > an
>> >> >> >> > application
>> >> >> >> > in IIS."
>> >> >> >> >
>> >> >> >> > I've been told by the previous developer that the website
>> >> >> >> > needs
>> >> >> >> > to
>> >> >> >> > be
>> >> >> >> > set
>> >> >> >> > as
>> >> >> >> > a "application". I assume this means what process it runs
>> >> >> >> > under?
>> >> >> >> > I've
>> >> >> >> > created
>> >> >> >> > a virtual directory to the location and the site can be
>> >> >> >> > seen.
>> >> >> >> > but
>> >> >> >> > I
>> >> >> >> > get
>> >> >> >> > that
>> >> >> >> > error listed above?
>> >> >> >> > The application pools are:
>> >> >> >> >
>> >> >> >> > DEFAULTAPPPOOL (default)
>> >> >> >> > MSSHAREPOINTAPPPOOL
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > What does this developer mean? Thanx
>> >>
>> >>
>> >>
>> >>
>>
>>
>>


Nov 19 '05 #18

P: n/a
Last set of questions I promise:

If I bring in the project into my VS.NET 2003 copy and recompile, will that
automaticaly copy the versions in 1.0 that are in 1.1 to 1.1?
So in theory I should be able to look at the project file and see them using
the 1.1 directory and not the 1.0 like I do now. And is there also the
assumption that if the project using 1.0 specific class, etc then they won't
be upgraded and I can see that in the project file as well.
Or do you have to "remove" each reference" then add it back thus ensuring it
to be 1.1? I.e. system.web, etc. I've looked at the project file after
re-compiling in VS2003 and they still point to 1.0.
I've used the article to response.write the version of the framework that is
running on the machine and I've confirmed 1.1.

Thanx for all your help.
"Juan T. Llibre" wrote:
re:
I don't need 1.0 on my Win2003 server.
The assumption is that the highest revision of
the framework is always backward compatible correct?


No.

Your 1.0 application may call assemblies which don't exist any more,
or whose functions have been changed in later versions.

That's why .Net versions run "side-by-side",
instead of the latest version just replacing the "old" version.

You need the *particular* version of .Net for which the application
was compiled for to be installed, and enabled, in order to be assured
of being able to run a .Net application compiled for a previous
version of the .Net Framework you've got installed.

Also, the assembly versioning in machine.config is different
for different versions of the .Net framework.

For example, see the differences between v1.1 and v2.0 :

1.1 :
<section name="webServices" type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler, System.Web.Services, Version=1.0.5000.0,

2.0 :
<section name="webServices" type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler, System.Web.Services, Version=2.0.3600.0,

Notice the difference between the Version numbers.
It's a different one for .Net 1.0, too.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message news:4A**********************************@microsof t.com...
I don't know what I was thinking, becuase I read that v1.1 is backward
compatible to v1.0, so I don't need 1.0 on my Win2003 server. If I move to
2.0 then it will have to updated on the server. The assumption is that the
highest revision of the framework is always backward compatible correct?

thanx.

"Juan T. Llibre" wrote:
If you've gotten that far, maybe you can get
v1.0.3705 to work by running aspnet_regiis -i
from the v1.0.3705 directory.

Then, you could switch the application's version,
so it runs under v1.0.3705, by running Denis Bauer's
"ASP.NET Version Switcher" to change the .net
version the Application will runs as.

http://www.denisbauer.com/NETTools/A...nSwitcher.aspx

When you run the "ASP.NET Version Switcher"
check the .net version your Application is running as.

If it's listed as running under v1.1, change it to v1.0.
( *after* you run aspnet_regiis -i ).

To do that, select ASP.NET version 1.0,
and click the "Switch .Net Framework Version" button.

I don't guarantee you results,
but if it works you owe me a virtual beer !

;-)

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:C0**********************************@microsof t.com...
>I right click on that file and I do get: 1.1.4322.2032.
>
> In the file you listed before:
> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
> on my win2003 server:
> <section name="webServices"
> type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
> System.Web.Services, Version=1.0.5000.0, Culture=neutral,
> PublicKeyToken=b03f5f7f11d50a3a"/>
>
> On local development box (VS.net on win2k):
> I get the same.
>
> I do have, on my 2003 server, a v1.0.3705 framework build now that I
> installed 1.0. This is where I tried to create a new pooling choice using
> it's 'aspnet_isapi.dll' file.
>
> what about my other question? Any of this make sense? I use updater
> service
> on both the server and workstation to keep updated.
>
> thanx.
>
>
> I get:
>
> "Juan T. Llibre" wrote:
>
>> Version 1.1 should be 1.1.4322, not 1.0.5000.0
>>
>> If you right-click aspnet_isapi.dll in the
>> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>> directory and select "properties", and then select
>> the "Version" tab, doesn't it have the version number
>> "1.1.4322.2032" ?
>>
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:A7**********************************@microsof t.com...
>> > Also, looked at my Win2003 server in the directory you list below
>> > /CONFIG/
>> > and I found:
>> >
>> > in v1.0....
>> > Version=1.0.3300.0
>> >
>> > in v1.1...
>> > Version=1.0.5000.0
>> >
>> > Is this right, I assume 1.0.5 is 1.1???? Where do you find the
>> > reference
>> > to
>> > 1.1 as the framework?
>> >
>> > thanx.
>> > "Juan T. Llibre" wrote:
>> >
>> >> Hmmm...that is a problem.
>> >>
>> >> If you take a look at
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> >>
>> >> you'll see that the references to v1.1.4322's
>> >> System.Web.Services are completely different.
>> >>
>> >> I'm not even sure that you can *run*
>> >> ..Net Framework v1.0.3705 in W2K3.
>> >>
>> >> Windows Server 2003 is the first OS which runs
>> >> the .Net Framework 1.1.4322 "out of the box".
>> >>
>> >> It doesn't even come with the
>> >> ..Net Framework v1.0.3705 installed.
>> >>
>> >> You could try to register the .Net Framework v1.0.3705,
>> >> if you copied the whole directory structure from the W2K box,
>> >> by running aspnet_regiis -i from the
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
>> >> quite frankly, this might screw up your system.
>> >>
>> >> It's bound to be quite a complicated, and risky, task
>> >> to run a deprecated version of the .Net Framework
>> >> in an OS which doesn't even come with it, but comes
>> >> with a later version.
>> >>
>> >> About the best thing I'd recommend is that VS.NET 2003
>> >> be installed in the *original* W2K box, and then that the
>> >> application be recompiled and debugged for the .Net 1.1 Framework.
>> >>
>> >> Then, you could copy the *Application*
>> >> to your W2K3 box and run it under .Net 1.1.
>> >>
>> >> best regards,
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:AD**********************************@microsof t.com...
>> >> > I'm not sure if this is the issue; they're running this app on a
>> >> > Window
>> >> > 2K
>> >> > box and I'mnot sure but the VS.NET project file has reference to
>> >> > Framework
>> >> > 1.0, see below:
>> >> >
>> >> > <Reference Name = "System.Web.Services"
>> >> > AssemblyName = "System.Web.Services"
>> >> > HintPath =
>> >> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> >> > />
>> >> >
>> >> > My Win2003 server only has accepted to run v1.1, is that the issue?
>> >> > If
>> >> > so,
>> >> > do I need to install v1.0? I moved the folder over to my server for
>> >> > the
>> >> > framework.
>> >> >
>> >> > Thanx.
>> >> >
>> >> > "Juan T. Llibre" wrote:
>> >> >
>> >> >> To create an Application using a Virtual Directory
>> >> >> as its starting point, open the IIS Manager, scroll
>> >> >> down to the virtual directory, select it, and rght-click it.
>> >> >>
>> >> >> From the pop-up menu, select "Properties".
>> >> >>
>> >> >> Then, click on the "Create" button.
>> >> >> That will make your virtual directory an Application.
>> >> >>
>> >> >> If you do that, your error message should disappear.
>> >> >> Please let us know how you do.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Juan T. Llibre
>> >> >> ASP.NET MVP
>> >> >> ===========
>> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> news:73**********************************@microsof t.com...
>> >> >> > I'm trying to get an existing VS.NET project up on my Win2003
>> >> >> > server
>> >> >> > and I
>> >> >> > get the following error (on the actual website page):
>> >> >> >
>> >> >> > "It is an error to use a section registered as
>> >> >> > allowDefinition='MachineToApplication' beyond application level.
>> >> >> > This
>> >> >> > error
>> >> >> > can be caused by a virtual directory not being configured as an
>> >> >> > application
>> >> >> > in IIS."
>> >> >> >
>> >> >> > I've been told by the previous developer that the website needs
>> >> >> > to
>> >> >> > be
>> >> >> > set
>> >> >> > as
>> >> >> > a "application". I assume this means what process it runs under?
>> >> >> > I've
>> >> >> > created
>> >> >> > a virtual directory to the location and the site can be seen. but
>> >> >> > I
>> >> >> > get
>> >> >> > that
>> >> >> > error listed above?
>> >> >> > The application pools are:
>> >> >> >
>> >> >> > DEFAULTAPPPOOL (default)
>> >> >> > MSSHAREPOINTAPPPOOL
>> >> >> >
>> >> >> >
>> >> >> > What does this developer mean? Thanx

Nov 19 '05 #19

P: n/a
I was quite intrigued by this question, and did additional research
which implies that under some conditions the .Net Framework
1.0 can be successfully installed in Windows Server 2003, and
Applications compiled and deployed for the .Net Framework 1.0
can run when deployed to a W2K3 Server.

No guarantees are given, though.

First and foremost, the .Net Framework 1.0 must have been
successfully installed ( by installing the .Net Framework redistributable
http://www.microsoft.com/downloads/d...displaylang=en
or installing a product which has it, like VS.NET 2002.

That download link installs .Net Framework version 1.0a.

Be aware that there's Service Packs which need to be applied,
and which I was not able to find at the Microsoft download center.

After the .Net Framework 1.0a has been successfully installed,
the following support pages are required reading :

Versioning, Compatibility, and Side-by-Side
Execution in the .NET Framework :
http://msdn.microsoft.com/netframewo...n/default.aspx

Side-by-Side Execution of the .NET Framework
http://msdn.microsoft.com/library/de...dexsidenet.asp

Configuring IIS 6.0 to Use the Correct
Version of the .NET Framework
http://www.microsoft.com/resources/d...g_upg_yybr.asp
This one is particularly important, as it states that
"Running versions 1.0 and 1.1 of the .NET Framework
side-by-side is only supported when IIS is configured
to run in IIS 5.0 isolation mode." , which could cause
serious inconveniences, like less reliability.

You would also have to create a separate application
pool which your 1.0 apps would use to run under.

ASP.NET supports only one version of the
..NET Framework for each application pool.

A slightly more detailed version of that page is at:
http://www.microsoft.com/resources/d...g_upg_nvpu.asp

Finally, a check should be made for possible incompatibilities
and breaking changes between the different .Net Framework
versions :

http://www.gotdotnet.com/team/changeinfo/default.aspx
http://www.gotdotnet.com/team/change...1/default.aspx

Mind you, under no circumstances interpret these pointers
as a *recommendation* that the installation of the .Net
Framework 1.0 on a W2K3 Server should be performed.

If you decide to install, configure and try to use the .Net
Framework 1.0 under W2K3 to run a .Net Framework
1.0 application, you are bound to run into many snags.

What I think is the best way to handle this, is to use a
development box which has both the .Net framework 1.0
and 1.1 installed, and which has VS.NET 2003 installed,
to recompile/debug/migrate the application to the
..NET Framework 1.1.

Then, that application will be assured of running well
under .Net Framework 1.1 and W23K Server.

Good luck with your choice.

Juan T. Llibre
ASP.NET MVP
===========
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:u9****************@TK2MSFTNGP14.phx.gbl...
re:
don't take this the wrong way


I'm not.

re:
You thought before that they shouldn't work together


They don't. See below.

re:
I did get them installed together but can't
get IIS to see the v1.0 structure.


I warned you about potential problems, didn't I ?

re:
Please don't take offense,


I haven't taken offense.

re:
I appreciate your help but need to know, thanx.


You should know, now.

re:
1.) Is it MS's position to leave 2003 at 1.1 and not to use 1.0?


See below.

re:
2.) Is win2K used for 1.0 only?


No. You can install any version of the .Net Framework on W2K.

re:
3.) Is there a MS article on using multple frameworks
on a win2003 server, not win2000?


The closest I could find is :
http://support.microsoft.com/default...b;en-us;830714

"On a Windows Server 2003 system, you must use .NET Framework 1.1."

re:
4.) Would it be better, theorically, to just update this
asp.net v1.0 app to 1.1? And what does that entail?


I already told you that was what you needed to do and how to do that.
About the best thing I'd recommend is that VS.NET 2003
be installed in the *original* W2K box, and then that the
application be recompiled and debugged for the .Net 1.1 Framework.

Then, you could copy the *Application*
to your W2K3 box and run it under .Net 1.1.


Good luck!

Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:30**********************************@microsof t.com...
don't take this the wrong way but I don't have a warm and fuzzy feeling
about
this. You thought before that they shouldn't work together, I did get
them
installed together but can't get IIS to see the v1.0 structure. Then
there is
a chance to use Denis Bauer's app to switch them, but we're not really
sure
if running on win2003 is sucj a good and stable thing. I can't get the
application I started out with to work on my win2003 server, and I'm not
feeling to sure of MS's position. I'd love to know:

1.) Is it MS's position to leave 2003 at 1.1 and not to use 1.0?
2.) Is win2K used for 1.0 only?
3.) Is there a MS article on using multple frameworks on a win2003
server,
not win2000?
4.) Would it be better, theorically, to just update this asp.net v1.0 app
to
1.1? And what does that entail?
5.) Is there a simply way to determine if an asp.net app is v1.0 or 1.1?
Check the VS.NET project file for referance paths? Anything with VS.net,
or a
file?

Please don't take offense, I appreciate your help but need to know,
thanx.

"Juan T. Llibre" wrote:
If you were able to install v1.0
( as apparently you've been able to)
running it should be no problem.

There's lot's of documentation stating tha
side-by-side running of v1.0 and v1.1 is OK.

When you *add* v1.1 to a v1.0 installation
it certainly runs OK.

I just didn't know whether running v1.0 in
W2K3 ( which runs 1.1 natively ) is OK.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:ED**********************************@microsof t.com...
> thanx, I saw his application but before I do that, can anyone at MS
> answer
> what do other developers do about Win2003 and Framework 1.0, I can't
> be
> the
> only person who has experinced this? What is the official MS word on
> the
> use
> of 1.0 and win2003?
>
> "Juan T. Llibre" wrote:
>
>> If you've gotten that far, maybe you can get
>> v1.0.3705 to work by running aspnet_regiis -i
>> from the v1.0.3705 directory.
>>
>> Then, you could switch the application's version,
>> so it runs under v1.0.3705, by running Denis Bauer's
>> "ASP.NET Version Switcher" to change the .net
>> version the Application will runs as.
>>
>> http://www.denisbauer.com/NETTools/A...nSwitcher.aspx
>>
>> When you run the "ASP.NET Version Switcher"
>> check the .net version your Application is running as.
>>
>> If it's listed as running under v1.1, change it to v1.0.
>> ( *after* you run aspnet_regiis -i ).
>>
>> To do that, select ASP.NET version 1.0,
>> and click the "Switch .Net Framework Version" button.
>>
>> I don't guarantee you results,
>> but if it works you owe me a virtual beer !
>>
>> ;-)
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:C0**********************************@microsof t.com...
>> >I right click on that file and I do get: 1.1.4322.2032.
>> >
>> > In the file you listed before:
>> > drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> > on my win2003 server:
>> > <section name="webServices"
>> > type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
>> > System.Web.Services, Version=1.0.5000.0, Culture=neutral,
>> > PublicKeyToken=b03f5f7f11d50a3a"/>
>> >
>> > On local development box (VS.net on win2k):
>> > I get the same.
>> >
>> > I do have, on my 2003 server, a v1.0.3705 framework build now that
>> > I
>> > installed 1.0. This is where I tried to create a new pooling choice
>> > using
>> > it's 'aspnet_isapi.dll' file.
>> >
>> > what about my other question? Any of this make sense? I use updater
>> > service
>> > on both the server and workstation to keep updated.
>> >
>> > thanx.
>> >
>> >
>> > I get:
>> >
>> > "Juan T. Llibre" wrote:
>> >
>> >> Version 1.1 should be 1.1.4322, not 1.0.5000.0
>> >>
>> >> If you right-click aspnet_isapi.dll in the
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>> >> directory and select "properties", and then select
>> >> the "Version" tab, doesn't it have the version number
>> >> "1.1.4322.2032" ?
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:A7**********************************@microsof t.com...
>> >> > Also, looked at my Win2003 server in the directory you list
>> >> > below
>> >> > /CONFIG/
>> >> > and I found:
>> >> >
>> >> > in v1.0....
>> >> > Version=1.0.3300.0
>> >> >
>> >> > in v1.1...
>> >> > Version=1.0.5000.0
>> >> >
>> >> > Is this right, I assume 1.0.5 is 1.1???? Where do you find the
>> >> > reference
>> >> > to
>> >> > 1.1 as the framework?
>> >> >
>> >> > thanx.
>> >> > "Juan T. Llibre" wrote:
>> >> >
>> >> >> Hmmm...that is a problem.
>> >> >>
>> >> >> If you take a look at
>> >> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> >> >>
>> >> >> you'll see that the references to v1.1.4322's
>> >> >> System.Web.Services are completely different.
>> >> >>
>> >> >> I'm not even sure that you can *run*
>> >> >> ..Net Framework v1.0.3705 in W2K3.
>> >> >>
>> >> >> Windows Server 2003 is the first OS which runs
>> >> >> the .Net Framework 1.1.4322 "out of the box".
>> >> >>
>> >> >> It doesn't even come with the
>> >> >> ..Net Framework v1.0.3705 installed.
>> >> >>
>> >> >> You could try to register the .Net Framework v1.0.3705,
>> >> >> if you copied the whole directory structure from the W2K box,
>> >> >> by running aspnet_regiis -i from the
>> >> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory
>> >> >> but,
>> >> >> quite frankly, this might screw up your system.
>> >> >>
>> >> >> It's bound to be quite a complicated, and risky, task
>> >> >> to run a deprecated version of the .Net Framework
>> >> >> in an OS which doesn't even come with it, but comes
>> >> >> with a later version.
>> >> >>
>> >> >> About the best thing I'd recommend is that VS.NET 2003
>> >> >> be installed in the *original* W2K box, and then that the
>> >> >> application be recompiled and debugged for the .Net 1.1
>> >> >> Framework.
>> >> >>
>> >> >> Then, you could copy the *Application*
>> >> >> to your W2K3 box and run it under .Net 1.1.
>> >> >>
>> >> >> best regards,
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Juan T. Llibre
>> >> >> ASP.NET MVP
>> >> >> ===========
>> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> news:AD**********************************@microsof t.com...
>> >> >> > I'm not sure if this is the issue; they're running this app
>> >> >> > on a
>> >> >> > Window
>> >> >> > 2K
>> >> >> > box and I'mnot sure but the VS.NET project file has reference
>> >> >> > to
>> >> >> > Framework
>> >> >> > 1.0, see below:
>> >> >> >
>> >> >> > <Reference Name = "System.Web.Services"
>> >> >> > AssemblyName = "System.Web.Services"
>> >> >> > HintPath =
>> >> >> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> >> >> > />
>> >> >> >
>> >> >> > My Win2003 server only has accepted to run v1.1, is that the
>> >> >> > issue?
>> >> >> > If
>> >> >> > so,
>> >> >> > do I need to install v1.0? I moved the folder over to my
>> >> >> > server
>> >> >> > for
>> >> >> > the
>> >> >> > framework.
>> >> >> >
>> >> >> > Thanx.
>> >> >> >
>> >> >> > "Juan T. Llibre" wrote:
>> >> >> >
>> >> >> >> To create an Application using a Virtual Directory
>> >> >> >> as its starting point, open the IIS Manager, scroll
>> >> >> >> down to the virtual directory, select it, and rght-click it.
>> >> >> >>
>> >> >> >> From the pop-up menu, select "Properties".
>> >> >> >>
>> >> >> >> Then, click on the "Create" button.
>> >> >> >> That will make your virtual directory an Application.
>> >> >> >>
>> >> >> >> If you do that, your error message should disappear.
>> >> >> >> Please let us know how you do.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> Juan T. Llibre
>> >> >> >> ASP.NET MVP
>> >> >> >> ===========
>> >> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> >> news:73**********************************@microsof t.com...
>> >> >> >> > I'm trying to get an existing VS.NET project up on my
>> >> >> >> > Win2003
>> >> >> >> > server
>> >> >> >> > and I
>> >> >> >> > get the following error (on the actual website page):
>> >> >> >> >
>> >> >> >> > "It is an error to use a section registered as
>> >> >> >> > allowDefinition='MachineToApplication' beyond application
>> >> >> >> > level.
>> >> >> >> > This
>> >> >> >> > error
>> >> >> >> > can be caused by a virtual directory not being configured
>> >> >> >> > as
>> >> >> >> > an
>> >> >> >> > application
>> >> >> >> > in IIS."
>> >> >> >> >
>> >> >> >> > I've been told by the previous developer that the website
>> >> >> >> > needs
>> >> >> >> > to
>> >> >> >> > be
>> >> >> >> > set
>> >> >> >> > as
>> >> >> >> > a "application". I assume this means what process it runs
>> >> >> >> > under?
>> >> >> >> > I've
>> >> >> >> > created
>> >> >> >> > a virtual directory to the location and the site can be
>> >> >> >> > seen.
>> >> >> >> > but
>> >> >> >> > I
>> >> >> >> > get
>> >> >> >> > that
>> >> >> >> > error listed above?
>> >> >> >> > The application pools are:
>> >> >> >> >
>> >> >> >> > DEFAULTAPPPOOL (default)
>> >> >> >> > MSSHAREPOINTAPPPOOL
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > What does this developer mean? Thanx
>> >>
>> >>
>> >>
>> >>
>>
>>
>>


Nov 19 '05 #20

P: n/a
OK...

If you open the VS.NET 2002 project in VS.NET 2003,
VS.NET 2003 will attempt to convert the project
and report back any problems which it found.

It also should create a backup of your 2002 project files.

Then, when you attempt the build, you may find build errors.
You would then have to determine the correct way to fix them.

What I would do is *not* try to open the old project.

I'd create a new, empty, web project, in VS.NET 2003,
and use the "add existing items" feature of VS.NET
to thenew project.

Then, I'd look in the previous project's VS.NET project file,
identify the references which don't exist in the empty
project, and add them to the new project.

That would ensure that the references are correct for .Net 1.1

Then, I'd compile the new version in VS.NET 2003.

You still might get build errors which you'd have to fix,
but you won't be saddled with conversion problems
should there be any.

Another thing to watch out for is whether the "old" project
had sub-projects in it.

Some web applications use more than one project.
You'd have add the additional projects, too, if there's any.

Hopefully it's a one-project solution and it'd be simpler.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:CB**********************************@microsof t.com...
Last set of questions I promise:

If I bring in the project into my VS.NET 2003 copy and recompile, will
that
automaticaly copy the versions in 1.0 that are in 1.1 to 1.1?
So in theory I should be able to look at the project file and see them
using
the 1.1 directory and not the 1.0 like I do now. And is there also the
assumption that if the project using 1.0 specific class, etc then they
won't
be upgraded and I can see that in the project file as well.
Or do you have to "remove" each reference" then add it back thus ensuring
it
to be 1.1? I.e. system.web, etc. I've looked at the project file after
re-compiling in VS2003 and they still point to 1.0.
I've used the article to response.write the version of the framework that
is
running on the machine and I've confirmed 1.1.

Thanx for all your help.
"Juan T. Llibre" wrote:
re:
> I don't need 1.0 on my Win2003 server.
> The assumption is that the highest revision of
> the framework is always backward compatible correct?


No.

Your 1.0 application may call assemblies which don't exist any more,
or whose functions have been changed in later versions.

That's why .Net versions run "side-by-side",
instead of the latest version just replacing the "old" version.

You need the *particular* version of .Net for which the application
was compiled for to be installed, and enabled, in order to be assured
of being able to run a .Net application compiled for a previous
version of the .Net Framework you've got installed.

Also, the assembly versioning in machine.config is different
for different versions of the .Net framework.

For example, see the differences between v1.1 and v2.0 :

1.1 :
<section name="webServices"
type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
System.Web.Services, Version=1.0.5000.0,

2.0 :
<section name="webServices"
type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
System.Web.Services, Version=2.0.3600.0,

Notice the difference between the Version numbers.
It's a different one for .Net 1.0, too.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:4A**********************************@microsof t.com...
>I don't know what I was thinking, becuase I read that v1.1 is backward
> compatible to v1.0, so I don't need 1.0 on my Win2003 server. If I move
> to
> 2.0 then it will have to updated on the server. The assumption is that
> the
> highest revision of the framework is always backward compatible
> correct?
>
> thanx.

> "Juan T. Llibre" wrote:
>
>> If you've gotten that far, maybe you can get
>> v1.0.3705 to work by running aspnet_regiis -i
>> from the v1.0.3705 directory.
>>
>> Then, you could switch the application's version,
>> so it runs under v1.0.3705, by running Denis Bauer's
>> "ASP.NET Version Switcher" to change the .net
>> version the Application will runs as.
>>
>> http://www.denisbauer.com/NETTools/A...nSwitcher.aspx
>>
>> When you run the "ASP.NET Version Switcher"
>> check the .net version your Application is running as.
>>
>> If it's listed as running under v1.1, change it to v1.0.
>> ( *after* you run aspnet_regiis -i ).
>>
>> To do that, select ASP.NET version 1.0,
>> and click the "Switch .Net Framework Version" button.
>>
>> I don't guarantee you results,
>> but if it works you owe me a virtual beer !
>>
>> ;-)
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:C0**********************************@microsof t.com...
>> >I right click on that file and I do get: 1.1.4322.2032.
>> >
>> > In the file you listed before:
>> > drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> > on my win2003 server:
>> > <section name="webServices"
>> > type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
>> > System.Web.Services, Version=1.0.5000.0, Culture=neutral,
>> > PublicKeyToken=b03f5f7f11d50a3a"/>
>> >
>> > On local development box (VS.net on win2k):
>> > I get the same.
>> >
>> > I do have, on my 2003 server, a v1.0.3705 framework build now that I
>> > installed 1.0. This is where I tried to create a new pooling choice
>> > using
>> > it's 'aspnet_isapi.dll' file.
>> >
>> > what about my other question? Any of this make sense? I use updater
>> > service
>> > on both the server and workstation to keep updated.
>> >
>> > thanx.
>> >
>> >
>> > I get:
>> >
>> > "Juan T. Llibre" wrote:
>> >
>> >> Version 1.1 should be 1.1.4322, not 1.0.5000.0
>> >>
>> >> If you right-click aspnet_isapi.dll in the
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>> >> directory and select "properties", and then select
>> >> the "Version" tab, doesn't it have the version number
>> >> "1.1.4322.2032" ?
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:A7**********************************@microsof t.com...
>> >> > Also, looked at my Win2003 server in the directory you list below
>> >> > /CONFIG/
>> >> > and I found:
>> >> >
>> >> > in v1.0....
>> >> > Version=1.0.3300.0
>> >> >
>> >> > in v1.1...
>> >> > Version=1.0.5000.0
>> >> >
>> >> > Is this right, I assume 1.0.5 is 1.1???? Where do you find the
>> >> > reference
>> >> > to
>> >> > 1.1 as the framework?
>> >> >
>> >> > thanx.
>> >> > "Juan T. Llibre" wrote:
>> >> >
>> >> >> Hmmm...that is a problem.
>> >> >>
>> >> >> If you take a look at
>> >> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> >> >>
>> >> >> you'll see that the references to v1.1.4322's
>> >> >> System.Web.Services are completely different.
>> >> >>
>> >> >> I'm not even sure that you can *run*
>> >> >> ..Net Framework v1.0.3705 in W2K3.
>> >> >>
>> >> >> Windows Server 2003 is the first OS which runs
>> >> >> the .Net Framework 1.1.4322 "out of the box".
>> >> >>
>> >> >> It doesn't even come with the
>> >> >> ..Net Framework v1.0.3705 installed.
>> >> >>
>> >> >> You could try to register the .Net Framework v1.0.3705,
>> >> >> if you copied the whole directory structure from the W2K box,
>> >> >> by running aspnet_regiis -i from the
>> >> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory but,
>> >> >> quite frankly, this might screw up your system.
>> >> >>
>> >> >> It's bound to be quite a complicated, and risky, task
>> >> >> to run a deprecated version of the .Net Framework
>> >> >> in an OS which doesn't even come with it, but comes
>> >> >> with a later version.
>> >> >>
>> >> >> About the best thing I'd recommend is that VS.NET 2003
>> >> >> be installed in the *original* W2K box, and then that the
>> >> >> application be recompiled and debugged for the .Net 1.1
>> >> >> Framework.
>> >> >>
>> >> >> Then, you could copy the *Application*
>> >> >> to your W2K3 box and run it under .Net 1.1.
>> >> >>
>> >> >> best regards,
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Juan T. Llibre
>> >> >> ASP.NET MVP
>> >> >> ===========
>> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> news:AD**********************************@microsof t.com...
>> >> >> > I'm not sure if this is the issue; they're running this app on
>> >> >> > a
>> >> >> > Window
>> >> >> > 2K
>> >> >> > box and I'mnot sure but the VS.NET project file has reference
>> >> >> > to
>> >> >> > Framework
>> >> >> > 1.0, see below:
>> >> >> >
>> >> >> > <Reference Name = "System.Web.Services"
>> >> >> > AssemblyName = "System.Web.Services"
>> >> >> > HintPath =
>> >> >> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> >> >> > />
>> >> >> >
>> >> >> > My Win2003 server only has accepted to run v1.1, is that the
>> >> >> > issue?
>> >> >> > If
>> >> >> > so,
>> >> >> > do I need to install v1.0? I moved the folder over to my
>> >> >> > server for
>> >> >> > the
>> >> >> > framework.
>> >> >> >
>> >> >> > Thanx.
>> >> >> >
>> >> >> > "Juan T. Llibre" wrote:
>> >> >> >
>> >> >> >> To create an Application using a Virtual Directory
>> >> >> >> as its starting point, open the IIS Manager, scroll
>> >> >> >> down to the virtual directory, select it, and rght-click it.
>> >> >> >>
>> >> >> >> From the pop-up menu, select "Properties".
>> >> >> >>
>> >> >> >> Then, click on the "Create" button.
>> >> >> >> That will make your virtual directory an Application.
>> >> >> >>
>> >> >> >> If you do that, your error message should disappear.
>> >> >> >> Please let us know how you do.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> Juan T. Llibre
>> >> >> >> ASP.NET MVP
>> >> >> >> ===========
>> >> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> >> news:73**********************************@microsof t.com...
>> >> >> >> > I'm trying to get an existing VS.NET project up on my
>> >> >> >> > Win2003
>> >> >> >> > server
>> >> >> >> > and I
>> >> >> >> > get the following error (on the actual website page):
>> >> >> >> >
>> >> >> >> > "It is an error to use a section registered as
>> >> >> >> > allowDefinition='MachineToApplication' beyond application
>> >> >> >> > level.
>> >> >> >> > This
>> >> >> >> > error
>> >> >> >> > can be caused by a virtual directory not being configured
>> >> >> >> > as an
>> >> >> >> > application
>> >> >> >> > in IIS."
>> >> >> >> >
>> >> >> >> > I've been told by the previous developer that the website
>> >> >> >> > needs
>> >> >> >> > to
>> >> >> >> > be
>> >> >> >> > set
>> >> >> >> > as
>> >> >> >> > a "application". I assume this means what process it runs
>> >> >> >> > under?
>> >> >> >> > I've
>> >> >> >> > created
>> >> >> >> > a virtual directory to the location and the site can be
>> >> >> >> > seen. but
>> >> >> >> > I
>> >> >> >> > get
>> >> >> >> > that
>> >> >> >> > error listed above?
>> >> >> >> > The application pools are:
>> >> >> >> >
>> >> >> >> > DEFAULTAPPPOOL (default)
>> >> >> >> > MSSHAREPOINTAPPPOOL
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > What does this developer mean? Thanx

Nov 19 '05 #21

P: n/a
re:
I'd create a new, empty, web project, in VS.NET 2003,
and use the "add existing items" feature of VS.NET
to thenew project.
That should read :

I'd create a new, empty, web project, in VS.NET 2003,
and use the "add existing items" feature of VS.NET
to add the source files in the old project, one by one,
to the new project.

Juan T. Llibre
ASP.NET MVP
===========
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:es**************@TK2MSFTNGP14.phx.gbl... OK...

If you open the VS.NET 2002 project in VS.NET 2003,
VS.NET 2003 will attempt to convert the project
and report back any problems which it found.

It also should create a backup of your 2002 project files.

Then, when you attempt the build, you may find build errors.
You would then have to determine the correct way to fix them.

What I would do is *not* try to open the old project.

I'd create a new, empty, web project, in VS.NET 2003,
and use the "add existing items" feature of VS.NET
to thenew project.

Then, I'd look in the previous project's VS.NET project file,
identify the references which don't exist in the empty
project, and add them to the new project.

That would ensure that the references are correct for .Net 1.1

Then, I'd compile the new version in VS.NET 2003.

You still might get build errors which you'd have to fix,
but you won't be saddled with conversion problems
should there be any.

Another thing to watch out for is whether the "old" project
had sub-projects in it.

Some web applications use more than one project.
You'd have add the additional projects, too, if there's any.

Hopefully it's a one-project solution and it'd be simpler.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:CB**********************************@microsof t.com...
Last set of questions I promise:

If I bring in the project into my VS.NET 2003 copy and recompile, will
that
automaticaly copy the versions in 1.0 that are in 1.1 to 1.1?
So in theory I should be able to look at the project file and see them
using
the 1.1 directory and not the 1.0 like I do now. And is there also the
assumption that if the project using 1.0 specific class, etc then they
won't
be upgraded and I can see that in the project file as well.
Or do you have to "remove" each reference" then add it back thus ensuring
it
to be 1.1? I.e. system.web, etc. I've looked at the project file after
re-compiling in VS2003 and they still point to 1.0.
I've used the article to response.write the version of the framework that
is
running on the machine and I've confirmed 1.1.

Thanx for all your help.
"Juan T. Llibre" wrote:
re:
> I don't need 1.0 on my Win2003 server.
> The assumption is that the highest revision of
> the framework is always backward compatible correct?

No.

Your 1.0 application may call assemblies which don't exist any more,
or whose functions have been changed in later versions.

That's why .Net versions run "side-by-side",
instead of the latest version just replacing the "old" version.

You need the *particular* version of .Net for which the application
was compiled for to be installed, and enabled, in order to be assured
of being able to run a .Net application compiled for a previous
version of the .Net Framework you've got installed.

Also, the assembly versioning in machine.config is different
for different versions of the .Net framework.

For example, see the differences between v1.1 and v2.0 :

1.1 :
<section name="webServices"
type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
System.Web.Services, Version=1.0.5000.0,

2.0 :
<section name="webServices"
type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
System.Web.Services, Version=2.0.3600.0,

Notice the difference between the Version numbers.
It's a different one for .Net 1.0, too.


Juan T. Llibre
ASP.NET MVP
===========
"Chris" <Ch***@discussions.microsoft.com> wrote in message
news:4A**********************************@microsof t.com...
>I don't know what I was thinking, becuase I read that v1.1 is backward
> compatible to v1.0, so I don't need 1.0 on my Win2003 server. If I
> move to
> 2.0 then it will have to updated on the server. The assumption is that
> the
> highest revision of the framework is always backward compatible
> correct?
>
> thanx.

> "Juan T. Llibre" wrote:
>
>> If you've gotten that far, maybe you can get
>> v1.0.3705 to work by running aspnet_regiis -i
>> from the v1.0.3705 directory.
>>
>> Then, you could switch the application's version,
>> so it runs under v1.0.3705, by running Denis Bauer's
>> "ASP.NET Version Switcher" to change the .net
>> version the Application will runs as.
>>
>> http://www.denisbauer.com/NETTools/A...nSwitcher.aspx
>>
>> When you run the "ASP.NET Version Switcher"
>> check the .net version your Application is running as.
>>
>> If it's listed as running under v1.1, change it to v1.0.
>> ( *after* you run aspnet_regiis -i ).
>>
>> To do that, select ASP.NET version 1.0,
>> and click the "Switch .Net Framework Version" button.
>>
>> I don't guarantee you results,
>> but if it works you owe me a virtual beer !
>>
>> ;-)
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> news:C0**********************************@microsof t.com...
>> >I right click on that file and I do get: 1.1.4322.2032.
>> >
>> > In the file you listed before:
>> > drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> > on my win2003 server:
>> > <section name="webServices"
>> > type="System.Web.Services.Configuration.WebService sConfigurationSectionHandler,
>> > System.Web.Services, Version=1.0.5000.0, Culture=neutral,
>> > PublicKeyToken=b03f5f7f11d50a3a"/>
>> >
>> > On local development box (VS.net on win2k):
>> > I get the same.
>> >
>> > I do have, on my 2003 server, a v1.0.3705 framework build now that
>> > I
>> > installed 1.0. This is where I tried to create a new pooling choice
>> > using
>> > it's 'aspnet_isapi.dll' file.
>> >
>> > what about my other question? Any of this make sense? I use updater
>> > service
>> > on both the server and workstation to keep updated.
>> >
>> > thanx.
>> >
>> >
>> > I get:
>> >
>> > "Juan T. Llibre" wrote:
>> >
>> >> Version 1.1 should be 1.1.4322, not 1.0.5000.0
>> >>
>> >> If you right-click aspnet_isapi.dll in the
>> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>> >> directory and select "properties", and then select
>> >> the "Version" tab, doesn't it have the version number
>> >> "1.1.4322.2032" ?
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre
>> >> ASP.NET MVP
>> >> ===========
>> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> news:A7**********************************@microsof t.com...
>> >> > Also, looked at my Win2003 server in the directory you list
>> >> > below
>> >> > /CONFIG/
>> >> > and I found:
>> >> >
>> >> > in v1.0....
>> >> > Version=1.0.3300.0
>> >> >
>> >> > in v1.1...
>> >> > Version=1.0.5000.0
>> >> >
>> >> > Is this right, I assume 1.0.5 is 1.1???? Where do you find the
>> >> > reference
>> >> > to
>> >> > 1.1 as the framework?
>> >> >
>> >> > thanx.
>> >> > "Juan T. Llibre" wrote:
>> >> >
>> >> >> Hmmm...that is a problem.
>> >> >>
>> >> >> If you take a look at
>> >> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\C ONFIG\machine.config
>> >> >>
>> >> >> you'll see that the references to v1.1.4322's
>> >> >> System.Web.Services are completely different.
>> >> >>
>> >> >> I'm not even sure that you can *run*
>> >> >> ..Net Framework v1.0.3705 in W2K3.
>> >> >>
>> >> >> Windows Server 2003 is the first OS which runs
>> >> >> the .Net Framework 1.1.4322 "out of the box".
>> >> >>
>> >> >> It doesn't even come with the
>> >> >> ..Net Framework v1.0.3705 installed.
>> >> >>
>> >> >> You could try to register the .Net Framework v1.0.3705,
>> >> >> if you copied the whole directory structure from the W2K box,
>> >> >> by running aspnet_regiis -i from the
>> >> >> drive:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ directory
>> >> >> but,
>> >> >> quite frankly, this might screw up your system.
>> >> >>
>> >> >> It's bound to be quite a complicated, and risky, task
>> >> >> to run a deprecated version of the .Net Framework
>> >> >> in an OS which doesn't even come with it, but comes
>> >> >> with a later version.
>> >> >>
>> >> >> About the best thing I'd recommend is that VS.NET 2003
>> >> >> be installed in the *original* W2K box, and then that the
>> >> >> application be recompiled and debugged for the .Net 1.1
>> >> >> Framework.
>> >> >>
>> >> >> Then, you could copy the *Application*
>> >> >> to your W2K3 box and run it under .Net 1.1.
>> >> >>
>> >> >> best regards,
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Juan T. Llibre
>> >> >> ASP.NET MVP
>> >> >> ===========
>> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> news:AD**********************************@microsof t.com...
>> >> >> > I'm not sure if this is the issue; they're running this app
>> >> >> > on a
>> >> >> > Window
>> >> >> > 2K
>> >> >> > box and I'mnot sure but the VS.NET project file has reference
>> >> >> > to
>> >> >> > Framework
>> >> >> > 1.0, see below:
>> >> >> >
>> >> >> > <Reference Name = "System.Web.Services"
>> >> >> > AssemblyName = "System.Web.Services"
>> >> >> > HintPath =
>> >> >> > "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\ System.Web.Services.dll"
>> >> >> > />
>> >> >> >
>> >> >> > My Win2003 server only has accepted to run v1.1, is that the
>> >> >> > issue?
>> >> >> > If
>> >> >> > so,
>> >> >> > do I need to install v1.0? I moved the folder over to my
>> >> >> > server for
>> >> >> > the
>> >> >> > framework.
>> >> >> >
>> >> >> > Thanx.
>> >> >> >
>> >> >> > "Juan T. Llibre" wrote:
>> >> >> >
>> >> >> >> To create an Application using a Virtual Directory
>> >> >> >> as its starting point, open the IIS Manager, scroll
>> >> >> >> down to the virtual directory, select it, and rght-click it.
>> >> >> >>
>> >> >> >> From the pop-up menu, select "Properties".
>> >> >> >>
>> >> >> >> Then, click on the "Create" button.
>> >> >> >> That will make your virtual directory an Application.
>> >> >> >>
>> >> >> >> If you do that, your error message should disappear.
>> >> >> >> Please let us know how you do.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> Juan T. Llibre
>> >> >> >> ASP.NET MVP
>> >> >> >> ===========
>> >> >> >> "Chris" <Ch***@discussions.microsoft.com> wrote in message
>> >> >> >> news:73**********************************@microsof t.com...
>> >> >> >> > I'm trying to get an existing VS.NET project up on my
>> >> >> >> > Win2003
>> >> >> >> > server
>> >> >> >> > and I
>> >> >> >> > get the following error (on the actual website page):
>> >> >> >> >
>> >> >> >> > "It is an error to use a section registered as
>> >> >> >> > allowDefinition='MachineToApplication' beyond application
>> >> >> >> > level.
>> >> >> >> > This
>> >> >> >> > error
>> >> >> >> > can be caused by a virtual directory not being configured
>> >> >> >> > as an
>> >> >> >> > application
>> >> >> >> > in IIS."
>> >> >> >> >
>> >> >> >> > I've been told by the previous developer that the website
>> >> >> >> > needs
>> >> >> >> > to
>> >> >> >> > be
>> >> >> >> > set
>> >> >> >> > as
>> >> >> >> > a "application". I assume this means what process it runs
>> >> >> >> > under?
>> >> >> >> > I've
>> >> >> >> > created
>> >> >> >> > a virtual directory to the location and the site can be
>> >> >> >> > seen. but
>> >> >> >> > I
>> >> >> >> > get
>> >> >> >> > that
>> >> >> >> > error listed above?
>> >> >> >> > The application pools are:
>> >> >> >> >
>> >> >> >> > DEFAULTAPPPOOL (default)
>> >> >> >> > MSSHAREPOINTAPPPOOL
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > What does this developer mean? Thanx


Nov 19 '05 #22

This discussion thread is closed

Replies have been disabled for this discussion.