Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.Start your free trial
Unable to start program...not a valid working directory.
I have cloned the Repo for ASP.NET MVC - Fitness Frog. When I try to run the program I get an error "Unable to start program" stating that the "\Treehouse.FitnessFrog\bin\Treehouse.FitnessFrog.dll" doesn't exist. I don't have a "bin" directory. What am I doing wrong here?
Robert Stefanic35,170 Points
Can you post your full current working directory path?
If you've just cloned the directory, and opened the solution, then you may need to build the project first. The complaint is that the executable can't be found. Usually, if you're building a project using Visual Studio (I'm assuming you're opening the project in VS), the bin directory is created and the executable is stored there.
If you happen to know where the program sits (i.e. not in your \bin folder), then you will need to say where Treehouse.FitnessFrog.dll lives on your machine.
I didn't notice because the Output window was closing so quickly, but when I tried to build the project, it threw this error: C:\Users\Jason.Finley\Source\Repos\aspnet-fitness-frog\src\Treehouse.FitnessFrog\Treehouse.FitnessFrog.csproj(178,5): error : This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\Microsoft.Net.Compilers.1.0.0\build\Microsoft.Net.Compilers.props.
I've got my Package Restore options checked. I'm not sure where to execute these things, though: For .NET Core projects, run dotnet restore or dotnet build (which automatically runs restore). On the command line, run nuget restore (except for projects created with dotnet, in which case use dotnet restore).
That worked! I'm back on track. Thank you.