Skip to content

Time to get rid of build.cmd? #787

Description

Tried to build PSSA with build.cmd and these errors:

30:59ms> .\build.cmd
Installing .NET Version Manager to C:\Users\Keith\.dnx\bin
Creating destination folder 'C:\Users\Keith\.dnx\bin' ...
Installing 'dnvm.ps1' to 'C:\Users\Keith\.dnx\bin' ...
Installing 'dnvm.cmd' to 'C:\Users\Keith\.dnx\bin' ...
Adding C:\Users\Keith\.dnx\bin to Process PATH
Adding C:\Users\Keith\.dnx\bin to User PATH
Adding C:\Users\Keith\.dnx to Process DNX_HOME
Adding C:\Users\Keith\.dnx to User DNX_HOME
Microsoft (R) Build Engine version 14.0.25420.1
Copyright (C) Microsoft Corporation. All rights reserved.

Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
Build started 6/17/2017 12:12:19 PM.
Project "C:\Users\Keith\GitHub\rkeithhill\PSScriptAnalyzer\PSScriptAnalyzer.sln" on node 1 (default targets).
C:\Users\Keith\GitHub\rkeithhill\PSScriptAnalyzer\PSScriptAnalyzer.sln.metaproj : error MSB4126: The specified solution
 configuration "|Any CPU" is invalid. Please specify a valid solution configuration using the Configuration and Platfor
m properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties bla
nk to use the default solution configuration. [C:\Users\Keith\GitHub\rkeithhill\PSScriptAnalyzer\PSScriptAnalyzer.sln]
Done Building Project "C:\Users\Keith\GitHub\rkeithhill\PSScriptAnalyzer\PSScriptAnalyzer.sln" (default targets) -- FAI
LED.

I also thought that .NET Core no longer uses $home/.dnx.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions