Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Dotnet Isolated runtime specific dependencies and cleanup durableUtils #3597

Merged
merged 9 commits into from
Mar 1, 2023

Conversation

MicroFish91
Copy link
Contributor

@MicroFish91 MicroFish91 commented Feb 28, 2023

Add .NET Isolated runtime specific dependencies, specifically for Netherite and MSSQL storage types.

Partially addresses the error message shown in #3566.

@MicroFish91 MicroFish91 changed the title Add Dotnet Isolated runtime specific dependencies Add Dotnet Isolated runtime specific dependencies and cleanup durableUtils Feb 28, 2023
// Seems that the package arrives out-dated and needs to be updated to at least 2.9.1;
// otherwise, error appears when running with sql backend
if (!isDotnetIsolated) {
packageNames.push(dotnetLtsDfBasePackage);
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not 100% sure if this is the best way to handle this; let me know if anyone has opinions on if this should be handled differently.

@MicroFish91 MicroFish91 marked this pull request as ready for review March 1, 2023 00:11
@MicroFish91 MicroFish91 requested a review from a team as a code owner March 1, 2023 00:11
@@ -111,19 +113,9 @@ export namespace durableUtils {
// eslint-disable-next-line @typescript-eslint/no-unsafe-assignment, @typescript-eslint/no-explicit-any, @typescript-eslint/no-unsafe-member-access
let packageReferences = result?.['Project']?.['ItemGroup']?.[0]?.PackageReference ?? [];
Copy link
Member

Choose a reason for hiding this comment

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

Unrelated to this PR, but there is a bug here if the package references are split into multiple item groups since we're only using the first item group. I can fix this in a separate PR.

Copy link
Contributor Author

@MicroFish91 MicroFish91 Mar 1, 2023

Choose a reason for hiding this comment

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

Ahh good catch! It should probably loop through the 'ItemGroup'[] and check for the 'PackageReference' instead

@MicroFish91 MicroFish91 merged commit c17edf5 into main Mar 1, 2023
@MicroFish91 MicroFish91 deleted the mwf/durable-dotnet-isolated branch March 1, 2023 18:51
@microsoft microsoft locked and limited conversation to collaborators Apr 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants