Posted 2 June 2022, 7:49 am EST
I don’t know if this helps, but we have dotnet core 6 projects which work OK using the method suggested in the help documentation.
We did two things. First, we created a dotnet 6 class library, and that’s where all of our reports are stored. Our main dotnet 6 projects (usually razor pages or MVC or console) then reference that compiled DLL. We did this to shield our other projects from the NuGet carpet bombing abomination and conflicts from their dozens of required packages.
The second thing is - as you know - you can’t edit the design in a dotnet 6 project. So we create a second dotnet framework project as described in the help file, solely for linking to the dotnet 6 active reports project reports. In the AR help PDF file it’s page 1251 titled, “Designing Code-based Section Reports in .NET Core”. We follow those steps, and then when you need to use the designer, you double-click the linked report in the dotnet framework to edit the designer. You still edit the code from the original.
This has worked fine. It’s completely less than great for us, considering every single report we’ve ever written is a code-based section report. I’ve never been given a technical answer as to why this is required, but AR blames it directly on Microsoft.
Oh, and the stand-alone report designer doesn’t allow me to edit the code-based section reports. I though that would be an “out”, but no joy.