-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
CoreCLR Loading Fails on 1.0.2-prerelease #5079
Comments
I assume you are talking about the Microsoft.DotNet.CoreCLR package on the dotnet-coreclr feed? The packages on that feed are very old and out are no longer updated. You should be using packages from the dotnet-core feed. You'll find newer versions of the 1.0.1 package you were using there. Are you seeing the same issue on 1.0.1-rc2 or 1.0.1-rc3 builds? @weshaggard Is it possible to un-list all the packages on that feed so folks don't get confused? I know we already say the feed is deprecated, but if we can unlist the packages it will make it even harder for folks to pick up these old packages. |
@ellismg And you would be correct. The only reason I used that feed at all was because I needed PDBs for |
Sound good. I will bug folks to see what the plan on symbols is, we should have a better story than what you had to deal with. |
@ellismg even if we were to unlist the package that wouldn't stop anyone from directly querying for that package at it would still work. unlisting only removes it from the full package query list but people can still get it directly if they reference the specific version. |
I was trying to get my Core GUI app (private repo) to run, and it could not load CoreCLR. (See #5076 for details.) However, if I remove my SxS setup (see #5075 for more details on that),
ICLRRuntimeHost2::Start()
still fails. The only way I can successfully load CoreCLR is to use version1.0.1-beta-23225
. I have not been able to get version1.0.2-prerelase
to load successfully at all. Does anyone else have any problems with this version of CoreCLR?The text was updated successfully, but these errors were encountered: