Skip to content
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

Closed
wjk opened this issue Feb 6, 2016 · 4 comments
Closed

CoreCLR Loading Fails on 1.0.2-prerelease #5079

wjk opened this issue Feb 6, 2016 · 4 comments

Comments

@wjk
Copy link
Contributor

wjk commented Feb 6, 2016

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 version 1.0.1-beta-23225. I have not been able to get version 1.0.2-prerelase to load successfully at all. Does anyone else have any problems with this version of CoreCLR?

@ellismg
Copy link
Contributor

ellismg commented Feb 7, 2016

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.

@wjk
Copy link
Contributor Author

wjk commented Feb 7, 2016

@ellismg And you would be correct. The only reason I used that feed at all was because I needed PDBs for coreclr.dll to help debug my problem, and that was the only place I could find them. However, I have since solved the original problem, and ceased usage of these deprecated packages. Is it OK to close this issue?

@ellismg
Copy link
Contributor

ellismg commented Feb 7, 2016

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.

@wjk wjk closed this as completed Feb 7, 2016
@weshaggard
Copy link
Member

@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.

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 30, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants