Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
no not using MVVM for this assignment, just following how my prof suggested to do things, we have a library that has a list of callback interfaces that calls updategui, and even if I did use MVVM the problem is that the callback from the service isn't firing for whatever weird reason, it's just odd that having the List like that would cause that issue
How do you even come up with shit like this?
I found such a treasure today in the production code.
WCF doesn't like me adding to lists...
I have to make an uno game that supports multiplayer with WCF for school...
I have a player class that has a list of card classes.
I have a function called dealHand, it adds Cards to the hand list...
I also have a callback function for updating my wpf gui...
For whatever reason if when the gui calls dealhand and I try to use myList.add(new Card()) then the updategui function in my wpf client doesn't fire...
But if I take a seperate method called makeHand which returns a list of cards, and just do myList = makeHand() then that works fine...
Never been so baffled/cursed so much at code before... Is there something about Lists that WCF doesn't like? Seriously... was weird...
Hopefully that was somewhat coherent...
rant
wcf
c#
lists
weirdshit