-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Factor WebAssembly debugging infrastructure out of Microsoft.AspNetCore.Components.Server #6519
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
Changes from all commits
7c5e455
3a21f26
ae35e67
64686da
2601fd9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
<Project Sdk="Microsoft.NET.Sdk"> | ||
|
||
<PropertyGroup> | ||
<TargetFramework>netstandard2.0</TargetFramework> | ||
<Description>Runtime server features for ASP.NET Core Blazor applications.</Description> | ||
<IsProductPackage>true</IsProductPackage> | ||
</PropertyGroup> | ||
|
||
<ItemGroup> | ||
<PackageReference Include="Microsoft.AspNetCore.Hosting.Abstractions" Version="$(AspNetCorePackageVersion)" /> | ||
<PackageReference Include="Microsoft.AspNetCore.WebSockets" Version="$(AspNetCorePackageVersion)" /> | ||
<PackageReference Include="Microsoft.AspNetCore.Hosting.Abstractions" Version="$(AspNetCorePackageVersion)" /> | ||
<PackageReference Include="Newtonsoft.Json" Version="$(NewtonsoftJsonPackageVersion)" /> | ||
|
||
<!-- Used by ws-proxy sources only. Remove this once we're able to consume ws-proxy as a NuGet package. --> | ||
<PackageReference Include="Mono.Cecil" Version="0.10.0-beta7" /> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm sure this will come up at some point, and it's OK to use an issue to track - but is there a stable version we can use? We don't generally want to depend on prerelease in release, and it looks like that would be easy to happen. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Looks like there have been 2 stable releases of Mono.Cecil on nuget since the 0.10.0-beta7 version. Latest version: Mono.Cecil 0.10.1 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good points. Thanks for the info. To avoid waiting for another long CI build, I'm going to make the |
||
</ItemGroup> | ||
|
||
</Project> |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -87,12 +87,6 @@ public static IApplicationBuilder UseBlazor( | |
}); | ||
} | ||
|
||
// Accept debugger connections | ||
if (config.EnableDebugging) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a plan/need to clean this up in BlazorConfig? Or is this a temporary thing while we figure out how to ship all of this. Personally, I feel like having this show up in startup code is an improvement because it's more inline with our other diagnostics features. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I'm sure we'll review and change the Blazor build/hosting mechanisms as we head towards a stable release of that. |
||
{ | ||
app.UseMonoDebugProxy(); | ||
} | ||
|
||
// Finally, use SPA fallback routing (serve default page for anything else, | ||
// excluding /_framework/*) | ||
app.MapWhen(IsNotFrameworkDir, childAppBuilder => | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<3