PR #2
Merged
PR #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…315.3 (#30960) [main] Update dependencies from dotnet/efcore
…viderUsesContractResolver Andremi/conversion result provider uses contract resolver
…o-main [automated] Merge branch 'release/5.0' => 'main'
- SocketAsyncEventArgs have lots of state on them and as a result are quite big (~350) bytes at runtime. We can pool these since sends are usually very fast and we can reduce the per connection overhead as a result. - We also allocate one per IOQueue to reduce contention. - Fixed buffer list management - Disposed pool when the transport is disposed - Added project to slnf so running tests in VS was possible - Clear the buffer and buffer list before returning to the pool - This cleans up dumps as the pooled senders don't see references to buffers while pooled in the queue - Keep track of items in the pool separately from the queue count.
* Add Consolidated view classifier to make view types internal * Address feedback from peer review * Address feedback and fix tests
…o-main [automated] Merge branch 'release/2.1' => 'main'
[main] Update dependencies from dotnet/runtime dotnet/efcore - Remove assemblies from the ref and runtime pack - Remove more references
Co-authored-by: Pranav K <[email protected]>
Co-authored-by: Pranav K <[email protected]>
…316.2 (#30991) [main] Update dependencies from dotnet/efcore
* Connection error for invalid HTTP/3 frame on request stream * Update src/Servers/Kestrel/Core/src/CoreStrings.resx * Write frame types and errors codes in logs as per spec * Clean up * Add HTTP/3 connection exception with code * Connection abort * More abort connection stuff * More test * More tests * PR feedback
…317.1 (#30998) [main] Update dependencies from dotnet/efcore
…tch value object (#30974) * - Adding a new ConvertTo overload to ConversionResultProvider that takes an IContractResolver and hooking it up for ListAdapter - Unit test to verify above works for heterogenous collections
[main] Update dependencies from dotnet/runtime dotnet/efcore
* Dispose streams that don't fit in pool * PR feedback
* Respect consolidated views in all document classifiers * Address feedback from peer review
* Add API to Renderer to trigger a UI refresh on hot reload Fixes #30816
* Fix credscan issues in DataProtection * Fix credscan issues in Identity, except where they affect checked in certs * Updated scan
* Wires up static web assets support on the WebViewManager.
- Removed the nullable from the Socket property as approved in API review - Make the IConnectionSocketFeature an additional feature instead of one implemented on the TransportConnection. - Added a test to verify it works
Co-authored-by: Roman Marusyk <[email protected]>
…o-main [automated] Merge branch 'release/5.0' => 'main'
- #31044 - `RazorPagesTemplate_RazorRuntimeCompilation_BuildsAndPublishes()` Co-authored-by: Doug Bunting <[email protected]>
…o-main [automated] Merge branch 'release/5.0' => 'main'
…o-main [automated] Merge branch 'release/3.1' => 'main'
* Remove unused dependency * Remove outdated AAD sample
* Add failing E2E case * Implement fix * Add E2E test * Update src/Components/test/testassets/BasicTestApp/EventCustomArgsComponent.razor * Update suppressions
* A new package Microsoft.AspNetCore.SpaProxy has been added that is
used by the templates to launch their development proxy via npm/yarn.
* The SPA development proxy for each CLI now is the frontend for the
application and proxies the requests to the backend which is the
ASP.NET Core application.
* At publish time the application assets are copied to the wwwroot.
* SpaServices.Extensions has been removed from the templates since it is
no longer needed. MapFallbackToFile("index.html") handles unknown
requests and serves the SPA entry point.
* The templates have been updated to keep using HTTPS with the SPA proxy
configured to use the ASP.NET Core HTTPS development certificate via a
new aspnetcore-https.js file that ships within the template.
* The configuration for angular has been updated with a proxy.conf.js
file to proxy requests to the backend.
* The entry point for the application in development is now
https://localhost:5002 when using https and http://localhost:5002
otherwise.
This does a big chunk of #30248 while heavily refactoring the RequestDelegateFactory by splitting it out into a bunch of smaller methods. For part 2 of #30248, a "scalar value type that lives in the System namespace", I went with the alternative of "Something convention-based like the presence of a bool TryParse(string, out T) method" instead. This conventions work for types in any namespace including user-defined types.
* Avoid closure caused by local function - Made the local function static and passed state via parameters.
* Remove form support from minimal APIs * Add * MapActionSample -> MinimalSample * Remove MapActionSample.csproj from Mvc.slnf
Updates the react template to use the http-proxy-middleware for handling the requests instead of the asp.net core proxy in the same way it's done for the Angular template.
…time (#31576) [main] Update dependencies from dotnet/emsdk dotnet/efcore dotnet/runtime - Add `RemoveDevicePlatformSupport` To `Microsoft.AspNetCore.Authentication.Negotiate.csproj`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.