@KlausLoeffelmann thank you for explanations.
Mainly I was trying to fix/understand #5 bug.
I was spent several hours playing with this and I think I'm beginning to understand something... But at the same time, I generally cease to understand how it works now in this (chart) project? How can it work if everything is in one heap in one .Net6 project??? 🤦‍♂️
To begin with, I want to note that all this is very complicated, at least for a person who has never written a complex control with it's own designer 😭

I found what line of code is responsible of #5. Simplified code:

public override object Serialize(IDesignerSerializationManager manager, object value)
{
    Diagnostics.Trace.WriteLine("Context " + manager.Context.Current + "; value " + value);
    Chart chart = value as Chart;

    object result = null;
    CodeDomSerializer baseSerializer = (CodeDomSerializer)manager.GetSerializer(typeof(Chart).BaseType, typeof(CodeDomSerializer));
    if (baseSerializer is not null)
    {
        result = IsSerialized(manager, value) ? GetExpression(manager, value) : baseSerializer.Serialize(manager, value);
        if (chart is not null && chart.DataSource is string dSstring && dSstring != "(none)" && result is CodeDom.CodeStatementCollection statements)
        {
            CodeDom.CodeExpression targetObject = base.SerializeToExpression(manager, value); // the problem in this line!
            //if (targetObject is not null)
            //{
            //    CodeDom.CodeAssignStatement assignStatement = new CodeDom.CodeAssignStatement(
            //        new CodeDom.CodePropertyReferenceExpression(targetObject, "DataSource"),
            //        new CodeDom.CodePropertyReferenceExpression(new CodeDom.CodeThisReferenceExpression(), dSstring));
            //    statements.Add(assignStatement);
            //}
        }
    }

    return result;
}

With code above we have #5 and Diagnostics line will never appear and DataSource is null of corse. So Serialize method simply never called.
If comment out this line:

CodeDom.CodeExpression targetObject = base.SerializeToExpression(manager, value);

we have no #5 problem.

So, my thots that this line (when referenced by project) somehow instructs V.S. to call this code from .net framework (via reflection)???

Also, as I understand from linked repo, that most of the code related to custom editors must be in separate project with net472 target.
In our case in this repo all are in same project. Could this be the reason for this (#5) behaviour? I don't understand how it even worked through the dll reference??? 🤷‍♂️🤦‍♂️

I wanted to separate all entities as described above. If we had only one property with a custom editor (as in the example), then I think I would have succeeded. I see a lot code in *.Protocol project for only one costume property! But we have about two hundred of them! This is really a nightmare! Or I missed something? 😳

And I also think that articles on how to make a new control for a new designer are good, but we definitely need guides on how to migrate the old control with the least effort. Maybe some sort of helper tool? For example, in my situation - I have a large and complex control, I did not write it, moreover, I did not write my own designers / editors at all. And I need to migrate all this staff to a new designer, to be honest, my hands just drop when I see how complicated / unclear this process is 😥

@RussKie
Thank you, but still a lot is not clear :( First of all (as I mentioned above) I totally not understand how does it manage to work now being in one .net6 project???

After that you may be in a position to start building or migrating the editors to be compatible with the out-of-process designer.

Hmmm, I thought that what you described above that's what it is migrating the editors to be compatible with the out-of-process designer. 🤷‍♂️ And in my understanding the sequence should be like this:

Restructure the solution separating the client, the server and the protocol implementations.
The control should really be published as a NuGet, and referenced as one.

I'm wrong? Well, the problems of point 1 (in my understanding) I described above.

P.s. And sorry for being not so responsive. With all this situation in my original country, things become very complicated :(

What is easiest way to swap this in to my solution? #1

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions