-
-
Notifications
You must be signed in to change notification settings - Fork 11
Migrate to .NET 6 #68
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
src/GitExtensions.PluginManager/GitExtensions.PluginManager.csproj
Outdated
Show resolved
Hide resolved
src/GitExtensions.PluginManager/GitExtensions.PluginManager.csproj
Outdated
Show resolved
Hide resolved
src/GitExtensions.PluginManager/GitExtensions.PluginManager.csproj
Outdated
Show resolved
Hide resolved
|
I believe you also need to update appveyor.yaml to list "Visual Studio 2022" for .net 6 support |
|
The current error is Waiting for gitextensions/gitextensions.extensibility#26 |
gerhardol
left a comment
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.
+1
Obviously needed.
I do not have the knowledge to say that this is the only needed changes (there are later steps though...)
|
I'm seeing this warning locally: |
|
https://www.nuget.org/packages/GitExtensions.Extensibility/0.3.0.57 is published, but it may be a little while before it becomes available. |
Me too, but I don't have capacity at the moment to update these packages. |
May be someone could help. Are these packages public? |
What I meant is whether the warnings are blocker for merging this PR? |
|
Yes, it's a blocker, we can't build it.
…On Tue, 22 Nov 2022 at 21:08, Marek Fišera ***@***.***> wrote:
This is a blocker for the release of 4.0.1, which is addressing few very
public issues.
What I meant is whether the warnings are blocker for merging this PR?
If not, I can do it later.
—
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBTEXS5V5QTHIAZLRXEWMDWJSLSPANCNFSM6AAAAAAR3TQIXI>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
|
Ok, I'll work on it. |
I have no idea :D |
|
@RussKie I have updated Neptuo packages and applied nullable annotations as you required in your commit. |
|
Build fails:
|
I think |
- error NU5103: The folder 'lib\ PackageManager\PackageManager.UI.exe' under 'lib' is not recognized as a valid framework name or a supported culture identifier. Rename itto a valid framework name or culture identifier. - error NU5101: The assembly 'li b\GitExtensions.PluginManager.dll' is placed directly under 'lib' folder. It is recommended that assemblies be placed inside a framework-specific folder. Move it into a framework-specific folder. - error NU5128: Some target fram eworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below: - Add a dependency group for PackageManager0.0 to the nuspec
GitExtensions.PluginManager shouldn't reference custom nuget packages to avoid version conflicts. It least I think that was the original idea for ArgsFix.cs.
👍 |
|
Hopefully last thing, versioning on AppVeyor is broken. |
|
@RussKie Do you know why appveyor produces versions
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
It appears gitextensions.pluginmanager/src/GitExtensions.PluginManager/GitExtensions.PluginManager.csproj Lines 87 to 89 in 4e3ba18
|
|
I've pulled it locally, and the tests wouldn't build. This had me scratching head for quite some time, and I'm surprised it was working on the CI... The order of imports of package references was incorrect, those need to be defined in the props file instead of the targets file. The local dev is also something that needs improving - I was unable to build the solution by |
|
v2.0.0 was never published... |
🤦 |



TODO
Fixes #67