"Faulted" WCF SOAP Client - Suspected VS Update
On Monday I had a big mystery bug. I was suddenly getting a "client faulted" exception in a WCF client that I had previously been testing OK on:
My boss called me over because it was running on his machine, so I double checked everything my side and found I had to update all my
My boss called me over because it was running on his machine, so I double checked everything my side and found I had to update all my
System.ServiceModel.* package refs from 4.4.* to 4.10.*, which immediately resolved my faulted client. My big question is how was my code working before the appearance of the faulted client? It seems I may have run the latest VS update earlier that day. How else would my API's WCF dependencies suddenly be broken?