Re: MasterPages or Web Visual Inheritance (ASP.Net 1.1)?
From: VR (vcreb_at_hotmail.com)
Date: 09/15/04
- Next message: Curt_C [MVP]: "Re: MasterPages or Web Visual Inheritance (ASP.Net 1.1)?"
- Previous message: Pipo: "store a delegate into a viewstate?"
- In reply to: Curt_C [MVP]: "Re: MasterPages or Web Visual Inheritance (ASP.Net 1.1)?"
- Next in thread: Curt_C [MVP]: "Re: MasterPages or Web Visual Inheritance (ASP.Net 1.1)?"
- Reply: Curt_C [MVP]: "Re: MasterPages or Web Visual Inheritance (ASP.Net 1.1)?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 15 Sep 2004 16:10:22 -0300
As in the subject of this message, ASP.Net 1.1.
The problem is not getting the same functionality (I know these are two
different approaches), I want to know if I could face problems with this
approach (WebForms Visual Inheritance). Let's say I asked myself "since
Framework 1.0 there is Visual Inheritance for WinForms, why did not MS say
you can do the same with WebForms, is there any problem I'm missing?"
Regards,
Victor Reboucas
"Curt_C [MVP]" <software_AT_darkfalz.com> wrote in message
news:uqFwwb1mEHA.1716@TK2MSFTNGP12.phx.gbl...
> Are you trying this in 2.0 or in 1.0/1.1 ?
> If 2.0 you need the MASTER= in the page
> If 1.0/1.1 you aren't going to get the same functionality
>
> --
> Curt Christianson
> Owner/Lead Developer, DF-Software
> Site: http://www.Darkfalz.com
> Blog: http://blog.Darkfalz.com
>
>
> "VR" <vcreb@hotmail.com> wrote in message
> news:%23djS4Y1mEHA.896@TK2MSFTNGP12.phx.gbl...
>> Hi, I read about Master Pages in ASP.Net 2.0 and after implementing some
>> WinForms Visual Inheritance I tryed it with WebForms (let's say .aspx
>> pages, my MasterPage does not have a form tag itself so, cannot be called
>> a WebForm itself, the child pages will implement forms).
>> I created a Master.aspx page and removed all HTML from it, added some
>> code to the .aspx.vb file to add controls to my page. Then I created a
>> Child.aspx and changed the "Inherits System.Web.UI.Page" to "Inherits
>> MyWeb.Master" and everything gone really fine.
>>
>> Problem: all I need as HTML/Forms/Controls/Etc need to be created by
>> code, I cannot use the Designer to work on the page (but, let's say
>> that's my problem)
>>
>> Question: Is there anything I'm missing here? Is that easy like it? Is
>> there any internal ASP.Net design considerations that would bring me
>> problems with this approach?
>>
>> PS: I know about the MasterPage control found in www.asp.net, I do not
>> need an alternative for my approach, I just want to know if this kind of
>> design would work without problems.
>>
>>
>> Thanks,
>> Victor Reboucas
>>
>>
>
>
- Next message: Curt_C [MVP]: "Re: MasterPages or Web Visual Inheritance (ASP.Net 1.1)?"
- Previous message: Pipo: "store a delegate into a viewstate?"
- In reply to: Curt_C [MVP]: "Re: MasterPages or Web Visual Inheritance (ASP.Net 1.1)?"
- Next in thread: Curt_C [MVP]: "Re: MasterPages or Web Visual Inheritance (ASP.Net 1.1)?"
- Reply: Curt_C [MVP]: "Re: MasterPages or Web Visual Inheritance (ASP.Net 1.1)?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|