How do you get the full base style/template for a C1 control in .NET9/Blend?

Posted by: jacob.a.buchanan6.ctr on 24 June 2026, 11:18 am EST

    • Post Options:
    • Link

    Posted 24 June 2026, 11:18 am EST

    My team used the .NET Framework version of C1 for a long time and often we would load the controls into Blend for Visual Studio 2022 to get the full template. We would add the control and then right-click the item and click “Edit Template” → “Edit a Copy”. We recently updated our app to .NET9 from framework and I noticed we can no longer get the template for C1 controls. Is this a change in policy for newer C1 builds, or am I doing something wrong?

    To be more specific, when we were on .NET Framework 4.7.2 we were using C1 v5.6.20251.877 and we got a copy of the style for the C1DockControl in order to make a few minor changes to the C1DockTabItem’s ControlTemplate so that we could add a custom button to the TabItem header.

    Upon updating to the .NET9 version of C1 v9.0.20251.1133 I am now getting an error on launch due to my template. I don’t yet know the exact cause of the issue other than its related to my C1DockTabItem style/control template. My initial plan was just to load the updated C1.WPF.Docking package into blend and get the updated template, but the “Edit a Copy” button is greyed out.

    All tips and ideas are appreciated!

  • Posted 25 June 2026, 8:14 am EST

    Hi Jacob,

    Thank you for sharing the details. We could see the behavior you mentioned, where “Edit a Copy” button is disabled in a .NET project. We have shared the details with the development team to get their insights and will let you know the updates as soon as possible

    [Internal Tracking ID: C1XAML-39857]

    Best Regards,

    Kartik

  • Posted 2 July 2026, 10:04 am EST

    Does this apply to all versions of the .NET package? I have an older release, so if the issue is isolated to my version, then I can go through the process of updating. My companies network makes it difficult to get updates, but not impossible. So I can go through that process if it will resolve this issue.

  • Posted 3 July 2026, 9:58 am EST

    Hi Jacob,

    We apologize for the delay in our response.

    The issue where the “Edit a Copy” button is disabled does not appear to be related to a specific version and seems to affect all recent versions. We are getting in touch with the development team to get an update on this, and we will let you know as soon as possible.

    In the meantime, we investigated your requirement further and found that it can be accomplished simply by including the generic.xaml style-definition for C1.WPF.Docking in your project. These files are available at the following installation location - C:\Program Files (x86)\MESCIUS\ComponentOne\WPF\Themes

    Since these files also include internal references to private classes, using them directly may cause build issues on your end. Therefore, for your convenience, we have attached a style-definition with the internal references removed. You can also include this file in your project and customize the ControlTemplate of the C1DockTabItem as needed.

    Attachment: EditTemplateTestCore.zip

    Best Regards,

    Kartik

  • Posted 7 July 2026, 12:36 am EST

    Hi,

    The development team has confirmed that the “Edit a Copy” button being disabled is due to the same issue mentioned above. Since C1Docking uses an internal (inaccessible) class in its template, Visual Studio is unable to generate a copy of the template, causing the option to be disabled.

    This behavior may have been handled differently by Visual Studio for .NET Framework projects (as the design-time implementation differs from .NET Core), but the end result is the same i.e. a copy of the template cannot be created.

    Therefore, the recommended approach is to use the XAML file from our installation folder, remove the inaccessible private references, and then include it as a merged resource in your project. An example is already provided in our previous response.

    Best Regards,

    Kartik

  • Posted 9 July 2026, 4:57 pm EST

    That worked, thanks!

    It took a minute to test out because we are on a closed network and had an older version of C1 installed on our machines. We normally got our updated releases of C1 through nuget packages. So, the themes folder on our machines was out of date showing v4.6.2 themes. We got the newest install and updated themes and we’re able to import all those resource dictionaries into our app.

    Thanks for your help!

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels