Skip to content

Use project path instead of working directory to resolve launchSettings.json #23184

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

Merged
merged 2 commits into from
Dec 31, 2021

Conversation

pranavkm
Copy link
Contributor

Fixes dotnet/aspnetcore#35393

dotnet-watch attempts to read the app's launchSettings.json to read things like the launch URL. Currently the URL is read relative to the working directory (it looks for $WorkDir/Properties/launchSettings.json). However, this is incorrect if the --project option is used to specify a project path / directory. This change updates the code to use the project directory and adds a couple of tests.

@ghost ghost added the Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch label Dec 27, 2021
@pranavkm pranavkm requested a review from TanayParikh December 27, 2021 23:14
@TanayParikh
Copy link
Contributor

Looks like the CI isn't happy yet though 👀

Copy link
Contributor

@TanayParikh TanayParikh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, CI is green

@pranavkm pranavkm merged commit 023b715 into main Dec 31, 2021
@pranavkm pranavkm deleted the prkrishn/path branch December 31, 2021 17:56
pranavkm added a commit that referenced this pull request Jan 3, 2022
…gs.json (#23184)

* Use project path instead of working directory to resolve launchSettings.json

Fixes dotnet/aspnetcore#35393

* Update DotNetWatcherTests.cs
pranavkm added a commit that referenced this pull request Jan 3, 2022
* Assume basline capabilities (#23185)

In a Blazor app, the apply-update capabilities are available after the app is up and running in the browser.
Occasionally it takes long for the app to start up and our baseline task times out. Currently we return an empty
list of capabilities which causes the compiler to produce no deltas. This PR bumps up the timeout ever so slightly
and returns baseline capabilities instead.

Fixes dotnet/aspnetcore#36723

* Use project path instead of working directory to resolve launchSettings.json (#23184)

* Use project path instead of working directory to resolve launchSettings.json

Fixes dotnet/aspnetcore#35393

* Update DotNetWatcherTests.cs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dotnet-watch: Blazor Hosted project specifying Server path via --project does not work
2 participants