* Add description to package
* Automatically resolve proxy target based on available environment variables
* Introduce a temporary page while the proxy is launching and redirect to the proxy page when visiting the backend for the first time
* Switch to probing the proxy on a per-request basis. This helps in cases where the user closes the proxy window (for example when the app is run without debugging via Ctrl+F5) in IIS Express scenarios.
Commit migrated from dotnet/aspnetcore@64efb3eea5
This reverts commit c6346a336a.
It breaks or templates, we can make this change once we are consuming an SDK version that has the right bits.
Commit migrated from dotnet/aspnetcore@131d207102
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.
Commit migrated from dotnet/aspnetcore@e5667a925e
* 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.
Commit migrated from dotnet/aspnetcore@6bc4b79f4e
* Use Random.Shared
Use the new .NET 6 Random.Shared static property where possible.
See https://github.com/dotnet/runtime/pull/50297.
* Revert WebApi-CSharp changes
For some reason I don't understand, this template doesn't see Random.Shared when compiled so this reverts the previous change for this template.
Commit migrated from dotnet/aspnetcore@2458822000
Description
This PR updates the version of the caniuse-lite dependency to the latest version on our React and React/Redux SPA templates. The caniuse-lite dependency provides a database of browser features and their support across different browsers (as seen in caniuse.com). We were getting a warning because the dependency was out-of-date which meant that it was reporting compatibility info that was no longer accurate.
This PR also updates the version of node-sass to the latest version which no longer depends on the no-longer-supported Python 2.
Customer Impact
This bug was discovered during CTI validation.
This bug has a low severity because the user application can still run although JavaScript-based build tooling might report that the developer is leveraging browser features that aren't supported by the browser when they actually are.
Users can workaround this by running npx browserslist@latest --update-db inside their ClientApp directory. Users can also manually upgrade node-sass to v5 by editing their package.json file.
Regression?
No.
Risk
Low risk, because:
Change was validated manual
This fix applies the changes recommended by the browserlist library
Commit migrated from dotnet/aspnetcore@e0213bf8af
## Description
Updates outdated dependencies for the Angular, React and React redux templates.
## Customer Impact
Customers creating new projects get obsolete versions of some javascript dependencies and need to update them manually.
## Regression?
- [ ] Yes
- [X] No
[If yes, specify the version the behavior has regressed from]
## Risk
- [ ] High
- [ ] Medium
- [X] Low
The changes only update dependencies and have been tested manually.
## Verification
- [X] Manual (required)
- [ ] Automated
## Packaging changes reviewed?
- [ ] Yes
- [ ] No
- [X] N/A
Commit migrated from dotnet/aspnetcore@94804f3100
Description
This PR updates the version of the caniuse-lite dependency to the latest version on our React and React/Redux SPA templates. The caniuse-lite dependency provides a database of browser features and their support across different browsers (as seen in caniuse.com). We were getting a warning because the dependency was out-of-date which meant that it was reporting compatibility info that was no longer accurate.
This PR also updates the version of node-sass to the latest version which no longer depends on the no-longer-supported Python 2.
Customer Impact
This bug was discovered during CTI validation.
This bug has a low severity because the user application can still run although JavaScript-based build tooling might report that the developer is leveraging browser features that aren't supported by the browser when they actually are.
Users can workaround this by running npx browserslist@latest --update-db inside their ClientApp directory. Users can also manually upgrade node-sass to v5 by editing their package.json file.
Regression?
No.
Risk
Low risk, because:
Change was validated manual
This fix applies the changes recommended by the browserlist library
Commit migrated from dotnet/aspnetcore@135f7820d1
* Shorten package version properties
- `$(...PackageVersion)` -> `$(...Version)`
- inspired by a similar dotnet/efcore change
- aligns names with Arcade SDK, meaning our values apply consistently
* Remove unused PublishSymbols.proj and related property
- restore Arcade's control of `$(MicrosoftSymbolUploaderBuildTaskVersion>)`
- would otherwise result in a version downgrade
* Update `$(MicrosoftNetCompilersToolsetVersion)` to match Arcade's value
- avoid using an older toolset
- now successfully overriding Arcade value
* Avoid an odd `CS8603` error
- delete the unused `GetOptionalProperty(...)` method
* Correct an unintentional change reading package metadata
- `%(ReferencePathWithRefAssemblies.NuGetPackageVersion)` is the correct name
Commit migrated from dotnet/aspnetcore@44c0e6651e
[master] Update dependencies from dotnet/runtime dotnet/efcore
- Update TFM net5.0 -> net6.0
- Introduce $(TargetTFM)
- TargetTfm -> DefaultNetCoreTargetFramework
- Updated: NETCoreAppMaximumVersion
- Apply suggestions from code review
Co-authored-by: Doug Bunting <6431421+dougbu@users.noreply.github.com>
- Fix version numbers used in Blazor WASM SDK
- Address feedback from peer review
- Fix check for platform version
- Fix build config for dotnet-watch project
- Update TFM net5.0 -> net6.0
- Introduce $(TargetTFM)
- TargetTfm -> DefaultNetCoreTargetFramework
- Apply suggestions from code review
Co-authored-by: Doug Bunting <6431421+dougbu@users.noreply.github.com>
- Fix version numbers used in Blazor WASM SDK
- Address feedback from peer review
- Remove workaround in dotnet-watch tests
- Testrunner to 5.0 and adding workarounds
- Try props.in
- net50
- Fixup KnownFrameworkReference for integration tests
- Resolve a few comments
- don't use repo-specific properties in shipping file
- pass `$(DefaultNetCoreTargetFramework)` into template files used in tests
- Update src/Components/WebAssembly/Sdk/src/targets/Microsoft.NET.Sdk.BlazorWebAssembly.Current.targets
- Update KnownFrameworkReference for template tests
- Use DefaultNetcoreTFM
- Undo change to props.in
- Update src/ProjectTemplates/test/ProjectTemplates.Tests.csproj
- Update GenerateTestProps.targets
- this is where `$(KnownAppHostPackOrFrameworkReferenceTfm)` is needed
- Update src/ProjectTemplates/test/ProjectTemplates.Tests.csproj
- additional template input not needed here
- Other file changes
- Rename the one net5.0 directory in the repo
- Fixup rebase remnants
- Use runtime and ref/ assemblies matching repo in Helix testing
- add Directory.Build.*.in files based on project template test infrastructure
- use files as import boundary where the project doesn't create its own Directory.Build.* files
- ensure `dotnet-watch` tests also use the latest runtime and ref/ assemblies
- Switch Directory.Build.*.in files in Helix content
- ensure item manipulation is done after base items exist
nit: Fix *.in exclusion
- Update TFM workaround to reference 5.0 instead of 3.1 (dotnet/aspnetcore#26991)
- Make some Directory.Build.*.in settings override-able
- that is, move some properties to Directory.Build.props.in
also
- fix `Condition`s that resulted in empty Directory.Build.targets
- separate Directory.Build.empty.in
- ensure RunTests project is _not_ affected by root Directory.Build.* files
- Update SDK
- Set `$(DefaultNetCoreTargetFramework)` in Helix root Directory.Build.props
= `dotnet-watch` tests otherwise fail with "The TargetFramework value '' was not recognized"
- Extend Helix Directory.Build.* workarounds
- generate Directory.Build.* files when restoring any projects
- include generated files in Helix runs needing the latest runtime
- copy generated files when testing `dotnet-watch` locally
- include generated content in Microsoft.NET.Sdk.BlazorWebAssembly.IntegrationTests test assets
- remove duplicate settings from existing Directory.Build.* files
- ensure shared framework and targeting packs are laid out under .dotnet/ before test assets restore
- !fixup! Remove extra end tags
- !fixup! Don't build GenerateFiles.csproj in desktop `msbuild`
- !fixup! Arcade uses different test targets
- Disable `crossgen` when building for Helix runs
- make `$(CrossgenOutput)` property override-able
- use override in CI jobs that submit to other platforms
- for now, leave the ARM64 Helix jobs alone (build on Ubuntu, run in Debian)
nits:
- correct condition for `$(GenerateCrossgenProfilingSymbols)`
- set `$(ASPNETCORE_TEST_LOG_DIR)` in every step of the Helix build jobs
- Ensure ReadRequest type can be loaded on server. Fixesdotnet/aspnetcore#26882 (dotnet/aspnetcore#26931)
- Enable debugging when using embedded PDBs (dotnet/aspnetcore#27107)
* Fix debug using embedded PDBs.
* Check for either debugBuild or referenced PDBs
Co-authored-by: Thays <thaystg@gmail.com>
- Ensure Blazor JS files are up-to-date
- Merge branch 'master' into darc-master-76e24f4d-c90c-42ac-a1e5-411ae61ca37b
Commit migrated from dotnet/aspnetcore@219ecd6880
templates will be showing the templates directly in the New Project
Dialog instead in the One ASP.NET dialog.
In this PR I have updated the English titles. For localized strings we
will need to get those from the localization team. I believe we are not
setup for that to be automated here.
I think we should merge the English strings because they are the most
used, and for other locales we will show the old localized names for
now. If it's difficult to get those localized, I can work with @phenning
to see if we can localize those files this time.
Commit migrated from dotnet/aspnetcore@118d6b2986
* Fix header tab ordering issues. Fixes 1163117
* Ensure text can be zoomed to 200% without switching to mobile layout. Fixes 1163184.
* Ensure "Log out" link can show focus state. Fixes 1162890
* Use screen reader-friendly link text. Fixes 1163642
* Update template test
Commit migrated from dotnet/aspnetcore@ecc2ba16b8
* Updates to IdentityServer 4.0.4
* Updates templates with the new migrations.
* Fixes a small configuration bug that required the configuration for the key to be specified.
* Updates the error url in IdentityServer config to match our template defaults.
Commit migrated from dotnet/aspnetcore@38563dd8d1
* nit: Remove useless `$(HasReferenceAssembly)` settings
- set in /Directory.Build.targets
- `true` only in `$(IsAspNetCoreApp)` projects
* nit: Remove useless `$(CompileUsingReferenceAssemblies)` settings
- no current versioning differences between ref/ and src/ assemblies when targeting default TFM
* Add more `$(GenerateDocumentationFile)` settings
- increases the number of generated doc files, mostly without problems
- !fixup! correct typo in `DebugProxyHost` doc comments
- was not generating a doc file before
- remove previous (ineffective) src/Components/Directory.Build.targets setting
- nit: remove a duplicate `$(GenerateDocumentationFile)` setting
* nit: Remove useless `$(IsPackable)` settings
- only analyzers and implementation projects are packable by default
- main use case for explicit setting is projects shipping only in shared framework
- conditional setting in src/Mvc/Directory.Build.props just subset logic in /Directory.Build.targets
* nit: Remove useless `$(IsProjectReferenceProvider)` settings
- only implementation projects are providers by default
* nit: Remove useless `$(IsTestAssetProject)` settings
- set in src/Mvc/test/WebSites/Directory.Build.props
* !fixup! Looks like `InProcessNewShimWebSite` must compile w/o ref/ assemblies
- restore `$(CompileUsingReferenceAssemblies)` in this one project
Commit migrated from dotnet/aspnetcore@c4c6e25a06
Hao Kung
Javier Calvarro Nelson
Phil Henning
Martin Costello
Justin Kotalik
Chris Ross
Pranav K
Safia Abdalla
Doug Bunting
Damla Köksal
John Luo
Benjamin Day
Eugene Ogongo
dotnet-maestro[bot]
Chris Yungmann
Sayed Ibrahim Hashimi
Steve Sanderson
Sébastien Ros
Ajay Bhargav B