Darren Kattan

I'm also experiencing this issue. Any chance someone can get this patched?

@andyleejordan Curious your thoughts on this. It ended up being heavier-handed than I wanted with all the async changes, but I'm wondering if that would be desirable if I split...

@TravisEz13 Can you take a look at this and let me know what you think?

I am in favor of this! I did not know that PS 5.1 did this automatically.

I would love to see WhatIf messages on the InformationStream. I'm trying to use the WhatIf output to test if certain things exist already, like a compliance check. It would...

> Just hit this too, my use case however is slightly different. I had a function of a module that would output which items it modifies when "WhatIf" was specified,...

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...

@SeeminglyScience @adityamandaleeka @TravisEz13 There are 2 problems: 1. 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 2. Microsoft.PowerShell.Commands.Management references System.Management.Automation.dll 7.3.0.500 while Microsoft.PowerShell.SDK references 7.3.0.0 Personally,...

> @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...

@SeeminglyScience I saw some work done in https://github.com/PowerShell/PowerShell/issues/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...