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

How to deal with our two .NET/CSharp Wechaty project #4

Closed
huan opened this issue Sep 28, 2020 · 2 comments
Closed

How to deal with our two .NET/CSharp Wechaty project #4

huan opened this issue Sep 28, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@huan
Copy link
Member

huan commented Sep 28, 2020

Current we have two .NET Wechaty projects related to your issue:

It would be great for our community if we can have a plan to make it clear for the developers for how to use our .NET/CSharp Wechaty.

The details are to be discussed.

Please feel free to let me know if you have any good suggestions @echofool @Jesn

Related Issues: wechaty/wechaty#2070

@huan
Copy link
Member Author

huan commented Oct 28, 2020

Update: We decided to merge the two together!

After a discussion with @echofool and @Jesn on WeChat, we decided that it would be our best choice to merge https://github.com/Jesn/dotnet-wechaty to https://github.com/wechaty/dotnet-wechaty so that we can keep our codebase simple and focus, and all .Net users will use one dotnet-wechaty.

Todo-list

@huan huan added the enhancement New feature or request label Oct 28, 2020
@Jesn
Copy link
Contributor

Jesn commented Dec 4, 2020

After discussion , .Net Wechaty use native, ABP Wechaty is not maintained,

dotnet-wechaty-getting-started ==> https://github.com/wechaty/dotnet-wechaty-getting-started

@Jesn Jesn closed this as completed Dec 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants