dotnet / dotnet/fsharp

Static linking: Understanding FS2009 warnings

Open
#13,108 6 comments 0 reactions 0 assignees View on GitHub
Area-Compiler-CodeGen Bug Impact-Medium
Dominant language
F#
Stars
4.3k
Forks
876
Avg merge
4d 11h
Merged PRs (30d)
131

Description

Please provide a succinct description of the issue.

**Repro steps**

1. Clone https://github.com/VsVim/VsVim
2. Checkout the branch dev/jaredpar/fs2009
3. cd src\VimCore
4. run `dotnet build`

**Expected behavior**

The build completes cleanly

**Actual behavior**

The build produces several FS2009 warnings

```
Microsoft (R) Build Engine version 17.2.0-preview-22152-03+719247ede for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

Determining projects to restore...
All projects are up-to-date for restore.
FSC : warning FS2009: Ignoring mixed managed/unmanaged assembly 'System.Configuration.ConfigurationManager' during static linking [C:\Users\jaredpar\c
ode\VsVim\Src\VimCore\VimCore.fsproj]
FSC : warning FS2009: Ignoring mixed managed/unmanaged assembly 'System.Security.Permissions' during static linking [C:\Users\jaredpar\code\VsVim\Src\
VimCore\VimCore.fsproj]
VimCore -> C:\Users\jaredpar\code\VsVim\Binaries\Debug\VimCore\net472\Vim.Core.dll
VimCore -> C:\Users\jaredpar\code\VsVim\Binaries\Debug\VimCore\net6.0\Vim.Core.dll
```

This project does link the FSharp runtime into the DLL which is likely the source of the FS2009 warnings. Unfortunately though I can't find any information on what this warning is, how to mitigate it, etc ... Looked in a number of places but coming up empty. Want to try and understand this warning so I can move forward with fixing this correctly vs suppressing and moving on.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.