C1 2025 v2.1 Maintenance Release with Licensing Changes

C1 2025 v2.1 Maintenance Release with Licensing Changes

Posted by: greg.lutz on 12 February 2026, 12:21 pm EST

• 

  greg.lutz

  

  • Post Options:
  • Link
    Copy

  Posted 12 February 2026, 12:21 pm EST

  The ComponentOne 2025 v2.1 Maintenance Release is now available. This release includes critical bug fixes related to the 2025 v2 release, small improvements, and a significant licensing change that impacts all active subscribers. Read more below.

  Download the update: https://developer.mescius.com/componentone/download

  Breaking Change with Your License

  As part of recent improvements, our licensing code has also changed. Because of this change, after you download and install the latest version, you’ll need to reactivate your license to continue developing without interruption.

  See how to reactivate your license: https://developer.mescius.com/componentone/docs/license/online-license/activating-serial-key#reactivate-a-serial-key-using-the-c1controlpanel

  Release History - see bug fixes and small improvements

  *WinForms - https://developer.mescius.com/componentone/docs/win/online-releasehistory/releasehistory/2025-v2-1

  *WPF - https://developer.mescius.com/componentone/docs/wpf/online-releasehistory/releasehistory/2025-v1-2

  *ASP.NET Core - https://developer.mescius.com/componentone/docs/mvc/online-mvc/ReleaseHistory/2025-v2

  *Blazor - https://developer.mescius.com/componentone/docs/blazor/online-blazor/release-history/2025-v2-1

  *WinUI - https://developer.mescius.com/componentone/docs/winui/online-winui/release-history/2025-v2-1

  *.NET MAUI - https://developer.mescius.com/componentone/docs/maui/online-maui/releasehistory/2025-v2-1

• 

  rick.papke

  • Post Options:
  • Link
    Copy

  Posted 7 March 2026, 4:09 pm EST

  FWIW - to assist anyone having a similar issue with the new licensing.

  After installing Activereports 20, I was getting errors in my NF 4.8 solution (that uses C1 Enterprise controls) similar to Could not find file '\obj\Debug.sa3licx.

  I upgraded all of the C1 assemblies to the latest (had to download the latest ComponentOne Control Panel) and try to force an update - took several tries. I reapplied my licence. I was still experiencing problems. A manual install of the licensing tool resolved it

  dotnet tool install -g sa3client

  This was my experience, which is likely not indicative of most.

• 

  jim

  • Post Options:
  • Link
    Copy

  Posted 28 April 2026, 2:51 pm EST

  I have been using C1 controls for more than 25 years, and I have never had so much trouble with licensing as I have since late last year. It is at the point where I may need to find new controls if this cannot be resolved, and that is no easy matter.

  My experience with the new licensing system has been horrible. It started back in late 2025 when I saw my first nag screen. **I was down for over 2 months while C1 Support tried to talk with the developers **and the disconnect between the teams made it almost impossible for them to provide timely support. Only after more than 2 months of waiting was I able to start compiling my code again. During the entire time I felt that they were far more concerned with the overseas developers than the impact on my business.

  Since then I have had random nags screens appear and when they do I am shut down hard and am forced to figure out where the offending source is, and since C1 offers no tools to help with this, it can take a long time to go through all my projects to find the source.

  Recently I had this happen out of the blue again and I was unable to find the offending source. I was shut down hard right when I needed to publish. I moved on to other more pressing matters and when I got back to the offending project it no longer showed the nag, and I have no idea what I did to resolve it.

  I find the way it shuts down my IDE to be completely unacceptable, and the lack of tools with which to rapidly identify the source makes this an even less acceptable problem.

  I need the nag screen to be survivable - meaning the project continues and stays alive. This would give me an opportunity to complete whatever task or workflow I am engaged in before trying to find the source of the nag.

  As for finding the source of the nag, the nag screen itself should directly show the root cause assembly, otherwise tools that make it easy to find must be provided.

  Failing this the controls are not useable as they cost productivity that I cannot tolerate, especially after losing more than two months of productivity due to early issues with the licensing system.

  As a customer I do not really care about the needs of ComponentOne in a situation like this. I must have a reliably vendor, and sadly, due to the disconnect between Development and Support combined with the poor implementation of the Licensing system I am struggling to find the value in these controls which I have now used for over 25 years.

  I am deeply disappointed with C1 at this time. I hope they can find a way to fix these issues so I can resume my development without fear of random shutdowns.