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! While you're at it, check out some resources Treehouse students have shared here.
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 trialHenrik Christensen
Python Web Development Techdegree Student 38,322 Points.Net core
Hi,
I finished setting up for .Net core and tried to create a project, but I find the creation time to be very long :-/
The examples I've seen the user got his/hers project created almost instantly when a line or two in the console.
Now I'm wondering if it normal to wait like 200,0000ms for a dotnet project to get created?
Here is what I see in the console/powershell:
Welcome to .NET Core!
Learn more about .NET Core @ https://aka.ms/dotnet-docs. Use dotnet --help to see available commands or go to https://ak a.ms/dotnet-cli-docs.
Telemetry
The .NET Core tools collect usage data in order to improve your experience. The data is anonymous and does not include c ommand-line arguments. The data is collected by Microsoft and shared with the community. You can opt out of telemetry by setting a DOTNET_CLI_TELEMETRY_OPTOUT environment variable to 1 using your favorite shel l. You can read more about .NET Core tools telemetry @ https://aka.ms/dotnet-cli-telemetry.
Configuring...
A command is running to initially populate your local package cache, to improve restore speed and enable offline access. This command will take up to a minute to complete and will only happen once. Decompressing 100% 18653 ms Expanding 100% 660525 ms Failed to create prime the NuGet cache. restore failed with: 1 Content generation time: 205,1653 ms The template "Console Application" created successfully.
dotnet restore takes about the same amount of time and then just fail because System.Runtime.dll is being used by another process
2 Answers
James Churchill
Treehouse TeacherHenrik,
Yes, that should have installed the latest version.
Restoring all of the NuGet packages that you need to develop a .NET Core app will take a bit the first time that you do it. Once you have your local NuGet cache populated, creating subsequent projects will go much faster.
The System.Runtime.dll is being used by another process
error sounds like you might have two restores running at the same time. Try restarting Windows and doing a dotnet restore
from within the root of your project.
Thanks ~James
James Churchill
Treehouse TeacherHenrik,
1) What platform are you using? Windows, macOS, or Linux?
2) What version of the .NET Core SDK did you have installed?
3) Is this the first time that you've installed .NET Core? Or did you install any earlier versions?
Thanks ~James
Henrik Christensen
Python Web Development Techdegree Student 38,322 PointsHi James :-)
1) I'm using Windows.
2) I followed the instructions (including the video) from https://www.microsoft.com/net/core#windowscmd (I guess this is the newest version?)
3) Yes, this is the first time I installed it.
Henrik Christensen
Python Web Development Techdegree Student 38,322 PointsHenrik Christensen
Python Web Development Techdegree Student 38,322 PointsSeems to be working now, thank you very much James :-)
James Churchill
Treehouse TeacherJames Churchill
Treehouse TeacherGlad to hear it and you're welcome!
James