PMC Tools: Error when project opened from a file share

[rowanmiller]

Moved from dotnet/EntityFramework.Docs#346
cc @klipi

I'm following the tutorial here: https://docs.microsoft.com/en-us/ef/core/get-started/aspnetcore/new-db up to the point where I need to run the first migration:

PM> Add-Migration MyFirstMigration
Unable to resolve startup project 'Microsoft.PowerShell.Core\FileSystem::\\mac\home\documents\visual studio 2017\Projects\EFGetStarted.AspNetCore.NewDb\EFGetStarted.AspNetCore.NewDb\EFGetStarted.AspNetCore.NewDb.csproj'.
To undo this action, use Remove-Migration.
Add-Migration : Exception calling "AddFromFile" with "1" argument(s): "'basePath' cannot be an empty string ("") or start with the null character.
Parameter name: basePath"
At line:1 char:1
+ Add-Migration MyFirstMigration
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Add-Migration], MethodInvocationException
    + FullyQualifiedErrorId : ArgumentException,Add-Migration

I'm running Visual Studio 2017 RC3 under a Win10 VM in Parallels, so that might be the cause of some issues. However I have no idea on how to start to debug this, as I'm quite new to the .NET Core world and Entity Framework.

[oniskanen]

Copying this over from the documentation side

PM> $DTE.Solution.SolutionBuild.StartupProjects
EFGetStarted.AspNetCore.NewDb\EFGetStarted.AspNetCore.NewDb.csproj
PM> $DTE.Solution.Properties.Item('Path').Value
\\mac\home\Documents\Visual Studio 2017\Projects\EFGetStarted.AspNetCore.NewDb\EFGetStarted.AspNetCore.NewDb.sln

I'll try to redo the tutorial under C:\ and see what happens. Not sure if anything else is breaking, been away from Windows and VS for a couple of years. A quick HelloWorld-type web app works nicely and I was even able to publish it to Azure without a hitch. Trying to add the database layer (and EF along it) is the first I'm running into trouble.

[oniskanen]

@bricelam, No issue running under C:\

[bricelam]

Groovy. I suspect this is the root of our problems:

PS> Split-Path \\mac\home -IsAbsolute
False

[ojorma]

im having a similar issue except that im not in a file share. I just got vs2017 and i get this error when i try to add-migration

`add-migration : Exception calling "AddFromFile" with "1" argument(s): "'basePath' cannot be an empty string ("") or start with the null character.
Parameter name: basePath"
At line:1 char:1

• add-migration init

•   + CategoryInfo          : NotSpecified: (:) [Add-Migration], MethodInvocationException
    + FullyQualifiedErrorId : ArgumentException,Add-Migration
  

`

[dotnetnoobie]

I have the same error message as @ojorma
Using VS2017 ASPNET CORE & EF CORE 1.1 versions

I am using a class library for the DataContext Objects

I only get this error with the DataContext which also is the context object which is used for ApplicationDbContext

When I try it with other DataContext objects which are for small stand alone databases I don't get the error.

I also noticed that when I tried to run the web app and use the build in apply migrations button that EF-Core could not login to the database and was trying to use my Microsoft Login for the Windows/Microsoft Account, even when I have set the connection string in the app settings to use a trusted connection.

The message asked me to create the migration manually for the ApplicationDbContext
I created it manually, no error, I updated the database with no error

Once I had done this manually via the nuget command window in VS2017

I was then able to create the same migration which I got the above error for
but this time I got no error and was able to update the database and everything worked as it normally does with no errors

[bricelam]

@ojorma @dotnetnoobie Are you using Docker? You may be hitting #7439. (Workaround: Pass your web app as -StartupProject)

[ojorma]

@bricelam I am using a console app. I first tried it with a class library but thesame thing so i tried it again in a console app. I just got vs2017 and testing the basic stuff out. I got burnt with version 1.0 cause of entityframework core.

[ojorma]

@bricelam @rowanmiller @dotnetnoobie
this is what my sample project looks like

[dotnetnoobie]

@bricelam I am not using docker
Just a standard projects

AspNetCore 1.1 app which references Class Library

I have the DataContext objects on a separate project which is a
.NetCore App 1.1 (Class Library)

I set the "Default Project" in the "Package Manager Console" from the dropdown
but I did not use this "-StartupProject" option in the commands

[dotnetnoobie]

@bricelam I also had problems with the class library originally
what I did was create a test website with individual auth set in the options
I then opened the .csproj file and copied the correct EF Core related references for the nuget packages
and added them to the class library .csproj file

This seemed to solve the issues I has of not actually having all the correct nuget packages referenced to get everything working

@rowanmiller @dotnetnoobie