Open InteXX opened 7 years ago
@siegfriedpammer please verify https://github.com/icsharpcode/RefactoringEssentials/commit/15454bea78991cc718b7fe02a0b604f904383057 but I am sure that is the culprit (seems we went overboard with ConfigureAwait in this place)
The error message is a pretty strong hint, that it's related to ConfigureAwait. Oddly enough, I cannot reproduce the issue at all (with and without your change).
@siegfriedpammer — I'm not very familiar with Async/Await, nor Threading in general, but I've seen comments on SO to the effect that Async/Await doesn't use threading. Stephen (Steven?) Cleary is a pretty good authority on Async/Await.
https://msdn.microsoft.com/en-us/library/system.threading.tasks.task.configureawait(v=vs.110).aspx
That's why it might or might not work, depending on your "luck".
@christophwille — Thanks, I stand corrected.
After updating to v4.8 from the original v4.4 that I installed mid-Nov 2016, I'm getting this error when converting:
I'm running VS 2015.3.
Things I've tried:
Oddly, I can successfully make the same
ClipBoard.SetText()
call, referencing the same Framework assemblies, with a quick VB.NET console program of my own.In the end, the only thing that has worked for me has been to revert to the older v4.4 (I'm not finding a download for v4.6, and that version isn't showing up in my system backups). Accordingly, I've turned off auto-update in my VSIX settings.
It's doubtful that this manifests on your system, as you would have encountered it early in your tests. So I'm perplexed. I'm unaware of how to proceed. Please advise.