TestPathCommand and several others removed in PowerShell 7.2 SDK #16862

colinblaise · 2022-02-09T17:35:48Z

Prerequisites

Write a descriptive title.
Make sure you are able to repro it on the latest released version
Search the existing issues.
Refer to the FAQ.
Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

Using C# SDK, I updated Microsoft.PowerShell.Commands.Management from 7.1.5 to 7.2.1.

The SDK no longer has references to the following commands:

JoinPathCommand
TestPathCommand
GetChildItemCommand
GetItemCommand
SetItemCommand

If this was intentional, how should I be referencing these commands?

Expected behavior

I need to import the commands listed under steps to reproduce

Actual behavior

I can now longer use the commands listed under steps to reproduce

Error details

No response

Environment data

Key                       Value
---                       -----
PSVersion                 7.2.1
PSEdition                 Core
GitCommitId               7.2.1
OS                        Linux 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021
Platform                  Unix
PSCompatibleVersions      {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion      1.1.0.1
WSManStackVersion         3.0

Visuals

No response

The text was updated successfully, but these errors were encountered:

colinblaise · 2022-02-09T17:46:58Z

Related - #16141

dkattan · 2022-03-07T12:42:29Z

Further, if you try to include Microsoft.PowerShell.Commands.Management from NuGet you get the error:

Assembly 'Microsoft.PowerShell.Commands.Management' with identity 'Microsoft.PowerShell.Commands.Management, Version=7.3.0.2, Culture=neutral, PublicKeyToken=31bf3856ad364e35' uses 'System.Management.Automation, Version=7.3.0.2, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'System.Management.Automation' with identity 'System.Management.Automation, Version=7.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

dkattan · 2022-12-05T21:10:12Z

@SeeminglyScience @adityamandaleeka @TravisEz13

There are 2 problems:

Microsoft.PowerShell.SDK is missing an assembly reference to Microsoft.PowerShell.Commands.Management.dll, Microsoft.PowerShell.Commands.Diagnostics, Microsoft.PowerShell.Security, and Microsoft.WSMan.Management
Microsoft.PowerShell.Commands.Management references System.Management.Automation.dll 7.3.0.500 while Microsoft.PowerShell.SDK references 7.3.0.0

Personally, I don't really care about 2 because I only needed it due to the missing reference in Microsoft.PowerShell.SDK

Problem 1

I believe to fix it we need to the missing assemblies to the $supportedRefList array to this block of code:

PowerShell/tools/packaging/packaging.psm1

Lines 2265 to 2267 in 07175ae

    
           $supportedRefList = @( 
        
               "Microsoft.PowerShell.Commands.Utility", 
        
               "Microsoft.PowerShell.ConsoleHost")

and also to

PowerShell/tools/packaging/packaging.psm1

Lines 2456 to 2460 in 07175ae

    
           $assemblyNames = @( 
        
               "System.Management.Automation", 
        
               "Microsoft.PowerShell.Commands.Utility", 
        
               "Microsoft.PowerShell.ConsoleHost" 
        
           )

Problem 2

If you are interested in also fixing the mismatch in problem 2, if you add a hintpath you can get Visual Studio to tell you more information about the issue:

Before

<ItemGroup>
    <PackageReference Include="Microsoft.PowerShell.SDK" Version="7.1.5" />
    <PackageReference Include="Microsoft.PowerShell.Commands.Management" Version="7.1.5"/>
</ItemGroup>

After

<ItemGroup>
    <PackageReference Include="Microsoft.PowerShell.SDK" Version="7.1.5" />
    <PackageReference Include="Microsoft.PowerShell.Commands.Management" Version="7.1.5">
      <GeneratePathProperty>True</GeneratePathProperty>
    </PackageReference>
  </ItemGroup>

  <ItemGroup>
    <Reference Include="Microsoft.PowerShell.Commands.Management"> 
<HintPath>$(PkgMicrosoft_powershell_commands_management)\runtimes\unix\lib\net6.0\Microsoft.PowerShell.Commands.Management.dll</HintPath>
    </Reference>
  </ItemGroup>

Found conflicts between different versions of "System.Management.Automation" that could not be resolved.
There was a conflict between "System.Management.Automation, Version=7.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" and "System.Management.Automation, Version=7.3.0.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35".
    "System.Management.Automation, Version=7.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" was chosen because it was primary and "System.Management.Automation, Version=7.3.0.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35" was not.
    References which depend on "System.Management.Automation, Version=7.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" [C:\Users\DKattan.IN\.nuget\packages\system.management.automation\7.3.0\ref\net7.0\System.Management.Automation.dll].
        C:\Users\DKattan.IN\.nuget\packages\system.management.automation\7.3.0\ref\net7.0\System.Management.Automation.dll
          Project file item includes which caused reference "C:\Users\DKattan.IN\.nuget\packages\system.management.automation\7.3.0\ref\net7.0\System.Management.Automation.dll".
            C:\Users\DKattan.IN\.nuget\packages\system.management.automation\7.3.0\ref\net7.0\System.Management.Automation.dll
    References which depend on "System.Management.Automation, Version=7.3.0.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35" [].
        C:\Users\DKattan.IN\.nuget\packages\microsoft.powershell.commands.management\7.3.0\runtimes\unix\lib\net7.0\Microsoft.PowerShell.Commands.Management.dll
          Project file item includes which caused reference "C:\Users\DKattan.IN\.nuget\packages\microsoft.powershell.commands.management\7.3.0\runtimes\unix\lib\net7.0\Microsoft.PowerShell.Commands.Management.dll".
            Microsoft.PowerShell.Commands.Management
1>CSC : error CS1705: Assembly 'Microsoft.PowerShell.Commands.Management' with identity 'Microsoft.PowerShell.Commands.Management, Version=7.3.0.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35' uses 'System.Management.Automation, Version=7.3.0.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'System.Management.Automation' with identity 'System.Management.Automation, Version=7.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
1>Done building project "TestPowerShell73Dependency2.csproj" -- FAILED.

adityapatwardhan · 2022-12-06T19:42:18Z

@dkattan Could you please provide the full csproj? I would like to see the target framework.

If targeting NET6 -> use Microsoft.Powershell.SDK v 7.2.7
If targeting NET7 -> use Microsoft.Powershell.SDK v 7.3.0

v7.1.x is out of support and should not be used. Also, v7.0.x is out of support.

dkattan · 2022-12-09T14:24:16Z

@dkattan Could you please provide the full csproj? I would like to see the target framework.

If targeting NET6 -> use Microsoft.Powershell.SDK v 7.2.7 If targeting NET7 -> use Microsoft.Powershell.SDK v 7.3.0

v7.1.x is out of support and should not be used. Also, v7.0.x is out of support.

TestPowerShell73Dependency2.zip

csproj

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

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net7.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.PowerShell.SDK" Version="7.3.0" />
  </ItemGroup>

</Project>

Program.cs

// See https://aka.ms/new-console-template for more information
using System.Management.Automation.Runspaces;

Console.WriteLine("Hello, World!");
var iss = InitialSessionState.CreateDefault2();
iss.Commands.Add(new SessionStateCmdletEntry("Resolve-Path", typeof(Microsoft.PowerShell.Commands.ResolvePathCommand), null));

dkattan · 2022-12-21T11:36:42Z

@SeeminglyScience I saw some work done in #18782 v7.4.0-preview.1 related to nuget packages, any chance we can get some traction on this? I just updated my test project to Microsoft.PowerShell.SDK v7.4.0-preview.1 and the problem persists.

dkattan · 2023-01-23T21:07:36Z

Hey @adityapatwardhan Any update on this?

bironeaj · 2023-01-23T22:28:29Z

@adityapatwardhan we are having this issue too. Any update?

adityapatwardhan · 2023-01-23T22:32:59Z

This issue is not fixed yet. I am working on it and hopefully will be done soon. Thank you for your patience.

bretesq · 2023-01-24T19:06:05Z

@adityapatwardhan We are also seeing this issue. Any luck with a timeline on this?

dkattan · 2023-01-24T22:45:23Z

Still an issue on 7.3.2, SDK is unusable

@SeeminglyScience @adityapatwardhan @andschwa

dkattan · 2023-01-25T18:56:35Z

@adityapatwardhan Can you look at my merge request and perhaps test it since you have access to the required DevOps environment? #19033

adityapatwardhan · 2023-03-09T22:50:37Z

This PR should fix the problem: #19302

We plan to release the next PowerShell Preview with this change.

dkattan · 2023-03-10T02:49:30Z

This PR should fix the problem: #19302

We plan to release the next PowerShell Preview with this change.

Yaaass. While you’re in there, any love for SourceLink or Debug symbols? 🥺

adityapatwardhan · 2023-03-13T18:53:17Z

Not right now at least. But maybe in a separate PR.

dkattan · 2023-03-13T18:56:50Z

Not right now at least. But maybe in a separate PR.

Like perhaps this one you created 5 years ago?

#8184

adityapatwardhan · 2023-03-14T22:27:23Z

@dkattan The Microsoft.PowerShell.SDK version v7.4.0-preview.2 will be available on NuGet.org in sometime. Could you please help validate that your scenario is fixed by that?

dkattan · 2023-03-15T14:27:59Z

@dkattan The Microsoft.PowerShell.SDK version v7.4.0-preview.2 will be available on NuGet.org in sometime. Could you please help validate that your scenario is fixed by that?

I'm trying but I'm not yet seeing it in nuget.

dkattan · 2023-03-16T10:36:14Z

@dkattan The Microsoft.PowerShell.SDK version v7.4.0-preview.2 will be available on NuGet.org in sometime. Could you please help validate that your scenario is fixed by that?

I'm trying but I'm not yet seeing it in nuget.

I found it, I didn't have the Include Prerelease box checked.

Evidently it requires .NET 8 which requires Visual Studio 2022 17.6 Preview. Got all that installed.

When I attempt to install Microsoft.PowerShell.SDK or Microsoft.PowerShell.Commands.Utility I get:

Severity	Code	Description	Project	File	Line	Suppression State
Error	NU1102	Unable to find package Microsoft.CodeAnalysis.CSharp with version (>= 4.6.0-2.23152.6)
  - Found 142 version(s) in nuget.org [ Nearest version: 4.6.0-1.final ]
  - Found 0 version(s) in Microsoft Visual Studio Offline Packages	TestPowerShell73Dependency2	C:\Users\DKattan\source\repos\TestPowerShell73Dependency2\TestPowerShell73Dependency2\TestPowerShell73Dependency2.csproj	1

System.Management.Automation, Microsoft.PowerShell.Commands.Diagnostics and Microsoft.PowerShell.Commands.Management install fine.

Installing Microsoft.PowerShell.Commands.Management 7.4.0-preview.2 does solve the problem for TestPathCommand.

colinblaise added the Needs-Triage The issue is new and needs to be triaged by a work group. label Feb 9, 2022

iSazonov added the WG-DevEx-SDK hosting PowerShell as a runtime, PowerShell's APIs, PowerShell Standard, or development of modules label Feb 9, 2022

adityapatwardhan self-assigned this Jan 4, 2023

dkattan mentioned this issue Jan 25, 2023

Hotfix/nuget packages #19033

Closed

22 tasks

msftbot bot added the In-PR Indicates that a PR is out for the issue label Jan 25, 2023

iSazonov mentioned this issue Feb 2, 2023

Could not load file or assembly 'System.Management.Automation' after update to .NET 7 #19078

Open

5 tasks

msftbot bot removed the In-PR Indicates that a PR is out for the issue label Mar 14, 2023

TestPathCommand and several others removed in PowerShell 7.2 SDK #16862

TestPathCommand and several others removed in PowerShell 7.2 SDK #16862

colinblaise commented Feb 9, 2022

colinblaise commented Feb 9, 2022

dkattan commented Mar 7, 2022

dkattan commented Dec 5, 2022 •

edited

adityapatwardhan commented Dec 6, 2022

dkattan commented Dec 9, 2022

dkattan commented Dec 21, 2022

dkattan commented Jan 23, 2023

bironeaj commented Jan 23, 2023

adityapatwardhan commented Jan 23, 2023

bretesq commented Jan 24, 2023

dkattan commented Jan 24, 2023

dkattan commented Jan 25, 2023

adityapatwardhan commented Mar 9, 2023

dkattan commented Mar 10, 2023

adityapatwardhan commented Mar 13, 2023

dkattan commented Mar 13, 2023

adityapatwardhan commented Mar 14, 2023

dkattan commented Mar 15, 2023

dkattan commented Mar 16, 2023

Mar	APR	May
	06
2022	2023	2024

TestPathCommand and several others removed in PowerShell 7.2 SDK #16862

TestPathCommand and several others removed in PowerShell 7.2 SDK #16862

Comments

colinblaise commented Feb 9, 2022

Prerequisites

Steps to reproduce

Expected behavior

Actual behavior

Error details

Environment data

Visuals

colinblaise commented Feb 9, 2022

dkattan commented Mar 7, 2022

dkattan commented Dec 5, 2022 • edited

Problem 1

Problem 2

adityapatwardhan commented Dec 6, 2022

dkattan commented Dec 9, 2022

dkattan commented Dec 21, 2022

dkattan commented Jan 23, 2023

bironeaj commented Jan 23, 2023

adityapatwardhan commented Jan 23, 2023

bretesq commented Jan 24, 2023

dkattan commented Jan 24, 2023

dkattan commented Jan 25, 2023

adityapatwardhan commented Mar 9, 2023

dkattan commented Mar 10, 2023

adityapatwardhan commented Mar 13, 2023

dkattan commented Mar 13, 2023

adityapatwardhan commented Mar 14, 2023

dkattan commented Mar 15, 2023

dkattan commented Mar 16, 2023

dkattan commented Dec 5, 2022 •

edited