Skip to content

Cross target .NET 5.0 and 3.1 #159

@Tratcher

Description

@Tratcher
Member

Multiple partners have said that they will be able to adopt YARP sooner if we provide a netcoreapp3.1 target. We can cross target the package and light up new functionality. We'll want to have a doc tracking things that won't work on 3.1.

Activity

added this to the 1.0.0-preview2 milestone on May 12, 2020
self-assigned this
on May 14, 2020
added a commit that references this issue on May 15, 2020
kasini3000

kasini3000 commented on May 16, 2020

@kasini3000

mypoint:
If there is a lot of work for compatibility with .net core 3.1, I suggest not supporting it first. And through the powershell command line support.

Q: Will YARP provide compatibility with .net core 3.1?
A:
You can use the .net core3.1 client to access YARP through the command line, after ssh, there is a powershell command line interface. This command line interface is compatible with any external calls such as win, linux, python, etc.

user app want add back end to YARP--->commandline--->ssh client---> ssh server--->
powershell YARP module (powershell 7.1 preview base .net core 5)
---> the static method of .net core 5 of YARP
powershell eg:
1 Add-Type -Path "d:\yarp.dll" or "/xxx/yarp.dll"
2[YARP]::add_urlrewrite('http://11/aa/bb','http://22/cc/dd')

in windows via:winrm client --->winrm server

Tratcher

Tratcher commented on May 16, 2020

@Tratcher
MemberAuthor

If there is a lot of work for compatibility with .net core 3.1, I suggest not supporting it first.

So far almost every works, the main 5.0 improvements have been in performance. We'll see if we run into any roadblocks later on.

kasini3000

kasini3000 commented on May 17, 2020

@kasini3000

ok,3q

2 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Priority:0Used for divisional .NET planningType: EnhancementNew feature or requestUser StoryUsed for divisional .NET planning

Type

No type

Projects

No projects

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @Tratcher@samsp-msft@kasini3000

      Issue actions

        Cross target .NET 5.0 and 3.1 · Issue #159 · dotnet/yarp