-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VS2017 conversion show big error message #563
Comments
same issue here... are we missing some core dlls? |
Hi, thanks for posting. It looks like a dependency upgrade in a recent release broke support for VS2017 - I can reproduce this issue on VisualStudio.15.Release/15.9.21+28307.1064 For now, you'll need to either use VS2019, or uninstall the extension, close all visual studio windows, then install version 8.01 from here If there's any reason you can't use VS2019 I'd be interested to know why (is it a licensing thing?) since I'll be considering dropping support for VS2017 in 6 months |
Hi, the solution I was trying to use it, is "technically super-outdated" with a big mess of c# and vb projects, old node.js modules and such. Classic entropy death scenario,. Issue is, the solution just doesn't compile/work under vs2019 and "upgrading" is too much of an effort.. |
Makes sense, thanks for the info. I would like to keep VS2017 going as long as possible for the reason you describe, but it's pretty hard to stay compatible while making use of the great new tools available. I've put in a tentative fix, would you mind trying it? There's a CI build artifact you can try here: https://icsharpcode.visualstudio.com/icsharpcode-pipelines/_build/results?buildId=1188&view=results |
it's working now under vs2017.. thx a lot! |
Great thanks for confirming! |
It's working, Thank you :) |
I have installed newest version of converter in VS 2017 Enterprise. If I want convert VB.NET code to C# I get this error message:
Output window:
Converting XXXXX.aspx.vb...
Phase 1 of 2:
That is all. Can you help me?
The text was updated successfully, but these errors were encountered: