Submit My Question - Recent Questions - Recent Answer
Msdn Tech >> .NET Development >> .NET Base Class Library

INamingContainer, what are you doing with that MasterPage?

The master pages feature in the new .NET 2.0 framework is great. Better said, there is nothing that can compare to it! And that makes it even more frustrating, that the MasterPage class implements the INamingContainer interface. Besides that, there is no need for the MasterPage to implement that interface, because the ContentPlaceHolder -usually used within a master page- implement the INamingContainer interface too. So when ensuring a control's uniqueness, the ContentPlaceHolder would do just fine. Or.....
Is this true? Why does the MasterPage implement this interface? And is there a possibility to NOT use the INamingContainer, but keep using those amazing Master Pages?
I'm generating my interfaces from the database and therefore I know that my interfaces have a unique id. But now I have the problem, I can't find them anymore, because an INamingContainer 'renames' my controls.
Who can help me on this one?
[1023 byte] By [DeKale] at [2007-12-16]
«« BinaryFormatter compatibility between .Net 2.0 Beta 1 and Beta 2
»» Reporting Services with Axapta
# 1
DeKale, can I suggest you ask this question in the ASP.NET forum: http://forums.asp.net

Regards,
KIt

KitG at 2007-9-9 > top of Msdn Tech,.NET Development,.NET Base Class Library...
# 2
a little discussion about the subject has been going on on asp.net/forums.
DeKale at 2007-9-9 > top of Msdn Tech,.NET Development,.NET Base Class Library...
.NET Development
.NET Base Class Library

.NET Development Hot Topic

.NET Development New Topic

.NET Development

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech

Site Classified