+ CategoryInfo : ObjectNotFound: (C:\Users\\tools\init.ps1:String), CommandNotFoundException rgs+=$_} & 'C:\Users\\source\repos\ConsoleApp1\packages\. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. & : The term 'C:\Users\\source\repos\ConsoleApp1\packages\EntityFramework.6.4.4\tools\init.ps1' is not recognized as the name of a cmdlet, function, script file, or When VS loads that project during a fresh launch, I get roughly the same issue. I then thought to try EF under a test console project in. rgs+=$_} & 'C:\Users\\.nuget\packages\microsoft.entityfr. Check the spelling of the name, or ifĪ path was included, verify that the path is correct and try again. Recognized as the name of a cmdlet, function, script file, or operable program. & : The term 'C:\Users\\.nuget\packages\\3.1.8\tools\init.ps1' is not The PMC reported this : Executing script file 'C:\Users\\.nuget\packages\\3.1.8\tools\init.ps1'. I closed and relaunched VS and that is when I got my first hint of the problem. I first tried installing EFCore and EFCore Tools to an ASP.Net Core 3.1 project and found it odd that Add-Migration command wouldn't auto complete. I have VS Community 2019 installed (16.7.3) and am having trouble getting Entity Framework packages and commands to work properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |