dotnet / dotnet/wpf

WPF ClickOnce Deployment missing refs folder

Open
#8,455 2 comments 0 reactions 0 assignees View on GitHub
Investigate
Dominant language
C#
Stars
7.7k
Forks
1.3k
Avg merge
1d 11h
Merged PRs (30d)
61

Description

### Description

I have a WPF application based on the SDK project type Microsoft.NET.Sdk. A feature of this application is to start a local MVC site as part of the application using the WebApplication builder. This has been an issue with .NET 6/7/8. When publishing a ClickOnce deployment it does not include the "refs" subfolder which is created when building the application. Because of this running the ClickOnce deployed application fails to be able to render hosted web pages exhibited out of the WPF application. Only by copying the refs folder manually to the target system am I able to render the local hosted MVC razor pages. I need a way to either make the refs folder not required, or a way of adding them into the ClickOnce deployment process.

### Reproduction Steps

Create a wpf application. Add a web application listener within the startup. Publish a ClickOnce package. Install the ClickOnce package. Try to navigate to a page within the web application.

### Expected behavior

To be able to render pages from a local web application listener within a WPF application and deploy using ClickOnce package without need of intervention.

### Actual behavior

Fail to render page from local web application listener within a WPF application that was deployed using a ClickOnce package.

### Regression?

_No response_

### Known Workarounds

Copying the refs folder down from a published location upon application startup, and require restart.

### Impact

_No response_

### Configuration

Windows only due to WPF installation
.NET 6/7/8
x64

Not specific to any configuration other than hosting a web application listener inside a WPF application.

### Other information

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.