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
Add support for .NET Core 2.2 #62
Comments
I just tried it with both samples from this repo, and with another solution created from scratch that contains a .netcore project, along with a global.json file that points to '2.2.102'. And I just noticed you said '2.2.201'. There isn't a '201' yet. Maybe that's the problem? |
Ahh my bad, typo in the message. I meant '2.2.102' and double-checked that's indeed what we were trying. I tried now in the Migrator.EF6 sample projects and simply adding the following global.json file under 'Solution Items' causes the problem to happen:
Once that gets changed to '2.1.403' the command line tool works fine again, so it seems like even running a previous-version project in the 2.2 runtime causes the issue to surface. |
I'm sorry I still can't reproduce it. I tried putting the exact global.json above in this repo's root folder. It still worked. Maybe it's related to sdk 1.0. I believe that's still necessary for Migrator.EF6 to run. I'm not sure. Did you uninstall some version? What is the output of For comparison, this is mine:
|
I'm closing this, please reopen if you still have issues. |
Hi @mrahhal, sorry for checking up on this for so long, we had to abandon the .NET Core 2.2 upgrade initiative and are just revisiting it now. We tried matching your setup with the 1.1.7 versions and testing on 2.2.102, we're getting the same problem unfortunately =(
Which version of .NET Framework are you running on by chance? |
Hello @marchy I myself have 4.7.2. But in my team of 6, each probably have different versions. The only requirement they had to install were .net core sdk latest version (usually) + version 1.1.x (here). This is again my setup:
Can you try installing 1.1.14 sdk? |
Hi Mohammad, I tried matching your versions, both with [1.1.7 + 2.2.102] earlier as well as [1.1.14 + 2.2.401] (and some combination of both).
results in:
with 'global.json' being:
Is there any way to dive deeper / step through / debug the project to see what's happening in the tool? |
UPDATE: Okay this is extremely strange. I ran a debug session against the project (with setting the execution path to be the BasicConsoleApp sample project that references the tool) and not only did the debug session work, but now the command line is working as well – for both the sample projects and others! Could it be that the way the tools get registered with the dotnet CLI tool reference was somehow cached using an older version of the tool? Not sure how to check caches of this, my |
Wow.. Yeah to start with, debugging tools is seriously inconvenient, I haven't been able to do that properly in the past, not sure if anything changed.
I really doubt that if you've ever updated the version of the tool. NuGet will definitely obtain the newest version.
You'll need to check
Yeah it won't be there since this is not a global tool. So this is weird, but so, once you debugged your sample it started working? Did you repro this on other machines? (Though, I think you told me this problem only occurs on 1 machine?) |
This was happening on two additional machines previously, though did not try it on the other one this time around. We've actually got the 2.2 upgrade / 3.0 assessment scheduled for the end of September so I'll check against the one other machine to repro, and I'll check both what files are there beforehand and what changes if the same debugging trick resolves it. The path above wasn't a typo, we took it from this article (https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools) but I guess that must not apply for NuGet packages. I do see the Migrator.EF6 tool in the I'll update with any new findings when we do our full upgrade at the end of next month. Thanks again for your help and promptness on everything Mohammad! |
No worries! Glad you were able to get it to work, please do keep me updated. |
Switching over to .NET Core 2.2 makes the
dotnet ef6
command error with:Version for package 'Migrator.EF6.Tools' could not be resolved.
This can be tested by pointing the global.json file in a solution containing a .NET Core project from '2.1.403' to '2.2.201'.
Note that running the Console app in the Migrator.EF6 runs fine - so something is incompatible with the integration into the dot net tools/toolchain.
UPDATE: The .NET Core version tried above is actually '2.2.102' – typo in the message above.
The text was updated successfully, but these errors were encountered: