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

.Net8 ClickOnce app HARD crashes when launched with arguments. #338

Open
MrFJ opened this issue Feb 21, 2024 · 2 comments
Open

.Net8 ClickOnce app HARD crashes when launched with arguments. #338

MrFJ opened this issue Feb 21, 2024 · 2 comments
Assignees

Comments

@MrFJ
Copy link

MrFJ commented Feb 21, 2024

Description

I’m trying to launch an offline WPF ClickOnce app from another app, with launch parameters. After trying many different solutions, I think I’ve found a solution, except I’ve run into an issue: The app crashes as soon as I launch it, just after checking for new version, before even getting into the code. No exceptions, no logs, no windows event log. As far as I can tell this way of launching the app would have worked at least in .Net Framework, but perhaps even in .Net 6 (Sources are unclear)

Configuration

.Net 8
Windows 10, Visual Studio 2022
Any architecture.

Regression?

Sources on the internet claim it worked in .Net framework. Whether it worked in .Net 5 or .Net 6 is unclear to me.

Other information

To replicate the issue, create a new WPF click once app in .Net 8 (Or .Net 7). Publish it to a network drive. Install it, then try to launch it from a command prompt using the following command:
“%appdata%\Microsoft\Windows\Start Menu\Programs[PUBLISHERNAME][APPNAME].appref-ms” test

More info on journey with this issue: https://stackoverflow.com/questions/77859562/clickonce-net7-wpf-app-why-is-activationuri-null

@NikolaMilosavljevic
Copy link
Member

[Triage] @NikolaMilosavljevic please investigate.

@FFPJKamstrup
Copy link

I found a "Fix": Deleting the hidden .vs folder fixed the issue. It returns once in a while and I have to delete the .vs folder again before publishing. It's weird, but it works. I wish I knew why...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants