dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
https://asp.net
MIT License
35.49k stars 10.03k forks source link

Corrupt log messages after adding SPA to .Net Core 3.1 app #25726

Closed LeslieMurphy closed 3 years ago

LeslieMurphy commented 4 years ago

Describe the bug

I see corrupt information in the log after adding spa to my .Net Core 3.1 ASP.NET app . How do I fix this?

Microsoft.AspNetCore.SpaServices: Information: > dynamic_form_poc@0.1.0 start C:\Users\xxxx\source\Workspaces\xxx\xxx\ClientApp

rimraf ./build && react-scripts start

i 「wds」: Project is running at http://192.168.0.4/

Microsoft.AspNetCore.SpaServices: Information: i 「wds」: webpack output is served from

Microsoft.AspNetCore.SpaServices: Information: i 「wds」: Content not from webpack is served from C:\Users\xxxx\source\Workspaces\xxx\xxx\ClientApp\public i 「wds」: 404s will fallback to / Starting the development server...

To Reproduce

Take existing .Net Core app and add spa for React

services.AddSpaStaticFiles(configuration => { configuration.RootPath = "ClientApp/build"; });

...

app.UseDefaultFiles(); app.UseStaticFiles(); app.UseSpaStaticFiles(); app.UseSpa(spa => { spa.Options.SourcePath = "ClientApp"; spa.UseReactDevelopmentServer(npmScript: "start"); // this also adds a proxy to the dev server });

Further technical details

.NET SDK (reflecting any global.json): Version: 5.0.100-preview.8.20417.9 Commit: fc62663a35

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

Host (useful for support): Version: 5.0.0-preview.8.20407.11 Commit: bf456654f9

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

.NET runtimes installed: Microsoft.AspNetCore.All 2.1.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All] Microsoft.AspNetCore.App 2.1.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 5.0.0-preview.8.20414.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 2.1.21 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 5.0.0-preview.8.20407.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 3.1.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 5.0.0-preview.8.20411.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

VS Community 16.8.0 Preview 2.1

ghost commented 4 years ago

Thanks for contacting us. We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

ghost commented 4 years ago

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

javiercn commented 3 years ago

@LeslieMurphy thanks for contacting us.

We've significantly changed the way the SPA templates are setup for development and production to align with how other backend frameworks approach this and as a result we no longer use SpaServices as part of the development workflow.

While we haven't removed or obsoleted the code, we don't plan to make future changes/fixes on it and we recommend people migrate to the new approach we use in the templates.