call support and tell them you need the patch from that Q article you
mentioned..
"Mr Wizard" <anonymous@discussions.microsoft.com> wrote in message
news:E97CBECB-E127-4106-BD90-A5FA0A383E1F@microsoft.com...[color=blue]
> I am going through the front controller[/color]
http://msdn.microsoft.com/library/de...ollerInASP.asp
and all works well except when the server.transfer occurs. I get invalid
IsPostBack results which I believe can fixed using the patch in KB:821156.
How do I get this patch?[color=blue]
>
> Another question in the same pattern is when using LoadConrol to load a[/color]
..ascx file I get "maps to another application, which is not allowed" error
which is because the file I have is truly in another application. The
problem is this to use the design pattern above it is not useful if I cannot
load a control in another application but can infact load a page from
another site.[color=blue]
>
> Suppose I had three applications shown below. I only want to have files[/color]
in the applications that are different from each other (Visual Inheritance).
I know, I know you cant inherit a html page, yea, yea, yea read on. Lets
assume that Application1 is our base application and all other applications
inherit from it. For example Application1 login.aspx, Application2
login.aspx are different from each other.[color=blue]
>
> IIS
> |
> |-Application1
> | |
> | |-default.aspx
> | |-mycontrol.ascx
> | '-login.aspx
> |
> |-Application2
> | |
> | '-default.aspx
> |
> '-Application3
> |
> '-login.aspx
>
> Using the design pattern I can load default.aspx from Application1 using[/color]
Server.Transfer when the user goes to
http://localhost/Application3/default.aspx because I have an HttpHandler
which says if the user attempts to access Application3/*.aspx transfer them
to Application1/default.aspx if Application3 does not contain the requested
*.aspx page. This in fact works quite nicely.[color=blue]
>
> However if Application1's default.aspx says to[/color]
LoadControl("mycontrol.ascx") I get the "maps to another application, which
is not allowed" error which in fact is also true BUT if I can
Server.Transfer to another page then I should be able to load a control that
is in the same directory as that page "Another application" or not. It
appears that even though the pattern says in can implement a
model-view-controller it doesn't do so well with the "view" part.[color=blue]
>
> I attempted to trick IIS into thinking that the control is in a virtual[/color]
directory under Application3 but this only works to a certain extent. If I
want to override mycontrol.ascx in Application3 then I need to remove the
virtual directory and copy the structure entirely. This does not meet my
first requirement to not duplicate files across applications (and I have a
lot of directories). I am two seconds shy from hacking together my own
LoadControl but I REALLY don't want to do this.[color=blue]
>
> Now if anyone has a suggestion on an alternative to this I am listening.[/color]
I am trying to get a visual inheritance methodology to work as we have many
customers and don't want to duplicate the entire site for each one. I only
want to change pages that are customer specific.[color=blue]
>
> To send me an email
> nospamscotchy32000 yahoo com <--- remove nospam and insert a @ and . to[/color]
mail me.
