published application is missing assembly (missing runtime store associated ...) [2.0.0-preview2-005905]
See original GitHub issueSteps to reproduce
Using latest cli (2.0.0-preview2-005905)
mkdir mvc;cd mvc
dotnet new mvc
dotnet publish
dotnet bin/Debug/netcoreapp2.0/publish/mvc.dll
Expected behavior
Published application should run
Actual behavior
Error: assembly specified in the dependencies manifest was not found probably due to missing runtime store associated with manifest.linux-x64.xml -- package: 'Microsoft.AspNetCore.Antiforgery', version: '2.0.0-preview1-24647', path: 'lib/netstandard1.3/Microsoft.AspNetCore.Antiforgery.dll'
Environment data
$ dotnet --info
.NET Command Line Tools (2.0.0-preview2-005905)
Product Information:
Version: 2.0.0-preview2-005905
Commit SHA-1 hash: 2cc5612fec
Runtime Environment:
OS Name: rhel
OS Version: 7
OS Platform: Linux
RID: rhel.7-x64
Microsoft .NET Core Shared Framework Host
Version : 2.0.0-preview2-002093-00
Build : 1a195046fd92bd73d993d804bea2f4506c2b56f1
Issue Analytics
- State:
- Created 6 years ago
- Comments:47 (35 by maintainers)
Top Results From Across the Web
published application is missing assembly ...
It looks like the one that is in the store has a mis-matched version than the one trying to be used. Error from...
Read more >missing runtime store error on linux with .NET Core 2.0 ...
I think this is because the Runtime download does not generate the new runtime store folder needed when you use the Microsoft.AspNetCore.All ...
Read more >Runtime package store - .NET
Starting with .NET Core 2.0, it's possible to package and deploy apps against a known set of packages that exist in the target...
Read more >Force 'dotnet publish' to publish dependencies using ...
This assembly was expected to be in the local runtime store as the application was published using the following target manifest files:
Read more >How to resolve “Could not load file or assembly … or one of its ...
More often the first step — the assembly is not found matching the version. ... We understood which version the application gets and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Still having this issue. Mine is with application insights.
Error: An assembly specified in the application dependencies manifest (XXX.deps.json) was not found: package: ‘Microsoft.ApplicationInsights.AspNetCore’, version: ‘2.1.1’ path: ‘lib/netstandard1.6/Microsoft.ApplicationInsights.AspNetCore.dll’ This assembly was expected to be in the local runtime store as the application was published using the following target manifest files: aspnetcore-store-2.0.0-linux-x64.xml;aspnetcore-store-2.0.0-osx-x64.xml;aspnetcore-store-2.0.0-win7-x64.xml;aspnetcore-store-2.0.0-win7-x86.xml
I encountered this issue when I published my app built for 2.0.3 onto a server with 2.0.0 only installed. Obviously it couldn’t work and should fail but I believe error message could be a bit clearer.
And ideally as I was publishing the app via
dotnet publish -c Debug /p:WebPublishMethod=MSDeploy
it could tell me about missing dependencies.