Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How to reference System.Design
See original GitHub issueWhen converting the project to netcoreapp3.0 and keeping the System.Design reference, the compiler doesn’t seem to see the reference:
CS0012 The type ‘ComponentDesigner’ is defined in an assembly that is not referenced. You must add a reference to assembly ‘System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>netcoreapp3.0</TargetFramework>
<!-- ... -->
</PropertyGroup>
<ItemGroup>
<Reference Include="System.Design" />
<!-- ... -->
<FrameworkReference Include="Microsoft.DesktopUI" />
</ItemGroup>
</Project>
How will this work in the future?
(edit) This gets it to build:
<Reference Include="System.Design" HintPath="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\System.Design.dll" />
But since System.Design is heavily used at runtime, I’m doubtful that the .NET Framework’s System.Design will work.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We have similar dependencies for our custom WinForms controls too. The missing API set is nearly identical. In our case they are design-time only and we have a build option to strip them out of release builds, so we are still able to run our application on .NET Core 3 alpha today (with some additional fixes discussed in the CoreFX repository issues).
I suspect this will come up quite often and it has to be addressed in one way or another. I was hoping that this will eventually come later when the WinForms design-time support is brought in later preview. I’m taking a wait-and-see approach on this one, but wanted to express some support that the scenario is probably common.
Hi Olia,
Our applications depend on DevExpress’s End User Report Designer (docs). DevExpress built it on top of the System.ComponentModel/IDesignerHost/CodeDOM set of abstractions, very much like the Windows Forms designer itself.
This designer ships for our users at runtime (as the name suggests). We’ve written custom reporting elements that integrate with it. Since DevExpress based the designer heavily on System.Design, our integrations with the report designer are also tied to System.Design. We’re hoping that this doesn’t keep us from moving to .NET Core.
In this report, see especially
DevExpress.XtraReports.v17.2.Extensions.dllwhich houses their End User Report Designer: Portability report for DevExpress dependencies.xlsxThat’s what DevExpress’s code needs. Our code, which merely integrates with DevExpress’s report designer, ends up directly using these types:
And these members: