You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: port-plugins.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
### Notes
4
4
5
5
- When porting, please keep the author's commit history
6
-
- Flow Launcher targets .Net Core 3.1, so plugins should also be upgraded to keep the continuity of future developments
6
+
- Flow Launcher targets .Net 5, so plugins should also be upgraded to keep the continuity of future developments
7
7
- All dll libraries used by the plugin should be outputted and included in the final build, to do this, set the attribute CopyLocalLockFileAssemblies in your project file to true
8
8
9
9
### Steps
@@ -12,7 +12,7 @@
12
12
2. Use try convert tool from https://github.com/dotnet/try-convert
4. May need to fix on the project file, a good template to follow is the [Explorer plugin](https://github.com/Flow-Launcher/Flow.Launcher/blob/dev/Plugins/Flow.Launcher.Plugin.Explorer/Flow.Launcher.Plugin.Explorer.csproj) project:
15
-
- fix <TargetFramework> to netcoreapp3.1
15
+
- fix <TargetFramework> to net5.0-windows
16
16
- set the output location as 'Output\Release\<name of the project>'
17
17
- add `<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>` and `<AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>` to the csproj file
18
18
- bump version to 2.0.0 and fix up any missing attributes if neccessary
0 commit comments