Re: Web Projects in VS 2005

Tech-Archive recommends: Fix windows errors by optimizing your registry



Toby,

I don't think this behavior has changed from 1.x. The only difference is
that in 1.x you HAD TO create a virtual directory in order for hosting a Web
project/Web Control project whereas in VS 2005 the default of using file
based projects don't use or respect virtual directory boundaries.

You can still do this in VS.NET 2005 by opening the project as a Web Project
from the Web as opposed to opening as a file based project. When you do
ASP.NET recognizes Virtual boundaries and separates the projects as I think
you are looking for.


+++ Rick ---

--

Rick Strahl
West Wind Technologies
www.west-wind.com
www.west-wind.com/weblog


"TobyRiley" <TobyRiley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A18A94FF-D9F0-418E-851A-9CA9EC18EB15@xxxxxxxxxxxxxxxx
>I was reading the post from Scott Guthrie's site
> http://weblogs.asp.net/scottgu/archive/2005/08/23/423409.aspx regarding
> sub
> webs and I have a question. When I originally set up ASP.NET to use a
> modular
> approach to web site development I followed the Q article.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;307467#5 where you
> can create a root application then a sub web
>
> i.e.
>
> http://localhost/application1 (references project sharedcontrols, module1,
> module2)
> http://localhost/application1/module1 (references project sharedcontrols)
> http://localhost/application1/module2 (references project sharedcontrols)
> http://localhost/application1/sharedcontrols
>
> None of the sub webs are applications as everything fall back to the root.
> When using VS 2005 it seems impossible because a you cannot exclude sub
> webs
> unless they are an application BUT if they are an application you get an
> error - The virtual path #### maps to another application, which is not
> allowed.
>
> This seems like a complete catch 22. How do I share controls between apps
> on
> a system with about 50 separate modules. I cannot treat them as separate
> applications.
>
> Any explanation or workaround would be greatly appreciated.
>
> Regards
>
> Toby


.



Relevant Pages

  • Re: More than One
    ... Microsoft Online Support ... | directory can has its own virtual directory based IIS ... | there is no namespace statement in ASP.NET 2.0 applications and there is ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Having Two web.config files under same site.
    ... be integrated with other webs site developped to use other platforms such as php, jsp, etc. so obivously we have our own web.config file. ... Even tho you try to set this up in IIS to have separate virtual directories, an app domain for ASP.NET starts at a virtual directory and goes downward into the file structure. ... So then it finds another web.config and as it noted, you can't have more than 1 enterprise library config section. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Having Two web.config files under same site.
    ... Asela Gunawardena wrote: ... integrated with other webs site developped to use other platforms such as php, jsp, etc. so obivously we have our own web.config file. ... Even tho you try to set this up in IIS to have separate virtual directories, an app domain for ASP.NET starts at a virtual directory and goes downward into the file structure. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Forms Authentication
    ... "Hernan de Lahitte" wrote: ... > different applications, you have a SSO scenario with Forms ... >> successfully, when the login page, and the redirect page are in the same ... >> virtual directory, however, I want to put the login page into a separate ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Multiple Subdirectories with different login pages
    ... Yep -- a nested virtual directory under all of your applications' directories mapped to the same physical location works. ... different authentication schemes for the child directories then you'll have to make them applications in IIS. ... Now sites A,B, and C will all have seperate loging forms using ...
    (microsoft.public.dotnet.framework.aspnet)