Skip to content

Conversation

@maraf
Copy link
Member

@maraf maraf commented Nov 9, 2022

  • Migrate all projects to .NET 6
  • Update all nuget references
  • Unify common properties in Directory.Build.props

TODO

  • Update GitExtensions.Extensibility version
  • Update Neptuo.* to .NET

Fixes #67

@maraf maraf requested a review from RussKie November 9, 2022 16:21
@maraf maraf self-assigned this Nov 9, 2022
@dfev77
Copy link

dfev77 commented Nov 11, 2022

I believe you also need to update appveyor.yaml to list "Visual Studio 2022" for .net 6 support

@maraf
Copy link
Member Author

maraf commented Nov 13, 2022

The current error is error NU1102: Unable to find package GitExtensions.Extensibility with version (>= 0.3.0)

Waiting for gitextensions/gitextensions.extensibility#26

@maraf maraf requested a review from RussKie November 13, 2022 08:38
Copy link
Member

@gerhardol gerhardol left a 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...)

@RussKie
Copy link
Member

RussKie commented Nov 13, 2022

I'm seeing this warning locally:

D:\Development\gitextensions.pluginmanager\src\PackageManager.UI\PackageManager.UI.csproj : error NU1701: Package 'Neptuo.Exceptions 1.2.1' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7 
, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net6.0-windows7.0'. This package may not be fully compatible with your project. [D:\D 
evelopment\gitextensions.pluginmanager\GitExtensions.PluginManager.sln]

@RussKie
Copy link
Member

RussKie commented Nov 13, 2022

https://www.nuget.org/packages/GitExtensions.Extensibility/0.3.0.57 is published, but it may be a little while before it becomes available.

@maraf
Copy link
Member Author

maraf commented Nov 14, 2022

I'm seeing this warning locally:

Me too, but I don't have capacity at the moment to update these packages.
Is it blocker from your point of view for this release?
All the scenarios work.

@RussKie
Copy link
Member

RussKie commented Nov 22, 2022

Me too, but I don't have capacity at the moment to update these packages.
Is it blocker from your point of view for this release?
All the scenarios work.

May be someone could help. Are these packages public?
This is a blocker for the release of 4.0.1, which is addressing few very public issues.

@maraf
Copy link
Member Author

maraf commented Nov 22, 2022

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. As the app works.

@RussKie
Copy link
Member

RussKie commented Nov 22, 2022 via email

@maraf
Copy link
Member Author

maraf commented Nov 22, 2022

Ok, I'll work on it.
Btw. How did you build the .NET 5 version? Because the packages didn't change to quite some time.

@RussKie
Copy link
Member

RussKie commented Nov 23, 2022

How did you build the .NET 5 version? Because the packages didn't change to quite some time.

I have no idea :D

@maraf
Copy link
Member Author

maraf commented Dec 1, 2022

@RussKie I have updated Neptuo packages and applied nullable annotations as you required in your commit.
Please, go through the changes, if I missed something. Btw. the build was broken by one of the changes that treated warnings as errors.

@gerhardol
Copy link
Member

Build fails:

C:\projects\gitextensions-pluginmanager\src\GitExtensions.PluginManager\GitExtensions.PluginManager.csproj(58,5): error MSB3030: Could not copy the file "..\PackageManager.UI\bin\Release\net6.0-windows\publish\PackageManager.UI.exe" because it was not found.

@RussKie
Copy link
Member

RussKie commented Dec 2, 2022

...and applied nullable annotations as you required in your commit.

I think <nullable>enable</nullable> slipped through as I copied the lot from another place. It'd be great to remove nullable annotations to another PR so we can review it independently.

- 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
@maraf maraf requested a review from RussKie December 5, 2022 10:18
GitExtensions.PluginManager shouldn't reference custom nuget packages to avoid version conflicts.
It least I think that was the original idea for ArgsFix.cs.
@maraf maraf added this to the 2.0.0 milestone Dec 5, 2022
@RussKie
Copy link
Member

RussKie commented Dec 5, 2022

EDIT: probably figured it out..

👍

@maraf
Copy link
Member Author

maraf commented Dec 5, 2022

@maraf
Copy link
Member Author

maraf commented Dec 5, 2022

@RussKie Do you know why appveyor produces versions 0.0.0.* althou the yaml descriptor contains 2.0.0.*?

version: 2.0.0.{build}

@RussKie

This comment was marked as resolved.

@RussKie

This comment was marked as resolved.

@RussKie
Copy link
Member

RussKie commented Dec 6, 2022

Do you know why appveyor produces versions 0.0.0.* althou the yaml descriptor contains 2.0.0.*?

It appears $(PackageVersion) isn't set correctly:

<Target Name="Zip" AfterTargets="Pack">
<Exec Command="powershell -ExecutionPolicy Unrestricted $(MSBuildProjectDirectory)\..\..\tools\Zip-GitExtensionsPlugin.ps1 -Version $(PackageVersion) -Configuration $(Configuration)" />
</Target>

image

@RussKie
Copy link
Member

RussKie commented Dec 13, 2022

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 dotnet build as it would also try to generate a nuspec and package the app. But I'll leave it for another day.

@RussKie
Copy link
Member

RussKie commented Dec 13, 2022

Do you know why appveyor produces versions 0.0.0.* althou the yaml descriptor contains 2.0.0.*?

It appears $(PackageVersion) isn't set correctly:

This
image

@RussKie
Copy link
Member

RussKie commented Dec 13, 2022

Looks like we're in business!
image

@RussKie RussKie merged commit 3b53e6e into gitextensions:master Dec 13, 2022
@RussKie RussKie modified the milestones: 2.0.0, 3.0.0 Dec 13, 2022
@maraf maraf deleted the Net6 branch December 13, 2022 12:39
@maraf
Copy link
Member Author

maraf commented Dec 13, 2022

v2.0.0 was never published...
Git Extensions v3.5.x was using v1.1

@RussKie RussKie modified the milestones: 3.0.0, 2.1.0, 2.0.0 Dec 14, 2022
@RussKie
Copy link
Member

RussKie commented Dec 14, 2022

v2.0.0 was never published...

🤦
Reverted to 2.0. We haven't published anything, so no harm done.

@RussKie RussKie modified the milestones: 2.0.0, 2.1.0 Dec 14, 2022
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.

Mismatch between .Net version required by GitExt 4.0.0 & PackageManager

4 participants