CA1416. How to tell builder that only platform is Windows?

Question

dotnet run (on windows) causes warning CA1416: This call site is reachable on all platforms. 'WellKnownSidType.WorldSid' is only supported on: 'windows'.

My program is designed to run only on windows.

I tried to add SupportedPlatform to MyApp.csproj, but no luck.

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

  <PropertyGroup>
    <TargetFramework>net5.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Authentication.Negotiate" Version="5.0.5" />
    <PackageReference Include="System.DirectoryServices" Version="5.0.0" />
    <SupportedPlatform Include="Windows"/>
  </ItemGroup>

</Project>

What am I doing wrong? How can I show dotnet run that this project is windows-only?

Change Target OS in properties for project (Console, REST API,...) ? — Kiquenet
– Kiquenet, Commented Jul 13, 2022 at 6:56

JL0PD · Accepted Answer · 2021-04-16 04:07:26Z

85

You can mark each windows-specific method with System.Runtime.Versioning.SupportedOSPlatformAttribute e.g.

[SupportedOSPlatform("windows")]
public static void Foo()
    => Thread.CurrentThread.SetApartmentState(ApartmentState.STA);

Mark entire assembly with in AssemblyInfo (if you have one)

[assembly: System.Runtime.Versioning.SupportedOSPlatformAttribute("windows")]

Or edit .csproj file to target windows-specific version of dotnet to make these changes automatic

<TargetFramework>net5.0-windows</TargetFramework>

answered Apr 16, 2021 at 4:07

JL0PD

4,7182 gold badges20 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

9 Comments

TK-421 Over a year ago

Does the SupportedOSPlatform revers to the machine on which the dotnet app is being run, or the os platforms that user can reach the app from?

JL0PD Over a year ago

@TK-421, this attribute is only a recommendation from compiler to developer. It won't affect users of website

Nicke Manarin Over a year ago

Last one does nothing (testing with .NET 6).

JL0PD Over a year ago

@NickeManarin do you have <GenerateAssemblyInfo>false</GenerateAssemblyInfo> somewhere in project or Directory.build.props?

Nicke Manarin Over a year ago

@JL0PD Yes, I have. Removing it fixed the issue. Of course, I just had to migrate the app details (version, names, etc) to the project.

|

President James K. Polk · Accepted Answer · 2025-05-28 02:24:13Z

17

Removed the AssemblyInfo.cs file.
Removed the following from the .csproj file

    <GenerateAssemblyInfo>false</GenerateAssemblyInfo>

Add to the .csproj file

    <Project Sdk="Microsoft.NET.Sdk.Web">
        <PropertyGroup>
            <TargetFramework>net8.0-windows</TargetFramework>
            <PlatformName>windows</PlatformName>
            <OutputType>WinExe</OutputType>
       </PropertyGroup>
    </Project>

edited May 28 at 2:24

President James K. Polk

42.3k34 gold badges113 silver badges149 bronze badges

answered Mar 18, 2023 at 6:57

Joseph Wambura

3,5463 gold badges26 silver badges29 bronze badges

3 Comments

Tomasz Chudzik Over a year ago

Great answer. Fixed everything for me. I used it in my .Net 7 app with <TargetFramework>net7.0-windows</TargetFramework>

wiiznokes3 Over a year ago

funny thing: WinExe will discard all your logs if you're launching your exe as a child process AHAHA; thanks

l33t Over a year ago

The whole point of <GenerateAssemblyInfo>false</GenerateAssemblyInfo> is to get rid of that dreaded AssemblyInfo.cs. Certainly don't want to disable this new feature just because of this little glitch.

BRap · Accepted Answer · 2024-05-22 13:41:20Z

4

For getting by just in the code just wrap the function that is MS only in check for OperationSystem, like:

if (OperatingSystem.IsWindows())
    // call to a service that is only suported on Windows
else
    throw new Exception("Only available on Windows operating system!");

If it helps sombody...

answered May 22, 2024 at 13:41

BRap

6352 gold badges13 silver badges31 bronze badges

2 Comments

ps2goat Over a year ago

This works, but if you have a lot of places this is done then the attribute from the other answer is nice. Especially if the app is only planning to target windows.

O. R. Mapper Dec 25, 2024 at 16:48

@ps2goat: If you are planning to only target Windows, you are right. Otherwise, using the attribute form just moves the problem elsewhere, to wherever the now attributed method is called. For multi-platform applications, at some point, you'll have to fork execution between those lines that will run only on Windows and what is alternatively going to happen if you're not on Windows.

Collectives™ on Stack Overflow

CA1416. How to tell builder that only platform is Windows?

3 Answers 3

9 Comments

3 Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

9 Comments

3 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related