.NET Core RTM Support

bniemyjski's Avatar

bniemyjski

07 Jun, 2016 04:03 PM

They just announced that .NET Core RTM will be released on the morning of the 27th. This is very important to get our rtm packages out there ASAP after it's released. Would it be possible to schedule a deployment of updated images on the 27th with Nuget 3.5 + .NET CLI Tooling (Preview 2) which will be released on the 27th (not sure about nuget but at least the latest 3.5 beta is out now).

  1. Support Staff 1 Posted by Feodor Fitsner on 07 Jun, 2016 06:08 PM

    Feodor Fitsner's Avatar

    Can you drop a link to that announcement please?

  2. 2 Posted by bniemyjski on 07 Jun, 2016 07:41 PM

    bniemyjski's Avatar
  3. Support Staff 3 Posted by Feodor Fitsner on 07 Jun, 2016 10:30 PM

    Feodor Fitsner's Avatar

    Cool, let's schedule it for deployment on 27th then!

    Would you please remind me on Sunday, the day before that?

  4. 4 Posted by bniemyjski on 07 Jun, 2016 10:31 PM

    bniemyjski's Avatar

    Will do

    Get Outlook for iOS

  5. Support Staff 5 Posted by Feodor Fitsner on 07 Jun, 2016 11:18 PM

    Feodor Fitsner's Avatar
  6. 6 Posted by bniemyjski on 26 Jun, 2016 04:24 PM

    bniemyjski's Avatar

    Looks like some of the bits have leaked ( https://twitter.com/h0x0d ). They require VS Update 3 (the tooling) which I don't think has leaked. But should be out tomorrow morning!

  7. 7 Posted by bniemyjski on 26 Jun, 2016 04:37 PM

    bniemyjski's Avatar

    He tweeted the link to the VS2015 Update 3 RTM web installer / update : https://t.co/Z5MzckvCAR

    I'd uninstall all core rc2 bits (tooling and sdk) before updating.

  8. Support Staff 8 Posted by Feodor Fitsner on 26 Jun, 2016 04:58 PM

    Feodor Fitsner's Avatar

    Nice! Yeah, I think uninstalling RC2 before update makes sense.

  9. 9 Posted by bniemyjski on 27 Jun, 2016 12:07 PM

    bniemyjski's Avatar

    It looks like it will be officially released at 9am PST this morning as that is when the conference starts. Hows the time line look for this?

  10. 10 Posted by bniemyjski on 27 Jun, 2016 03:25 PM

    bniemyjski's Avatar

    https://channel9.msdn.com/Events/Linux/DevNation-2016

    Everyones releasing new rtm versions. Do you have a time today that you're planning on deploying the new tooling + update?

  11. Support Staff 11 Posted by Feodor Fitsner on 27 Jun, 2016 04:01 PM

    Feodor Fitsner's Avatar

    Yeah, will be working on that today.

  12. 12 Posted by bniemyjski on 27 Jun, 2016 04:23 PM

    bniemyjski's Avatar
  13. Support Staff 13 Posted by Feodor Fitsner on 27 Jun, 2016 04:28 PM

    Feodor Fitsner's Avatar

    Cool, what else?

  14. 14 Posted by bniemyjski on 27 Jun, 2016 04:48 PM

    bniemyjski's Avatar

    https://www.microsoft.com/net/download

    looks like 4.6.2 preview is out as well.

  15. 15 Posted by bniemyjski on 27 Jun, 2016 04:49 PM

    bniemyjski's Avatar

    Should just need update 3, and the tooling and sdk + vs integration which can be downloaded from (https://www.microsoft.com/net/core#windows)

  16. Support Staff 16 Posted by Feodor Fitsner on 27 Jun, 2016 04:53 PM

    Feodor Fitsner's Avatar

    Yeah, thought so. Update 3 and then .NET Core RTM.

  17. 17 Posted by bniemyjski on 27 Jun, 2016 08:55 PM

    bniemyjski's Avatar

    Any updates on when the images will be updated?

  18. Support Staff 18 Posted by Feodor Fitsner on 27 Jun, 2016 08:57 PM

    Feodor Fitsner's Avatar

    Working on that. For some reason installing .NET Core 1.0 on top of VS 2015 Update 3 breaks IDE with The XamarinShellPackage package did not load correctly. and other errors when starting it up.

  19. Support Staff 19 Posted by Feodor Fitsner on 27 Jun, 2016 09:02 PM

    Feodor Fitsner's Avatar

    Brilliant, now after installing .NET Core for Visual Studio official MSI Installer from the official page onto my local workstation I'm getting the same errors.

    Did you manage to get it working?

  20. 20 Posted by bniemyjski on 27 Jun, 2016 09:04 PM

    bniemyjski's Avatar

    Yes, try rebooting (I didn't get these errors tho). Make sure the previous sdk and tooling is uninstalled. If you want to pair on this via remote meeting I'd be more than happy to help.

  21. Support Staff 21 Posted by Feodor Fitsner on 27 Jun, 2016 09:06 PM

    Feodor Fitsner's Avatar

    Do you have Xamarin installed?

  22. 22 Posted by bniemyjski on 27 Jun, 2016 09:13 PM

    bniemyjski's Avatar

    I never specifically installed it but it does say I have Xamarin 4.0.1 installed.

  23. Support Staff 23 Posted by Feodor Fitsner on 27 Jun, 2016 09:14 PM

    Feodor Fitsner's Avatar

    ...and VS 2015 Update 3? Update 3 comes with Xamarin 4.1.

  24. 24 Posted by bniemyjski on 27 Jun, 2016 09:15 PM

    bniemyjski's Avatar

    Yes, I uninstalled the two installed .NET core rc programs (tooling and sdk). Then ran the 2015.3.exe which is an upgrader and then ran the tooling and rebooted and everything works.

  25. Support Staff 25 Posted by Feodor Fitsner on 27 Jun, 2016 09:20 PM

    Feodor Fitsner's Avatar

    hold on...looks like I found the issue. There was some component from "DNX" age that was not uninstalled.

  26. Support Staff 26 Posted by Feodor Fitsner on 28 Jun, 2016 02:08 AM

    Feodor Fitsner's Avatar

    OK, it's been deployed! VS 2015 Update 3 with .NET Core 1.0!

  27. 27 Posted by bniemyjski on 28 Jun, 2016 02:09 AM

    bniemyjski's Avatar

    Let me know if there is anything I can do to help

    ____________________

  28. Support Staff 28 Posted by Feodor Fitsner on 28 Jun, 2016 02:11 AM

    Feodor Fitsner's Avatar

    You can help by testing it ;) updated images are online already.

  29. 29 Posted by michiel on 28 Jun, 2016 08:11 AM

    michiel's Avatar

    Thanks for the quick upgrade.

    I found one issue, the first time you use the dotnet command, it does some local initialization and decompressing of files. This can take a minute or 2. And because every build on AppVeyor starts with a clean VM, it does this every build.

    So if you can just run the dotnet command on the base image so it does it's initialization, that would speed up a lot of builds!

  30. 30 Posted by jpapp on 28 Jun, 2016 01:28 PM

    jpapp's Avatar

    Adding c:\users\appveyor\.nuget to your build cache will also stop dotnet from having to run the initial local package cache on every build.

    It still would be nice to have the initial package cache for a few of the standard templates preloaded on the image

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac