"Linda Liu[MSFT]" <v-lliu@online.microsoft.com> wrote in message
news:J6UeX2HmIHA.9932@TK2MSFTNGHUB02.phx.gbl...
> Hi Schneider,
>
> You need to implement a custom CodeDomSerializer to control the generation
> of component initialization code for your custom control/component at
> design time. And then associate your custom CodeDomSerializer
> implementation with the type of your control/component using a
> DesignerSerializerAttribute.
>
> For more information on the CodeDomSerializer class and a sample, please
> refer to the following MSDN document:
> http://msdn2.microsoft.com/en-us/library/system.componentmodel.design.serial
> ization.codedomserializer.aspx
>
> Hope this helps.
> If you have any question, please feel free to let me know.
>
> Sincerely,
> Linda Liu
> Microsoft Online Community Support
>
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
> msdnmg@microsoft.com.
>
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>

"Linda Liu[MSFT]" <v-lliu@online.microsoft.com> wrote in message
news:%23pBKntumIHA.10116@TK2MSFTNGHUB02.phx.gbl...
> Hi Schneider,
>
> Thank you for your prompt reply!
>
> A custom CodeDomSerializer for a control can only control the generation
> of
> the control initialization code, which don't contain the code that adds
> the
> control to its parent's Controls collection, e.g. a form.
>
> So I also think that we need to intercept the root serializer for the
> form.
> Unfortunately, I haven't worked out how to do this. I am consulting this
> issue in our internal discussion group. As soon as I get an answer, I will
> get it back to you.
>
> I appreciate your patience!
>
> Sincerely,
> Linda Liu
> Microsoft Online Community Support
>
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
> msdnmg@microsoft.com.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>

"eschneider" <eschneider@community.nospam> wrote in message
news:ugLZLv0mIHA.5280@TK2MSFTNGP02.phx.gbl...
> Yes, thats what I'm looking for.
>
> Thanks,
> Schneider
>
>
>
> "Linda Liu[MSFT]" <v-lliu@online.microsoft.com> wrote in message
> news:%23pBKntumIHA.10116@TK2MSFTNGHUB02.phx.gbl...
>> Hi Schneider,
>>
>> Thank you for your prompt reply!
>>
>> A custom CodeDomSerializer for a control can only control the generation
>> of
>> the control initialization code, which don't contain the code that adds
>> the
>> control to its parent's Controls collection, e.g. a form.
>>
>> So I also think that we need to intercept the root serializer for the
>> form.
>> Unfortunately, I haven't worked out how to do this. I am consulting this
>> issue in our internal discussion group. As soon as I get an answer, I
>> will
>> get it back to you.
>>
>> I appreciate your patience!
>>
>> Sincerely,
>> Linda Liu
>> Microsoft Online Community Support
>>
>> Delighting our customers is our #1 priority. We welcome your comments and
>> suggestions about how we can improve the support we provide to you.
>> Please
>> feel free to let my manager know what you think of the level of service
>> provided. You can send feedback directly to my manager at:
>> msdnmg@microsoft.com.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>
>

"Linda Liu[MSFT]" <v-lliu@online.microsoft.com> wrote in message
news:DlrLanrnIHA.4932@TK2MSFTNGHUB02.phx.gbl...
> Hi Schneider,
>
> I got a reply from an expert in the WinForm design time field.
>
> He said that to control the code generation of a root object like a form,
> we need to derive from the TypeCodeDomSerializer class to implement the
> code generation we like. Then add a DesignerSerializerAttribute to the
> form
> with a second parameter of TypeCodeDomSerializer. For example:
>
> [DesignerSerializer(typeof(MyTypeSerializer),
> typeof(TypeCodeDomSerializer))]
> public class MyCustomForm : Form {
> }
>
> class MyTypeSerializer:TypeCodeDomSerializer
> {}
>
> TypeCodeDomSerializer does most of what you want, so you can simply derive
> from it. The one thing it doesn't know about is "InitializeComponent".
> You would have to add support for that. The following is a sample:
>
> internal class ComponentTypeCodeDomSerializer : TypeCodeDomSerializer {
> private static object _initMethodKey = new object();
> private const string _initMethodName = "InitializeComponent";
> private static ComponentTypeCodeDomSerializer _default;
>
> internal new static ComponentTypeCodeDomSerializer Default {
> get {
> if (_default == null) {
> _default = new ComponentTypeCodeDomSerializer();
> }
>
> return _default;
> }
> }
>
> /// <include file='doc\ComponentTypeCodeDomSerializer.uex'
> path='docs/doc[@for="ComponentTypeCodeDomSerializer.GetInitializeMethod"]/*'
> />
> /// <devdoc>
> /// This method returns the method to emit all of the
> initialization code to for the given member.
> /// The default implementation returns an empty constructor.
> /// </devdoc>
> protected override CodeMemberMethod
> GetInitializeMethod(IDesignerSerializationManager manager,
> CodeTypeDeclaration typeDecl, object value) {
> if (manager == null) {
> throw new ArgumentNullException("manager");
> }
>
> if (typeDecl == null) {
> throw new ArgumentNullException("typeDecl");
> }
>
> if (value == null) {
> throw new ArgumentNullException("value");
> }
>
> CodeMemberMethod method = typeDecl.UserData[_initMethodKey] as
> CodeMemberMethod;
>
> if (method == null) {
> method = new CodeMemberMethod();
> method.Name = _initMethodName;
> method.Attributes = MemberAttributes.Private;
> typeDecl.UserData[_initMethodKey] = method;
>
> // Now create a ctor that calls this method.
> CodeConstructor ctor = new CodeConstructor();
>
> ctor.Statements.Add(new CodeMethodInvokeExpression(new
> CodeThisReferenceExpression(), _initMethodName));
> typeDecl.Members.Add(ctor);
> }
>
> return method;
> }
>
> /// <include file='doc\ComponentTypeCodeDomSerializer.uex'
> path='docs/doc[@for="ComponentTypeCodeDomSerializer.GetInitializeMethods"]/*
> ' />
> /// <devdoc>
> /// This method returns an array of methods that need to be
> interpreted during deserialization.
> /// The default implementation returns a single element array
> with the constructor in it.
> /// </devdoc>
> protected override CodeMemberMethod[]
> GetInitializeMethods(IDesignerSerializationManager manager,
> CodeTypeDeclaration typeDecl) {
> if (manager == null) {
> throw new ArgumentNullException("manager");
> }
>
> if (typeDecl == null) {
> throw new ArgumentNullException("typeDecl");
> }
>
> foreach (CodeTypeMember member in typeDecl.Members) {
> CodeMemberMethod method = member as CodeMemberMethod;
>
> // Note: the order is important here for performance!
> // method.Parameters causes OnMethodPopulateParameters
> callback and therefore it is much more
> // expensive than method.Name.Equals
>
> if (method != null && method.Name.Equals(_initMethodName)
> && method.Parameters.Count == 0 ) {
> return new CodeMemberMethod[] { method };
> }
> }
>
> return new CodeMemberMethod[0];
> }
> }
>
> You'd have to do something similar in your own custom
> TypeCodeDomSerializer.
>
> Hope this helps.
>
> Sincerely,
> Linda Liu
> Microsoft Online Community Support
>
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
> msdnmg@microsoft.com.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>

"Linda Liu[MSFT]" <v-lliu@online.microsoft.com> wrote in message
news:FNC93OHoIHA.9932@TK2MSFTNGHUB02.phx.gbl...
> Hi Schneider,
>
> Thank you for your reply!
>
> For existing root designers, you need to derive the exiting Forms from the
> base Form which is adorned with the custom type codedom serializer. That's
> to say, change the base class of the existing Forms from
> System.Windows.Forms.Form to MyCustomForm.
>
> Then reopen the existing Forms in the designer and the code generated in
> the InitializeComponent method will change.
>
> Hope this helps.
>
> Sincerely,
> Linda Liu
> Microsoft Online Community Support
>
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
> msdnmg@microsoft.com.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>