Skip to content

Update Lambda PowerShell to target .NET 8 runtime#1674

Merged
normj merged 2 commits intonet8-stagingfrom
normj/dotnet8-powershell
Feb 21, 2024
Merged

Update Lambda PowerShell to target .NET 8 runtime#1674
normj merged 2 commits intonet8-stagingfrom
normj/dotnet8-powershell

Conversation

@normj
Copy link
Copy Markdown
Member

@normj normj commented Feb 17, 2024

Description of changes:
In preparation for the upcoming .NET 8 release update the AWSLambdaPSCore module for publishing PowerShell scripts to target .NET 8 and the upcoming .NET 8 Lambda runtime.

This follows the pattern we have done for previous runtime releases. The module has a major version update to v4. Users that take the v4 major version update will deploy to .NET 8. If users want to stay with .NET 6 then they need to keep using the v3.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

<ItemGroup Condition="'$(TargetFramework)' == 'netcoreapp2.1'">
<PackageReference Include="Microsoft.PowerShell.SDK" Version="6.0.4" />
<ItemGroup Condition="'$(TargetFramework)' == 'net6.0'">
<PackageReference Include="Microsoft.PowerShell.SDK" Version="7.2.1" />
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious/don't need to see changes, but any reason for 7.2.1 over 7.2.18 (looks like the most recent .NET 6 release)?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to version 7.2.18.


<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
<TargetFrameworks>net6.0;net8.0</TargetFrameworks>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is net6.0 target needed?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically somebody could stick with the old major version of the module and have a "PowerShell Lambda .NET project" and update to this new major version of Amazon.Lambda.PowerShellHost. An unlikely scenario but since .NET 6 is still in support I'm not ready to rule it out.

@normj normj merged commit bef47f8 into net8-staging Feb 21, 2024
@normj normj deleted the normj/dotnet8-powershell branch February 21, 2024 00:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants