question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Published Package doesn't start

See original GitHub issue

Bug description If a sideload package is created and installed it will not start. After attaching a VS debugger the following error message is produced even on the machine the build was created and release or debug builds within VS work fine. Error: An assembly specified in the application dependencies manifest (App1.deps.json) was not found: package: 'runtimepack.Microsoft.NETCore.App.Runtime.win-x64', version: '5.0.0' path: 'Microsoft.VisualBasic.Core.dll''App1.exe' (Win32): Loaded 'C:\Windows\System32\kernel.appcore.dll'. Symbols loaded.

dotnet --info produces following output:

.NET SDK (reflecting any global.json):
 Version:   5.0.100
 Commit:    5044b93829

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19041
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\5.0.100\

Host (useful for support):
  Version: 5.0.0
  Commit:  cf258a14b7

.NET SDKs installed:
  5.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Steps to reproduce the bug

  1. Create a new project with package
  2. Publish package with sideloading (Add a valid Certificate for installation)
  3. Install published package
  4. (optional) Attach debugger (Debug -> Other debug targets -> Debug installed app packages)
  5. Start App

Expected behavior App should start the same way as it does in VS

Version Info

  • Microsoft.WinUI 3.0.0-preview3.201113.0
  • Blank desktop App with package C#
  • VS 16.9.0 Preview 1.0
  • .net SDK 5.0.100 (Installed with VS)
  • Windows 10 19041

NuGet package version: [Microsoft.WinUI 3.0.0-preview3.201113.0]

Windows app type:

UWP Win32
Yes
Windows 10 version Saw the problem?
Insider Build (xxxxx)
May 2020 Update (19041) Yes
November 2019 Update (18363)
May 2019 Update (18362)
October 2018 Update (17763)
April 2018 Update (17134)
Fall Creators Update (16299)
Creators Update (15063)
Device form factor Saw the problem?
Desktop Yes
Xbox
Surface Hub
IoT

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:11 (4 by maintainers)

github_iconTop GitHub Comments

3reactions
lhakcommented, Dec 3, 2020

I have observed the same issue with the app not starting. In my case, setting PublishTrimmed to false in the Properties\PublishProfiles\win10-X.pubxml file fixed it.

1reaction
akanieskicommented, Dec 3, 2020

Running into the exact same problem as you list out above.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unable to install published package - How to Use GitLab
Here are the steps to fix: Update your project to be Public. Make sure that the project has package registry setting enabled.
Read more >
I published one package on npm, but it's not showing in the ...
I published one package as a public & i am trying to search it on npm (https://www.npmjs.com/), but there is no package available...
Read more >
Published package does not appear in Orchestrator
Hi I'm publishing updates of my automation and it doesn't give an error, but it's not showing up in the orchestrator what could...
Read more >
Testing npm packages before publishing | by Carl Vitullo
A package that has been published to npm is packaged as a tar archive, with configuration about how it should be packed. Symlinking...
Read more >
Unpublishing packages from the registry
Once a package is unpublished, republishing under the same name is blocked for 24 hours. If you've unpublished a package by mistake, we'd...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found