New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Core 1.1.0 #305
Comments
Is that blog post supposed to be live? There's nothing on the .NET blog about 1.1.0. EDIT: Since posting this comment the article has been posted. Thanks! |
I think it should be the latest stable .NET Core version installed. |
Since the release notes say nothing about it, I'm assuming this preview does not remove the OpenSSL dependency in macOS? |
Chiming in on the |
@kamcma The OpenSSL dependency is reduced, but not removed. There's still quite a lot of work left, crypto's big 😄. https://github.com/dotnet/corefx/issues/9394 is the work/tracking issue. |
The packages referenced in the release notes for Ubuntu downloads do not exist, at least in the xenial repository. Also the 16.10 section says
|
@vaindil Added package refs to the install page. Let me know if that's the right idea. Also fixed |
@leecow Helpful, definitely, but not quite the problem. Instructions say to run this command:
but that package does not exist so the command fails. I believe the correct command should be:
Installing that package resolved the error I was getting about 1.1.0 not being installed. |
@vaindil Gotcha ... will fix that. |
|
Apologies for that @tanaka-takayoshi ! Fedora 24 support did not make it into the Preview release but I have confirmed that it's in for the final release. From the core-setup repo:
|
@leecow Thanks for the confirmation. I'm looking forward to the final release. |
dotnet new produces the correct project.json, but creating a new ASP.NET Core (Core) from VS 2015 will generate the older 1.0 project.json; is that expected? |
Windows 10 Edit: Yeah IIS doesn't work now even when downgrading all packages to stable release Second Edit: For anyone else that does get this problem, I managed to fix it by going into my bin/debug/netcoreapp1.0 folder and deleting all files in there then deleting project.json and project.lock.json and copying in a fresh asp.net core template, project.json and project.lock.json and after restoring packages I no longer got this error. |
@Ponant - yes, that's expected until the upcoming Dev15 RC and .NET Core / ASP.NET Core update. |
@M-Curtis Sounds like there was an issue with the modified project.json file. If you can share the problematic project.json file with us we can take a look and see what might be amiss. |
Hi, OpenSUSE 42.1 link on ".NET Core 1.1 Preview 1 and .NET Core SDK 1.0 Preview 2.1" (core/release-notes/preview-download.md) page is wrong. Link refers to the version without sdk. Can you fix it? |
Feedback was requested on the "dotnet new" design choice for it using Preview 1 instead of 1.0. I think that perhaps you should add a command line option parameter for a version number if the default is not the choice you want. So "dotnet new" would give you the default most recent installed version, but if I explicitly want 1.0, then I can type "dotnet new --version 1.0" . As I write this, it seems roughly similar to dnvm. Maybe we could have that back in some form? |
Thanks for letting us know about the bad link @Thunderchie-f. Download page has been updated. |
@rhires, thanks for the feedback. This is inline with discussions we having to Include some gesture to choose what version to target with dotnet new. Will add your vote! /cc @richlander |
@tanaka-takayoshi Try this for bleeding edge Fedora 24 binaries. |
@Petermarcu Thanks, but it doesn't include dotnet SDK, only runtime. So I could try few things. |
@tanaka-takayoshi , yeah, its definitely bleeding edge. You can use the existing SDK's on other runtimes. You can likely replace the contents of dotnet/shared/Microsoft.NETCore.App/1.0.1 with the contents from that tar.gz and it should work. |
Using the
UPDATE: The official 1.1.0 packages are working without problems of course. |
Is there a new version of the IIS Hosting module for .NET Core 1.1 RTM? |
@VahidN There is a new version of the ASP.NET Core Module for IIS for .NET Core 1.1 RTM. The download link is listed on https://www.microsoft.com/net/download/core |
I was getting the same issue as @BalassaMarton when using the upgrade via NuGet functionality in Visual Studio. Had to rollback the upgrade. |
Closing this one. Please move to the latest release: #532. |
I have an app using .net core 1.1.0 and having a hell of a time getting the polyfills.ts file to be picked up by webpack or any part of the compile system. The application is required to work with IE11 and is currently hindered because of this issue. I would say that my biggest issue, is where to place the file polyfills.ts in the project so that it will be compiled and bundled with the rest of the application? Server setup is Windows server 2012 with IIS 8.0, Development machine is Windows 10 with IIS 8.5. |
[Renaming and updating this issue to the final 1.1 release]
You can read about .NET Core 1.1 in the blog post: Announcing .NET Core 1.1 and download the update from the .NET Core install page now.
Please report any issues you find with .NET Core 1.1 in this repo, either responding to this issue or creating a new issue.
Please include the following information plus any other info that you think is relevant:
OS version
Repro steps
Repro code (if you can share it / is relevant)
Error messages
Whether this worked before
Method of installing .NET Core
The text was updated successfully, but these errors were encountered: