473,326 Members | 2,337 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,326 software developers and data experts.

Nested Web sites in Visual Studio 2005

jdn
I have a root application that has various sub-applications (subdirectories
set up as applications within IIS). All of the sub-applications rely on the
root application for profiles, membership, etc.

This all worked fine for a bit, but now, I get an error when trying to build
the root site:

"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."

The subdirectory is configured as an application in IIS.

I also need to have separate global.asax pages for the root application and
the sub-applications, and Visual Studio doesn't seem to like this either.

How can I get this to work?

TIA,
jdn
Jan 20 '06 #1
8 1518
jdn
I was able to resolve the issue, though it isn't totally satisfactory.

If you add a web site (new or existing) in Visual Studio 2005, you have
three options: File System, IIS, FTP.

I don't know about the FTP option, but if you use the File System option,
the problem comes up. No sub-applications are recognized as such by VS
2005, no matter how they are configured in IIS.

If you use the IIS option, things are fine. So, if you have code that isn't
in the inetpub\wwwroot folder, set up the web site within IIS to point to
the folder where it resides, and then add the site to VS 2005 using the IIS
option. It will then see any sub-applications as applications.

This shouldn't be the case, in my opinion. Even a File System web site
should see the IIS settings. But, this is a workable workaround. You will
need to add any of the sub-applications as separate web sites to VS 2005 in
order to work on them (in the root application, they simply appear with a
special icon).

jdn

"jdn" <ki******@earthlink.net> wrote in message
news:eK**************@TK2MSFTNGP14.phx.gbl...
I have a root application that has various sub-applications (subdirectories
set up as applications within IIS). All of the sub-applications rely on
the root application for profiles, membership, etc.

This all worked fine for a bit, but now, I get an error when trying to
build the root site:

"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."

The subdirectory is configured as an application in IIS.

I also need to have separate global.asax pages for the root application
and the sub-applications, and Visual Studio doesn't seem to like this
either.

How can I get this to work?

TIA,
jdn

Jan 22 '06 #2
On Sat, 21 Jan 2006 19:06:43 -0600, "jdn" <ki******@earthlink.net>
wrote:
I was able to resolve the issue, though it isn't totally satisfactory.

If you add a web site (new or existing) in Visual Studio 2005, you have
three options: File System, IIS, FTP.

I don't know about the FTP option, but if you use the File System option,
the problem comes up. No sub-applications are recognized as such by VS
2005, no matter how they are configured in IIS.

If you use the IIS option, things are fine. So, if you have code that isn't
in the inetpub\wwwroot folder, set up the web site within IIS to point to
the folder where it resides, and then add the site to VS 2005 using the IIS
option. It will then see any sub-applications as applications.

This shouldn't be the case, in my opinion. Even a File System web site
should see the IIS settings. But, this is a workable workaround. You will
need to add any of the sub-applications as separate web sites to VS 2005 in
order to work on them (in the root application, they simply appear with a
special icon).

jdn


Hi,

This isn't a bug. In order to recognize application in IIS, Visual
Studio has to read the metabase and display file and folder structure
according to what is there. Obviously, this doesn't apply in a file
system project.
Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche
Jan 22 '06 #3
jdn

"Jim Cheshire" <no****@nomail.com> wrote in message
news:02********************************@4ax.com...
On Sat, 21 Jan 2006 19:06:43 -0600, "jdn" <ki******@earthlink.net>
wrote:
I was able to resolve the issue, though it isn't totally satisfactory.

If you add a web site (new or existing) in Visual Studio 2005, you have
three options: File System, IIS, FTP.

I don't know about the FTP option, but if you use the File System option,
the problem comes up. No sub-applications are recognized as such by VS
2005, no matter how they are configured in IIS.

If you use the IIS option, things are fine. So, if you have code that
isn't
in the inetpub\wwwroot folder, set up the web site within IIS to point to
the folder where it resides, and then add the site to VS 2005 using the
IIS
option. It will then see any sub-applications as applications.

This shouldn't be the case, in my opinion. Even a File System web site
should see the IIS settings. But, this is a workable workaround. You
will
need to add any of the sub-applications as separate web sites to VS 2005
in
order to work on them (in the root application, they simply appear with a
special icon).

jdn


Hi,

This isn't a bug. In order to recognize application in IIS, Visual
Studio has to read the metabase and display file and folder structure
according to what is there. Obviously, this doesn't apply in a file
system project.
Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche


I disagree. You shouldn't have a set of sites that WORK and have VS 2005
tell you that you can't build correctly.

I can't imagine it would be impossible to add the capability to do this.

At least you didn't call it a feature.

jdn
Jan 23 '06 #4
Okay, I will call it a feature. One of the purposes of the File System
option within VS 2005 is because some computers will not be able to have IIS
installed. In some corporate environments, IIS is not allowed on local
workstations, even this may be their development environment. Additionally,
some developers only have access to XP Home which does not come with IIS.
So, the File System option provides web developers the ability to test their
website with a standalone web server.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"jdn" <ki******@earthlink.net> wrote in message
news:uC**************@TK2MSFTNGP15.phx.gbl...

"Jim Cheshire" <no****@nomail.com> wrote in message
news:02********************************@4ax.com...
On Sat, 21 Jan 2006 19:06:43 -0600, "jdn" <ki******@earthlink.net>
wrote:
I was able to resolve the issue, though it isn't totally satisfactory.

If you add a web site (new or existing) in Visual Studio 2005, you have
three options: File System, IIS, FTP.

I don't know about the FTP option, but if you use the File System option,
the problem comes up. No sub-applications are recognized as such by VS
2005, no matter how they are configured in IIS.

If you use the IIS option, things are fine. So, if you have code that
isn't
in the inetpub\wwwroot folder, set up the web site within IIS to point to
the folder where it resides, and then add the site to VS 2005 using the
IIS
option. It will then see any sub-applications as applications.

This shouldn't be the case, in my opinion. Even a File System web site
should see the IIS settings. But, this is a workable workaround. You
will
need to add any of the sub-applications as separate web sites to VS 2005
in
order to work on them (in the root application, they simply appear with a
special icon).

jdn


Hi,

This isn't a bug. In order to recognize application in IIS, Visual
Studio has to read the metabase and display file and folder structure
according to what is there. Obviously, this doesn't apply in a file
system project.
Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche


I disagree. You shouldn't have a set of sites that WORK and have VS 2005
tell you that you can't build correctly.

I can't imagine it would be impossible to add the capability to do this.

At least you didn't call it a feature.

jdn

Jan 23 '06 #5
jdn
Then they should have found a way to be able to remove project files (where
they could have stored the required information) and yet not have this
happen.

I would call it maybe a design flaw then, instead of a bug.

I don't think it makes sense to be able to write perfectly functional, legal
code, which functions within a file system project and have the IDE say the
site can't be built.

jdn
"Christopher Reed" <ca****@nospam.nospam> wrote in message
news:eT**************@TK2MSFTNGP15.phx.gbl...
Okay, I will call it a feature. One of the purposes of the File System
option within VS 2005 is because some computers will not be able to have
IIS installed. In some corporate environments, IIS is not allowed on
local workstations, even this may be their development environment.
Additionally, some developers only have access to XP Home which does not
come with IIS. So, the File System option provides web developers the
ability to test their website with a standalone web server.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"jdn" <ki******@earthlink.net> wrote in message
news:uC**************@TK2MSFTNGP15.phx.gbl...

"Jim Cheshire" <no****@nomail.com> wrote in message
news:02********************************@4ax.com...
On Sat, 21 Jan 2006 19:06:43 -0600, "jdn" <ki******@earthlink.net>
wrote:

I was able to resolve the issue, though it isn't totally satisfactory.

If you add a web site (new or existing) in Visual Studio 2005, you have
three options: File System, IIS, FTP.

I don't know about the FTP option, but if you use the File System
option,
the problem comes up. No sub-applications are recognized as such by VS
2005, no matter how they are configured in IIS.

If you use the IIS option, things are fine. So, if you have code that
isn't
in the inetpub\wwwroot folder, set up the web site within IIS to point
to
the folder where it resides, and then add the site to VS 2005 using the
IIS
option. It will then see any sub-applications as applications.

This shouldn't be the case, in my opinion. Even a File System web site
should see the IIS settings. But, this is a workable workaround. You
will
need to add any of the sub-applications as separate web sites to VS 2005
in
order to work on them (in the root application, they simply appear with
a
special icon).

jdn
Hi,

This isn't a bug. In order to recognize application in IIS, Visual
Studio has to read the metabase and display file and folder structure
according to what is there. Obviously, this doesn't apply in a file
system project.
Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche


I disagree. You shouldn't have a set of sites that WORK and have VS 2005
tell you that you can't build correctly.

I can't imagine it would be impossible to add the capability to do this.

At least you didn't call it a feature.

jdn


Jan 25 '06 #6
On Tue, 24 Jan 2006 19:33:13 -0600, "jdn" <ki******@earthlink.net>
wrote:
Then they should have found a way to be able to remove project files (where
they could have stored the required information) and yet not have this
happen.

I would call it maybe a design flaw then, instead of a bug.

I don't think it makes sense to be able to write perfectly functional, legal
code, which functions within a file system project and have the IDE say the
site can't be built.


File system mode was meant to work against the ASP.NET Development
Server. You can, of course, use it to open content that's in physical
folders in the IIS web site structure, but in doing so, you have to
accept the fact that File System projects do not enumerate the
metabase because they are . . . well, file system projects.

Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche
Jan 25 '06 #7
There's a distinct difference between being able to "write perfectly
functional, legal code" and "have the IDE say the site can't be built".
Just because the individual pieces work doesn't mean that the website will.
If the files cannot be compiled together, then your website cannot function.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"jdn" <ki******@earthlink.net> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Then they should have found a way to be able to remove project files
(where they could have stored the required information) and yet not have
this happen.

I would call it maybe a design flaw then, instead of a bug.

I don't think it makes sense to be able to write perfectly functional,
legal code, which functions within a file system project and have the IDE
say the site can't be built.

jdn
"Christopher Reed" <ca****@nospam.nospam> wrote in message
news:eT**************@TK2MSFTNGP15.phx.gbl...
Okay, I will call it a feature. One of the purposes of the File System
option within VS 2005 is because some computers will not be able to have
IIS installed. In some corporate environments, IIS is not allowed on
local workstations, even this may be their development environment.
Additionally, some developers only have access to XP Home which does not
come with IIS. So, the File System option provides web developers the
ability to test their website with a standalone web server.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"jdn" <ki******@earthlink.net> wrote in message
news:uC**************@TK2MSFTNGP15.phx.gbl...

"Jim Cheshire" <no****@nomail.com> wrote in message
news:02********************************@4ax.com...
On Sat, 21 Jan 2006 19:06:43 -0600, "jdn" <ki******@earthlink.net>
wrote:

>I was able to resolve the issue, though it isn't totally satisfactory.
>
>If you add a web site (new or existing) in Visual Studio 2005, you have
>three options: File System, IIS, FTP.
>
>I don't know about the FTP option, but if you use the File System
>option,
>the problem comes up. No sub-applications are recognized as such by VS
>2005, no matter how they are configured in IIS.
>
>If you use the IIS option, things are fine. So, if you have code that
>isn't
>in the inetpub\wwwroot folder, set up the web site within IIS to point
>to
>the folder where it resides, and then add the site to VS 2005 using the
>IIS
>option. It will then see any sub-applications as applications.
>
>This shouldn't be the case, in my opinion. Even a File System web site
>should see the IIS settings. But, this is a workable workaround. You
>will
>need to add any of the sub-applications as separate web sites to VS
>2005 in
>order to work on them (in the root application, they simply appear with
>a
>special icon).
>
>jdn
>

Hi,

This isn't a bug. In order to recognize application in IIS, Visual
Studio has to read the metabase and display file and folder structure
according to what is there. Obviously, this doesn't apply in a file
system project.
Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche

I disagree. You shouldn't have a set of sites that WORK and have VS
2005 tell you that you can't build correctly.

I can't imagine it would be impossible to add the capability to do this.

At least you didn't call it a feature.

jdn



Jan 25 '06 #8
jdn

"Jim Cheshire" <no****@nomail.com> wrote in message
news:qi********************************@4ax.com...
On Tue, 24 Jan 2006 19:33:13 -0600, "jdn" <ki******@earthlink.net>
wrote:
Then they should have found a way to be able to remove project files
(where
they could have stored the required information) and yet not have this
happen.

I would call it maybe a design flaw then, instead of a bug.

I don't think it makes sense to be able to write perfectly functional,
legal
code, which functions within a file system project and have the IDE say
the
site can't be built.


File system mode was meant to work against the ASP.NET Development
Server. You can, of course, use it to open content that's in physical
folders in the IIS web site structure, but in doing so, you have to
accept the fact that File System projects do not enumerate the
metabase because they are . . . well, file system projects.

Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche


All the more reason to bring back project files then, I would think.

<shrug>

jdn
Jan 26 '06 #9

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

2
by: Marcus | last post by:
I have seen many posts of people with the same problem as me (attached below), but I have yet to see any solutions posted. Has anyone figured out how to deploy an Asp.net web site to the webserver...
4
by: Christopher J. Walker | last post by:
Hello, I am trying to create a website on port 8888 with VisualStuidio 2005. When I go to create a new project or migrate from an old one, everything seems to work fine, but when I go to build...
8
by: William LaMartin | last post by:
I just received my Visual Studio upgrade to 2005 and tried to create a new web site via File | New Web Site with location http. Unfortunately I received the following error: "Visual Web...
0
by: William LaMartin | last post by:
It was suggested that I post this query here rather than in the Microsoft.public.dotnet.languages.vb group. I just received my Visual Studio upgrade to 2005 Pro and tried to create a new web...
54
by: m.roello | last post by:
In the book: "Working with Microsoft Visual Studio 2005" Craig Skibo wrote: "The power of Visual Studio 2005 lies in its ability to empower users to build, test, and debug powerful applications...
0
by: fiona | last post by:
Innovasys Ltd., a leader in help authoring and documentation tools, today announced the inclusion of a tailored version of the Innovasys HelpStudio help authoring product, HelpStudio Lite, in the...
3
by: Rolf Welskes | last post by:
Hello, for a large web site project we would like to use nested Master Pages. Unfortunely VS2005 is not able to show pages in design mode when nested Master pages are used. This has the...
3
by: Edwin Smith | last post by:
I have a 2 form project in VS2005 that now hangs whenever I try to do anything with the second form. This seems to have started when I added some SQL tables from a Pervasive v.9 database using the...
1
by: johnlim20088 | last post by:
Hi, Currently I have 6 web projects located in Visual Source Safe 6.0, as usual, everytime I will open solution file located in my local computer, connected to source safe, then check out/check in...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.