Re: Some Advice

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance




thankyou for further proof
that developing sophisticated
web applications in .net is a joke

if ms simply allowed for codeblocks in
methods and classes

your problem would be solved





Cam wrote:
> It's not too difficult. You just partition the web layer up as seperate web
> projects, which will each output a different assembly containing part of your
> site, and will contain the from end (aspx, ascx) files also.
>
> The key thing that you have to do is Remove the application setting on
> Virtual Directories created for each module of the application when you set
> it up as a Web project in Visual Studio. Otherwise you will get a message
> saying that you can't access controls within other modules because they are
> in a differnt application.
>
> This means however that all the assemblies of your different web modules
> will need to go in a Bin folder underneath the root of your website.
> Unfortunately web projects refuse to allow you to target built assemblies to
> anywhere outside their project folder, therefore you'll need a script or
> something which is run after a completed build to copy newly built assemblies
> into the website root where the website will expect them.
>
> HTH,
> Cam
>
> "TobyRiley" wrote:
>
> > However I would like like to stop deveoping this as a single humongous web
> > site (as it keeps on growing) and develop individual web application modules
> > that can be more easily version controlled. As you can imagine one change
> > means a complete upgrade of an enitire site rather than just a small module.

.

Relevant Pages

  • RE: Some Advice
    ... will need to go in a Bin folder underneath the root of your website. ... Unfortunately web projects refuse to allow you to target built assemblies to ... into the website root where the website will expect them. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: solution requires web project in default site
    ... you have two different website in the IIS (one is the default ... are web project which are created on another website(no the default one, ... Since you have mulit websites in the IIS on the win2k server, ... caused by the permission setting in the website. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: solution requires web project in default site
    ... I decided to try re-creating the website and it cleared up the problem. ... I am assuming that there was some problem perhaps buried in the IIS meta ... >> are web project which are created on another website(no the default one, ... >> specify the ip address? ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Some Advice
    ... to ease such a deveopment.) ... "Cam" wrote: ... > will need to go in a Bin folder underneath the root of your website. ... > something which is run after a completed build to copy newly built assemblies ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: solution requires web project in default site
    ... > are web project which are created on another website(no the default one, ... or host headers? ... > specify the ip address? ... > caused by the permission setting in the website. ...
    (microsoft.public.dotnet.framework.aspnet)