-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Converting to GitHub Actions #2699
Conversation
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@jeromelaban when you get a chance if you could help take a look at why the Uno side is failing it would be greatly appreciated |
@@ -23,7 +23,7 @@ Prism.Wpf helps you more easily design and build rich, flexible, and easy to mai | |||
<Reference Include="System.Configuration" /> | |||
</ItemGroup> | |||
|
|||
<ItemGroup Condition=" $(TargetFramework.StartsWith('netcore')) OR $(TargetFramework.StartsWith('net5'))"> | |||
<ItemGroup Condition=" $(TargetFramework.StartsWith('netcore')) OR $(TargetFramework.StartsWith('net6'))"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dansiegel just wondering if it would be more beneficial to use the symbols NETFRAMEWORK and NETCOREAPP to do this portion for future target framework changes to Prism WPF.
Implementation for this condition would be: $(DefineConstants.Contains('NETCOREAPP'))
Description
Switching automated builds from Azure DevOps to GitHub Actions to keep everything Prism tied closer to the main Prism Repo.