C# WPF UI Tutorials 40 Synchronize Server & Client Settings

Part of a series of tutorials on creating WPF applications in C#

It's getting close to real - we link up the settings page on the client application so that the information is the real user profile information stored on the server.

[Trust_Me_Im_An_Engineer]

If you are getting Server response error (ServerResponse = null) it is because of the ApiResponse and ApiResponse<T> class design. Took me a while to figure out. The problem is they don’t serialize the way they should. If you want to keep the design presented in the video, you will most likely need to include attribute on public object Response property. This was a nasty hidden bug. Hope this saves you several hours worth of debugging. Great video as always Luke!

[loam]

I really appreciate your tutorials not only for being usefull and informative, but also for your pure English, which is pretty rare for programming tutorials out here on Youtube :) I'm not native speaker myself, but still tho can't bear hearing some bad English, I work hard on my own pronunciation and feel that I kinda can spoil myself listening to bad English :)

[squirekev]

1:01 Found the bug in the code. Good tutorial, well laid out format. Nice work.

[vinuhosanagar]

Thanks much. It's getting awesome to see a fully fledged application develped from scratch :)

[助理教授克莱登大学]

Thank you, Teacher. Your Lessions are the best contents I can find

[arnaudp]

Hello,

Thanks a lot again, you really made a complete and working project and it's incredible to find it step by step on youtube. You're the best teacher ! :)
I had an issue with the JSON Serializer, it gives me a name conflict error.
In fact it was coming from the "new" keyword in the "Response" property of ApiResponse<T> class. It is in conflict with "Response" property in ApiResponse.
Instead of doing like you shown, I made an ApiResponse<T> without inheritance with the "Response" property in type T.
Then I made my ApiResponse like that :
public class ApiResponse : ApiResponse<object> { }
It keeps the original behavior, with a no typed response, it give an "object" type (or null).
Has there is no "new" in the property it works on my side. I don't know if the error comes only on my side (maybe I missed something).
I hope it can helps somebody in the future. :)