Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET RID not supported #31

Open
nxtn opened this issue Aug 12, 2020 · 1 comment
Open

.NET RID not supported #31

nxtn opened this issue Aug 12, 2020 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@nxtn
Copy link

nxtn commented Aug 12, 2020

It would be good if we don't need to explicitly specify <Platform> if it has been implied by <RuntimeIdentifier>/<PlatformTarget>.

dotnet publish -c Release -r win10-x64

-or-

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

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net5.0</TargetFramework>
    <RuntimeIdentifier>win10-x64</RuntimeIdentifier>
  </PropertyGroup>

</Project>

It's valid to add a project reference from a Any CPU project to a x64 one.

exe> dotnet add reference ..\lib\
Reference `..\lib\lib.csproj` added to the project.

exe> dotnet build
  Determining projects to restore...
  lib -> lib\bin\x64\Debug\net5.0\lib.dll
  exe -> exe\bin\Debug\net5.0\exe.dll
@manodasanW manodasanW added the bug Something isn't working label Aug 17, 2020
@stevenbrix
Copy link

Related to this, we need the vcrtforwarders dlls to be in the correct runtimes\win10-x64\native directory, so that they are copied to the proper location for .NET5 apps. We can't rely on native assemblies being copied next to the .exe, as it breaks behavior with DllImport. See related issue microsoft/CsWinRT#266

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants