Collection property Hell on an ASP.NET Server Control

Posted by: Rick Strahls WebLog, on 18 Aug 2006 | View original

  I’ve been fighting an odd problem today with a custom control I’m building. The control is another extender control that has a number of child items that track other items on the form. The markup looks something like this:   <ww:LocalizationExtender id="Localizer" runat="server">     <LocalizationItems>     <ww:LocalizationItem ControlId="lblMessage"                          ...

Advertisement

Similar Posts

  • August 9th ASP.NET Link-Listing more
  • Introducing CaptainHook - A Subversion Hook Framework For .NET more
  • Why ASP.NET 2.0 Login control doesn't work with SQL Membership provider? more
  • Dynamically Loading Controls in ASP.NET Is A Pain more
  • A new exciting version of Visual WebGui 1.0 (build 5.81.3.72.2) is available for download more
  • CS Dev Guide: Add new page or user control to Control Panel more
  • ASP.NET 2.0 Client Validation Javascript Bug more
  • CS Dev Guide: Add new page or user control to Control Panel more
  • Web Parts in WSS 3.0 more
  • Building your own data bound controls... more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD