Home → Knowledge Base →

.NET Core RTM Support

Showing page 2 out of 2. View the first page

1. Support Staff 31 Posted by Feodor Fitsner on Jun 28, 2016 @ 05:22 PM

   

   @michiel - could you please give me an exact command? I've tried dotnet --version and it worked fast.

   @jpapp - what are those packages and what command can be used to pre-populate the cache?

   • Edit

2. 32 Posted by michiel on Jun 28, 2016 @ 05:27 PM

   

   You can do "dotnet new" and it will show the uncompressing of files.

   • Edit

3. 33 Posted by jpapp on Jun 28, 2016 @ 05:28 PM

   

   Looks like they fixed it from loading the local cache when calling dotnet --version https://github.com/dotnet/cli/issues/3580

   Calling dotnet restore on a project for the first time will trigger the local package cache. Maybe do dotnet new and then call dotnet restore in the same directory to make sure it does loads the local cache

   • Edit

4. Support Staff 34 Posted by Feodor Fitsner on Jun 28, 2016 @ 05:34 PM

   

   OK, I see - will take a look. Thanks for fast responses.

   • Edit

5. 35 Posted by bniemyjski on Jun 28, 2016 @ 06:42 PM

   

   I'm also seeing this.. It's adding minutes to each build.

   • Edit

6. Support Staff 36 Posted by Feodor Fitsner on Jun 29, 2016 @ 02:20 AM

   

   OK, deployed update with pre-cached dotnet tool.

   • Edit

7. 37 Posted by bniemyjski on Sep 14, 2016 @ 12:10 AM

   

   They just released version 1.0.1 (https://www.microsoft.com/net/core#windows) of .NET Core. It contains new sdk / runtime.

   • Edit

8. Support Staff 38 Posted by Feodor Fitsner on Sep 14, 2016 @ 12:47 AM

   

   Perfect timing, thanks for the hint! Will deploy it this week.

   • Edit

9. 39 Posted by chudinia on Sep 19, 2016 @ 02:02 PM

   

   Hello, not clear if .Net Core 1.0.1 is supported.
   I'm getting the error: "The project is configured to use .NET Core SDK version 1.0.0-preview2-003131 which is not installed or cannot be found under the path C:\Program Files\dotnet...."

   • Edit

10. Support Staff 40 Posted by Feodor Fitsner on Sep 19, 2016 @ 05:08 PM

    

    Image has been updated and .NET Core 1.0.1 is now available.

    • Edit

11. 41 Posted by michiel on Sep 19, 2016 @ 08:39 PM

    

    Looks like it is installed, but the old dotnet is still on the PATH.

    When I execute dotnet --version, this is the result:
    dotnet --version
    1.0.0-preview2-003121

    this should be: 1.0.0-preview2-003131

    • Edit

12. Support Staff 42 Posted by Feodor Fitsner on Sep 20, 2016 @ 05:10 PM

    

    Should be OK now. Give it another try please.

    • Edit

13. 43 Posted by michiel on Sep 20, 2016 @ 06:23 PM

    

    Yes, everything ok now. Thanks!

    • Edit

14. 44 Posted by bniemyjski on Oct 20, 2016 @ 05:36 PM

    

    https://blogs.msdn.microsoft.com/dotnet/2016/10/20/announcing-the-october-2016-update-for-net-core-1-0/

    Looks like a new update

    • Edit

15. Support Staff 45 Posted by Feodor Fitsner on Oct 20, 2016 @ 05:38 PM

    

    From that page:

    We are releasing an update today which addresses an issue installing on a clean macOS Sierra system. The change is limited to the macOS installer. There are no changes in the runtime or tools; .NET Core 1.0.1 remains the latest release for Windows and Linux.

    Looks like we're good?

    • Edit

16. 46 Posted by bniemyjski on Oct 20, 2016 @ 06:28 PM

    

    Yeah I think so, just saw it and posted on here, looks like fixes are incoming for windows next month.

    • Edit

17. Ilya Finkelshteyn closed this discussion on Aug 25, 2018 @ 02:09 AM.