Can't use SyntaxEditor package in cross-platform net6.0 project

SyntaxEditor for WPF Forum

Posted 1 year ago by Chris White
Version: 22.1.4
Platform: .NET 6.0
Environment: Windows 10 (64-bit)


We are having some trouble consuming the ActiproSoftware.Controls.Wpf.SyntaxEditor NuGet package from a cross-platform .NET 6.0 project. This project uses the text/parsing assemblies rather than the syntax editor itself, and the SyntaxEditor package helpfully includes both net5.0 and net5.0-windows variants, so it seems this should work.

Example project:

<Project Sdk="Microsoft.NET.Sdk">


    <PackageReference Include="ActiproSoftware.Controls.Wpf.SyntaxEditor" Version="22.1.4" />


Unfortunately, attempting to build this (dotnet build) gives the error:

error NETSDK1136: The target platform must be set to Windows (usually by including '-windows' in the TargetFramework
property) when using Windows Forms or WPF, or referencing projects or packages that do so. [C:\work\gen2\actipro\exampl

This seems to be down the to the .nuspec file not explicitly specifying a group for "net5.0" in the "frameworkReferences" section. If can make the error go away by hacking the .nuspec file so this section looks like this:

      <group targetFramework="net5.0-windows">
        <frameworkReference name="Microsoft.WindowsDesktop.App.WPF" />
	  <group targetFramework="net5.0" />
      <group targetFramework=".NETCoreApp3.1">
        <frameworkReference name="Microsoft.WindowsDesktop.App.WPF" />

Having done so, there is a second issue, which is that any code using the APIs is flagged. e.g. adding this code:

using ActiproSoftware.Text.Parsing;

namespace example;
public class Class1
    public IAstNode Example(IAstNode node) => node.Parent;

Produces a warning:

warning CA1416: This call site is reachable on all platforms. 'IAstNode.P
arent' is only supported on: 'windows'. [C:\work\gen2\actipro\example\example.csproj]

This is because the assemblies (ActiproSoftware.Text.LLParser.Wpf.dll and ActiproSoftware.Text.Wpf.dll) both specify SupportedOSPlatform("windows"), when it appears that they don't need to do so. Would it be possible for you to remove this attribute in future releases?

For now we are working around these issues by explicitly referencing the .NET Standard 2.0 assemblies instead of using PackageReferences, but it would be great if we could just consume the package.


Comments (1)

Answer - Posted 1 year ago by Actipro Software Support - Cleveland, OH, USA

Hi Chris,

Thanks for posting about this and we appreciate the detail.  We've updated everything for the next build to handle this properly for you.

Actipro Software Support

The latest build of this product (v24.1.2) was released 2 months ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.