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

Could you guys let some of the team members go to update WCF of Xamarin.Android and Xamarin.iOS? #1688

Open
huangjinshe opened this Issue Dec 4, 2016 · 29 comments

Comments

Projects
None yet
9 participants
@huangjinshe

huangjinshe commented Dec 4, 2016

Since WCF supported cross platform, We All need some features on the other platform such like Duplex Channel. But until now, it's not finished for Xamarin.Android and Xamarin.iOS.

We know Xamarin already belong to the Microsoft now, It would be very helpful if WCF team just let some one go to improve the feature of WCF for Xamarin, that will be very helpful for every one.

There are a lot of user want it too: More advanced/complete support for WCF

@zhenlan

This comment has been minimized.

Show comment
Hide comment
@zhenlan

zhenlan Dec 8, 2016

Member

@terrajobst can you help to route the feedback to Xamarin folks? It will be great if Xamarin can leverage WCF code on Core or full framework.

Member

zhenlan commented Dec 8, 2016

@terrajobst can you help to route the feedback to Xamarin folks? It will be great if Xamarin can leverage WCF code on Core or full framework.

@zhenlan zhenlan added this to the Future milestone Dec 8, 2016

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Dec 24, 2016

@terrajobst ,sorry for bothering, but is there any response from Xamarin team? Because if that will take too much time such like a year. I think we need to replace another solution instead of WCF for other platform, currently still waiting for that.

huangjinshe commented Dec 24, 2016

@terrajobst ,sorry for bothering, but is there any response from Xamarin team? Because if that will take too much time such like a year. I think we need to replace another solution instead of WCF for other platform, currently still waiting for that.

@terrajobst

This comment has been minimized.

Show comment
Hide comment
@terrajobst

terrajobst Dec 27, 2016

Member

Hey @marek-safar and @akoeplinger. Could you chime in?

Member

terrajobst commented Dec 27, 2016

Hey @marek-safar and @akoeplinger. Could you chime in?

@akoeplinger

This comment has been minimized.

Show comment
Hide comment
@akoeplinger

akoeplinger Jan 2, 2017

Member

@marek-safar as far as I know Marcos did a prototype on using the corefx WCF sources, do you know where we ended up with this?

Member

akoeplinger commented Jan 2, 2017

@marek-safar as far as I know Marcos did a prototype on using the corefx WCF sources, do you know where we ended up with this?

@marek-safar

This comment has been minimized.

Show comment
Hide comment
@marek-safar

marek-safar Jan 2, 2017

I am not sure why do you think WCF is cross platform but Xamarin WCF support is limited. I don't think this is going to change anytime soon (if ever) as WCF is large and has many hard to port dependencies.

We plan to (would like to) support full subset of WCF .NET Core client APIs but that work has been postponed few times already.

marek-safar commented Jan 2, 2017

I am not sure why do you think WCF is cross platform but Xamarin WCF support is limited. I don't think this is going to change anytime soon (if ever) as WCF is large and has many hard to port dependencies.

We plan to (would like to) support full subset of WCF .NET Core client APIs but that work has been postponed few times already.

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Jan 2, 2017

@marek-safar ,I don't know about other features, but only the Duplex channel we want it so badly for so long time. I really hope you guys has some priority levels for the new implementation. I feel we're losing WCF in the mobile age.

huangjinshe commented Jan 2, 2017

@marek-safar ,I don't know about other features, but only the Duplex channel we want it so badly for so long time. I really hope you guys has some priority levels for the new implementation. I feel we're losing WCF in the mobile age.

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Apr 23, 2017

@marek-safar , Is there any good news now? espetially for TCP Duplex channel.

huangjinshe commented Apr 23, 2017

@marek-safar , Is there any good news now? espetially for TCP Duplex channel.

@EdHyman

This comment has been minimized.

Show comment
Hide comment
@EdHyman

EdHyman Apr 25, 2017

The duplexchannelfactory was working as intended on a previous version of Xamarin Studio. I upgrade to a new version of OS (from Yosemite to El Capitan) and install Xamarin updates as well, then I receive this nonimplementedexception error. My previously compiled code running on a Mac laptop (old Yosemite OS) executes without error. Has anyone put together a work-around, for instance two one way channels?
Ed H (edhyman@icloud.com)

EdHyman commented Apr 25, 2017

The duplexchannelfactory was working as intended on a previous version of Xamarin Studio. I upgrade to a new version of OS (from Yosemite to El Capitan) and install Xamarin updates as well, then I receive this nonimplementedexception error. My previously compiled code running on a Mac laptop (old Yosemite OS) executes without error. Has anyone put together a work-around, for instance two one way channels?
Ed H (edhyman@icloud.com)

@ivanbottero

This comment has been minimized.

Show comment
Hide comment
@ivanbottero

ivanbottero May 3, 2017

Is there any news for TCP Duplex channel?

ivanbottero commented May 3, 2017

Is there any news for TCP Duplex channel?

@marek-safar

This comment has been minimized.

Show comment
Hide comment
@marek-safar

marek-safar May 3, 2017

No update for now but I'll see if we can schedule it anytime soon

marek-safar commented May 3, 2017

No update for now but I'll see if we can schedule it anytime soon

@ArgusMagnus

This comment has been minimized.

Show comment
Hide comment
@ArgusMagnus

ArgusMagnus Jul 6, 2017

I would highly appreciate tcp duplex channel support

ArgusMagnus commented Jul 6, 2017

I would highly appreciate tcp duplex channel support

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Jul 29, 2017

@marek-safar Please schedule it soon.

huangjinshe commented Jul 29, 2017

@marek-safar Please schedule it soon.

@huangjinshe huangjinshe reopened this Jul 29, 2017

@zhenlan zhenlan added the Xamarin label Jul 29, 2017

@ArgusMagnus

This comment has been minimized.

Show comment
Hide comment
@ArgusMagnus

ArgusMagnus Aug 15, 2017

Any progress on this?

ArgusMagnus commented Aug 15, 2017

Any progress on this?

@marek-safar

This comment has been minimized.

Show comment
Hide comment
@marek-safar

marek-safar Aug 15, 2017

This is large effort for us with many implications to resolve. Unfortunately, I don't see us leveraging dotnet WCF code anytime soon.

marek-safar commented Aug 15, 2017

This is large effort for us with many implications to resolve. Unfortunately, I don't see us leveraging dotnet WCF code anytime soon.

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Aug 15, 2017

@marek-safar I thought you guys will do that few months ago. You sounds like you guys giving up that now.....

huangjinshe commented Aug 15, 2017

@marek-safar I thought you guys will do that few months ago. You sounds like you guys giving up that now.....

@kartalbas

This comment has been minimized.

Show comment
Hide comment
@kartalbas

kartalbas Aug 31, 2017

so we have to wait until NET Core replaces mono?

kartalbas commented Aug 31, 2017

so we have to wait until NET Core replaces mono?

@ArgusMagnus

This comment has been minimized.

Show comment
Hide comment
@ArgusMagnus

ArgusMagnus Sep 21, 2017

@marek-safar Is it save to assume, that tcp duplex support is not coming to Xamarin.Android by the end of this year?
Is there a realistic chance that this will happen in the future at all?

ArgusMagnus commented Sep 21, 2017

@marek-safar Is it save to assume, that tcp duplex support is not coming to Xamarin.Android by the end of this year?
Is there a realistic chance that this will happen in the future at all?

@marek-safar

This comment has been minimized.

Show comment
Hide comment
@marek-safar

marek-safar Sep 21, 2017

@ArgusMagnus yes, that's the safe to assume but it's still in the plan for the future

marek-safar commented Sep 21, 2017

@ArgusMagnus yes, that's the safe to assume but it's still in the plan for the future

@zhenlan

This comment has been minimized.

Show comment
Hide comment
@zhenlan

zhenlan Sep 26, 2017

Member

@marek-safar what's the repo for Xamarin/mono so we can move this issue there for better tracking since this repo is only for WCF on .NET Core?

Member

zhenlan commented Sep 26, 2017

@marek-safar what's the repo for Xamarin/mono so we can move this issue there for better tracking since this repo is only for WCF on .NET Core?

@marek-safar

This comment has been minimized.

Show comment
Hide comment
@marek-safar

marek-safar commented Sep 27, 2017

@zhenlan best to report the issue at https://bugzilla.xamarin.com/

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Sep 27, 2017

@marek-safar , @zhenlan Don't need to do that, because I already did that almost 1 year or maybe 1.5 year ago......Turns out there is no one responsible for that.

huangjinshe commented Sep 27, 2017

@marek-safar , @zhenlan Don't need to do that, because I already did that almost 1 year or maybe 1.5 year ago......Turns out there is no one responsible for that.

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Dec 6, 2017

@marek-safar , Hi, Is there any news for this? It take too much time. If UWP dead right now, we need to use Android or iOS version of WCF feature more soon.

huangjinshe commented Dec 6, 2017

@marek-safar , Hi, Is there any news for this? It take too much time. If UWP dead right now, we need to use Android or iOS version of WCF feature more soon.

@marek-safar

This comment has been minimized.

Show comment
Hide comment
@marek-safar

marek-safar Dec 15, 2017

@huangjinshe no update at this point

marek-safar commented Dec 15, 2017

@huangjinshe no update at this point

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Feb 10, 2018

Is there any good news.....I almost lose my mind......

huangjinshe commented Feb 10, 2018

Is there any good news.....I almost lose my mind......

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Jun 15, 2018

Is there any news in this year? Microsoft is trying to support more and more, they want to be a service, the reason we use WCF because we want some advanced feature such like TCD Duplex Channel or like certification encryption, why stop updating it after finish some simple feature? , If we just use simple HTTP connection with json, then what's the point of use WCF? I hope WCF team bring these advanced feature to IOS and Android, let us use, not only stop after bring it after dead Windows phone !

huangjinshe commented Jun 15, 2018

Is there any news in this year? Microsoft is trying to support more and more, they want to be a service, the reason we use WCF because we want some advanced feature such like TCD Duplex Channel or like certification encryption, why stop updating it after finish some simple feature? , If we just use simple HTTP connection with json, then what's the point of use WCF? I hope WCF team bring these advanced feature to IOS and Android, let us use, not only stop after bring it after dead Windows phone !

@terrajobst

This comment has been minimized.

Show comment
Hide comment
@terrajobst

terrajobst Jun 15, 2018

Member

@huangjinshe

At Build we've announced our plans for .NET Core 3.0 which is focused on bringing the client tech (WinForms/WPF) to .NET Core (but it will remain Windows-only). Based on customer feedback we've prioritized this work over porting more server technologies. That doesn't mean those aren't gonna happen but it does mean they are currently taking the backseat. Please keep the feedback coming so we can prioritize it accordingly moving forward!

Member

terrajobst commented Jun 15, 2018

@huangjinshe

At Build we've announced our plans for .NET Core 3.0 which is focused on bringing the client tech (WinForms/WPF) to .NET Core (but it will remain Windows-only). Based on customer feedback we've prioritized this work over porting more server technologies. That doesn't mean those aren't gonna happen but it does mean they are currently taking the backseat. Please keep the feedback coming so we can prioritize it accordingly moving forward!

@huangjinshe

This comment has been minimized.

Show comment
Hide comment
@huangjinshe

huangjinshe Jun 15, 2018

@terrajobst

Thank you, that's a really good news, But still only for Windows, currently we need really need much more support for Android and iOS. I just hope you guys just use .NET Core replace Xamarin.iOS and Xamarin.Android (currently those based on mono), because .NET core growing speed too much faster than mono, mono has too much limits, No advanced feature.

Maybe that's much more better when use Xamarin/.NET Core, it should be better than Xamarin/mono.

huangjinshe commented Jun 15, 2018

@terrajobst

Thank you, that's a really good news, But still only for Windows, currently we need really need much more support for Android and iOS. I just hope you guys just use .NET Core replace Xamarin.iOS and Xamarin.Android (currently those based on mono), because .NET core growing speed too much faster than mono, mono has too much limits, No advanced feature.

Maybe that's much more better when use Xamarin/.NET Core, it should be better than Xamarin/mono.

@terrajobst

This comment has been minimized.

Show comment
Hide comment
@terrajobst

terrajobst Jun 15, 2018

Member

.NET Core will remain a cross-platform and we're working with the Mono/Xamarin teams to share more code to get a a more converged library stack. .NET has always been about also giving you access to native OS features and we'll continue to do so. However, I do agree with you that we also need to push the envelope how far you can go with cross-platform application and UI definition, but that's a next step.

Member

terrajobst commented Jun 15, 2018

.NET Core will remain a cross-platform and we're working with the Mono/Xamarin teams to share more code to get a a more converged library stack. .NET has always been about also giving you access to native OS features and we'll continue to do so. However, I do agree with you that we also need to push the envelope how far you can go with cross-platform application and UI definition, but that's a next step.

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