* Updates the angular template to exclude the client-side files from the single file publish output
* Updates the react template to exclude the client-side files from the single file publish output
* Updates the react-redux template to exclude the client-side files from the single file publish output
- #4914
- test service ref MSBuild tasks
- add `MockBuildEngine` class to support tests where a task logs
- correct an incredibly minor product issue about logging errors for `@(OpenApiProjectReference)` items
- set `%(SourceProject)` metadata and use it when logging
- add test project that builds and can be tested in the future
- #4923
- typo caused problems when cleaning files
- add `%(OpenApiProjectReference.GlobalPropertiesToRemove)` metadata
- stop removing `$(Configuration)` or `$(Platform)` global properties
- address timing issues cropping up occasionally in builds using service ref features
- avoid `AfterTargets="Build"`; referencing projects sometimes continue while post-build work is done
- instead use `BeforeTargets="Build"` since that's a no-op target wrapping up a build
- set only properties in buildMultiTargeting\Microsoft.Extensions.ApiDescription.Server.targets
- items not evaluated early enough to reference in all cases
- rename Microsoft.Extensions.ApiDescription.Client tasks
- remove net461 task assembly
- add '--quiet' option
- add '--debug' option (when building Debug configuration)
- support `--` in `dotnet-getdocument`; users may want to explictly add options for GetDocument.Insider
- remove '--no-color' option
- use `IReporter` extension methods instead of static `Reporter` class
- reduce `static` use to ease testing (coming soon) and share the `IConsole` and `IReporter`
- add `ProgramBase`
- allow mix of known and unknown command-line arguments
- maintain existing behaviour using switch added in aspnet/Extensions#2210
nits:
- add a couple more `CommandLineApplicationExtensions` methods
- take VS suggestions
Fixes: #13086
- Fixed some wrong logging (wrong EventIds)
- Added a base class for ignitor tests
- Centralized code for capturing data in ignitor
- Make `WaitForXyz` methods return the thing they found
- Make `WaitForXyz` methods report logs on timeout
- Fix synchronization problems with some tests
- Split invalid event tests into their own class for code reuse
The main thing here is that some of the JS interop reliability tests had
causality/synchronization problems. They were either not waiting for a
render batch, or they were not *triggering* a render batch.
In addition to that, I did a general consolidation of the infrastructure
for these tests to make sure that they are all using the same set of
practices. I found and fixed cases where tests were using timeouts that
were too small (inconsistency) or where they were using non-threadsafe
data structures (these tests always involve concurrency).
Adds the ability to specify multiple assemblies to the Router
component.
Prior to preview 8, the router would search all dependencies of
`AppAssembly` for routable components. We made an intentional change to
stop that. However, we haven't yet give users a way to specify multiple
assemblies if their components are split across assemblies.
* [Blazor] Allows multiple components as entry points
* Removes all overloads that register a component statically with aborts
selector.
* Updates render component to have a RenderMode parameter that indicates
how the component must render. Valid values are Static, Server, and
ServerPrerendered.
* When using Server or ServerPrerendered we emit marker comments into
the page that are later used by blazor.server.js to bootrstrap a
blazor server-side application.
- start of #4914 and #4896
- make infrastructure more accessible to these projects
- update list of projects
- run `.\eng\scripts\GenerateProjectList.ps1`
* Ignore overriden properties in component parameters
* Modify MemberAssignment to return shadowed properties, but not inherited properties
* Modify ComponentProperties to throw if a Parameter property is non-public
Fixes https://github.com/aspnet/AspNetCore/issues/13162
- #12792
- client:
- add error if OpenAPI file does not exist
- separate unsupported TFM case from targets being called when disabled
- server:
- generalize multi-targeting handling in Microsoft.Extensions.ApiDescription.Server
- add `$(_OpenApiGenerateDocumentsTFM)`, the TFM used when invoking inner build
- default `$(OpenApiGenerateDocuments)` to 'true' only when a supported TFM exists
- add separate error for non-existent cache file in `OpenApiGetDocuments` target
- add error in `GetDocumentInsider` if no documents are found
- make `<Warning />` in the targets file an `<Error />`
- add more text to existing `ServiceNotFound` error
- both:
- write errors to `stderr`
- clean up top-level output for `Exception`s
- stop writing the `Message` twice
* Correct "Open API" mentions; should be "OpenAPI"
- change package tags and comments
* Add service reference projects to MvcNoDeps.slnf
nits:
- add "service reference" tag in Microsoft.Extensions.ApiDescription.* packages
- add "document generation" tag in Microsoft.Extensions.ApiDescription.Server package
- `.Trim()` TFM properties because `<TargetFrameworks>;netcoreapp3.0;;</TargetFrameworks>` is allowed
- don't use bold black for verbose messages
- reorder MSBuild property settings for readability
Fixes: #12553
This change renames all of our browser/DOM specific types from
`UIFooEventArgs` to `FooEventArgs` and puts the in the `.Web` namespace.
In addition to this, we're moving `EventHandlers` and `BindAttributes`
to the same. This has the impact of scoping the mappings those classes
provide based on the `.Web` namespace.
This means that we now expect `.Web` to be present as a using in
basically all contexts for a browser-based Blazor app. Updated
templates, samples and tests. I'll also need to update about a million
tests in the compiler codebase.
I've logged https://github.com/aspnet/AspNetCore.Docs/issues/13832 to
track the docs and release notes part of this work.