dotnet windows forms designtime: Designer services -- dotnet windows forms designtime

You're in the

dotnet windows forms designtime

group:

Designer services

Re: Designer services

Frank Hileman
10/15/2004 6:28:39 AM

dotnet windows forms designtime:

Since there is no real documentation on this, go with your instinct. There
seems to be no harm we have found in storing references per-designer, but we
only store the most frequently used ones. For others we create private
properties to call GetService dynamically. It is safer to get the services
dynamically, since theoretically they can change. Looking at the service
provider code in reflector, I would say most references are fixed for the
lifetime of the designer.

Regards,
Frank Hileman

check out VG.net: www.vgdotnet.com
Animated vector graphics system
Integrated Visual Studio .NET graphics editor

[quoted text, click to view]

Designer services

Joey Callisay
10/15/2004 10:32:24 AM

there are a lot of samples for designer classes. Some are storing internal
references to the services (componentchangeservice, selectionservice, etc.)
on the designer classes, some are getting them when needed. Are there
disadvantages on storing private references to such services rather than
getting them from designer host when needed? thanks...

Re: Designer services

Joey Callisay
10/19/2004 9:04:23 AM

thanks a lot Sir Frank...

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the dotnet windows forms designtime group.

home · blog · groups

Questions? Comments? Contact the dn