RCTycooner

It's running on a hosted agent. Currently a vs2017-win2016. Rerunning on the same agent gives the same error, but happened after another message (e.g. in the "getting the details of...

Hi, just tried with v2.29.4. same error, but on a different build. See the attached log. [log2.txt](https://github.com/rfennell/AzurePipelines/files/4351027/log2.txt) I'm unable to try it on a private agent as we don't have...

Thanks, haven't looked at the code yet. But perhaps a retry mechanisme is in order? (I'm in Belgium btw, GMT+1) It sure could be that they throttle it based on...

Hi, thanks for the update. I've actually wrote my own code to get the release notes based on what you were doing. So far it seems to work fine. Not...

I was able to work around this issue by marking the DateTime-properies with Exclude, and adding a string-property that wraps the original DateTime prop. Something like: > [Include()] public String...

I can confirm this works when marking the Kind & Ticks properties with Include as you've suggested. For now, this has been the only type I've seen this error on....

Hmm, To test it this time, I've written a small program. But now the previous workaround (where you mark the Kind and Ticks properties to be included) no longer works!...

The ideal situation is ofcourse that basic types such as a DateTime work out of the box. So I would add a special condition for DateTimes.

@clement911 same issue here... going to attempt to manually squash my migrations now.

@clement911 what's the status of issue for build pipelines? We're using hosted agents that should be getting the latest versions of everything, but still has this issue. Will update my...