-
-
Notifications
You must be signed in to change notification settings - Fork 11
Migration to .NET 5 #58
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
Conversation
- Replaced costura with .NET single file publish. - Fixed package source ordering in Nuget.PackageManagement-v5.11.0.
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.
Looks sensible
I'm testing the .NET 5.0 release, and the Plugin Manager is failing to start with the following error:
It looks like it is looking for PackageManager.UI.dll, and there's only a PackageManager.UI.exe.... |
You can grab build artifacts here: https://ci.appveyor.com/project/gitextensions/gitextensions/builds/41427744/artifacts, or use the branch if you want to build it locally: https://github.com/gitextensions/gitextensions/tree/msi |
@RussKie Are you using MSI or portable? Because with portable from the link about it seems the PM is working (it shows an error with reading settings, but the PM starts and works). I struggling to run the installer on sandbox machine. I have there .NET 5.0.12 runtime, but it still says that I don't and clicking yes does nothing. Anyway, the portable version runs there... |
💡 Also, the installer and portable still contains an previous PM version (1.1.0.109). |
gitextensions/gitextensions#9704 to build installer with msbuild explicitly |
I built the msi locally having downloaded the latest version of the PM
manually.
Then installed the msi.
…On Tue, 9 Nov 2021, 8:01 am Gerhard Olsson, ***@***.***> wrote:
gitextensions/gitextensions#9704
<gitextensions/gitextensions#9704> to build
installer with msbuild explicitly
(but I do not get it built myself)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#58 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBTEXQDIDNNWNBVQ6SS343ULA3BHANCNFSM5HDVRPHQ>
.
|
I probably found the problem. The build on AppVeyor doesn't work as locally. Size of these artifacts should be about 4MB. The problem is with single file publish of PackageManager UI. When I run the build script ( @RussKie Any ideas? |
- Moving package down in sources collection wasn't working. - Remove --no-build from Run-Tests.ps1, because we don't build whole solution in previous steps.
- Replace publish profile with direct arguments in Prepare-Release.ps1. - Generate binlogs during publish. This is follow-up to gitextensions#58.
Fixes #57.