Skip to content

Microsoft.NET.Sdk.IL doesn't work correctly when installed in path with spaces #35785

Description

@filipnavara

Attempt to build dotnet/winforms on my machine:

  Accessibility-version -> C:\Projects\winforms\artifacts\bin\Accessibility-version\Debug\netcoreapp5.0\Accessibility-version.dll
  'C:\Users\Filip' is not recognized as an internal or external command,
  operable program or batch file.
C:\Users\Filip Navara\.nuget\packages\microsoft.net.sdk.il\5.0.0-preview.5.20253.6\targets\Microsoft.NET.Sdk.IL.targets(96,5): error MSB3073: The command "C:\Users\Filip Navara\.nuget\packages\\runtime.win-x64.microsoft.netcore.ildasm\5.0.0-preview.5.20253.6\runtimes\win-x64\native/ildasm "C:\Projects\winforms\artifacts\bin\Accessibility-version\Debug\netcoreapp5.0\Accessibility-version.dll" /OUT="C:\Projects\winforms\artifacts\obj\Accessibility\Debug\netcoreapp5.0\/Accessibility.ref.il"" exited with code 9009. [C:\Projects\winforms\src\Accessibility\src\Accessibility.ilproj]

Activity

  1. Dotnet-GitSync-Bot commented on May 4, 2020

    @Dotnet-GitSync-Bot
    Collaborator

    I couldn't figure out the best area label to add to this issue. Please help me learn by adding exactly one area label.

  2. filipnavara commented on May 4, 2020

    @filipnavara
    MemberAuthor

    Related to 5dc7013. /cc @stephentoub

    I've locally added " (not ") at the same places which fixed the issue on my machine. Apparently the original fix was reverted because it was broken on some non-Windows environment. Currently I have no access to similar environment to test.

  3. added this to the 5.0 milestone on May 11, 2020
  4. removed
    untriagedNew issue has not been triaged by the area owner
    on May 11, 2020
  5. BruceForstall commented on May 11, 2020

    @BruceForstall
    Contributor

    Fix for this was made, then reverted: dotnet/coreclr#27793

  6. BruceForstall commented on May 11, 2020

    @BruceForstall
    Contributor

    @ViktorHofer @jkoritzinsky @ericstj @tannergooding Does anyone who has touched this file want to claim ownership of this issue?

  7. ViktorHofer commented on May 12, 2020

    @ViktorHofer
    Member

    I don't think someone needs to take ownership explicitely. I marked the issue as up-for-grabs.

  8. BruceForstall commented on Jun 3, 2020

    @BruceForstall
    Contributor

    I'm going to close this as a dup of #13740

  9. ghost locked as resolved and limited conversation to collaborators on Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions