Skip to content
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

Cross target .NET 5.0 and 3.1 #159

Closed
Tratcher opened this issue May 12, 2020 · 3 comments
Closed

Cross target .NET 5.0 and 3.1 #159

Tratcher opened this issue May 12, 2020 · 3 comments
Assignees
Labels
Priority:0 Used for divisional .NET planning Type: Enhancement New feature or request User Story Used for divisional .NET planning

Comments

@Tratcher
Copy link
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.

@kasini3000
Copy link

kasini3000 commented May 16, 2020

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
Copy link
Member Author

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
Copy link

ok,3q

@samsp-msft samsp-msft added the User Story Used for divisional .NET planning label Oct 21, 2020
@samsp-msft samsp-msft added the Priority:0 Used for divisional .NET planning label Jan 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:0 Used for divisional .NET planning Type: Enhancement New feature or request User Story Used for divisional .NET planning
Projects
None yet
Development

No branches or pull requests

3 participants