Hi Daniel, Welcome to the Group! I hope you enjoy your time here.
Your idea seems interesting and valid. But I do not think it is supported by ASP.NET. The "controls" configuration element basically corresponds to the @Register directive and essentially allows you to specify only the tagPrefix, namespace and Source/Assembly of the control. Perhaps, you can build the logic into the controls that they take a default connectionstring if none is provided. On Aug 31, 1:09 am, Daniel M <[EMAIL PROTECTED]> wrote: > Hi all, > > New to the group and I hope I can contribute. > My question. I'd like to create a databound control library, > basically an assembly, that has a custom globally scoped property. > Something so I can add an attribute to the register directive for a > set of controls. > > <pages enableEventValidation="true"> > <controls> > <add tagPrefix="myControls" assembly="my.Controls" > namespace="my.Controls" connectionstring="myConnectionstring" /> > </controls> > </pages> > > That way I wouldn't have to reiterate my attribute property in the > designer every time I create an instance of the control. I don't know > if this violates the separation of data and presentation or not. But > it seems like a good way of creating a set of custom controls with > their data pre-populated for my common data. > > Any ideas? > Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx -~----------~----~----~----~------~----~------~--~---
