This issue has been moved from a ticket on Developer Community.

The UseResponseCaching method in the ResponseCachingExtensions class in the Microsoft.AspNetCore.Builder namespace is missing XML Documentation Comments.

(As a quick aside, the "Summary" sec

If you're creating a bug/problem report, please include followings:

• Your Abp package version. - 5.2
• Your base framework: .Net Core. 3.1

Aspnetboilerplate Angular Template 5.2

Integration with the explanation from the page:
https://aspnetboilerplate.com/Pages/Documents/OData-AspNetCore-Integration

in .net core 3.1 mvc.internal is removed:

Could not load type 'Microsoft.AspN

Right now when I need to create a new website what should I choose? The templates look similar but with some differences. I think this should be documented with some good guidance for beginners.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0b952f8a-18e1-4843-0741-6ca877fb303a
• Version Independent ID: d80dfb96-bc86-a

Hi,

Similar to issue #125 it would be good to allow the same for the letsencrypt certbot container, could you please add a bind IP question during the bitwarden.sh install part in the letsencrypt section.

https://github.com/bitwarden/server/blob/36e97ccbd255ec50ddbcb668ba12792d3a485985/scripts/run.sh#L65-L77

And something similar with (or storing the information for later in the previous

Currently we debug over an attach to the process.

An idea would be to setup an own debug-profile with the "dotnet electronize init" command.

It seems that someone edited out all documentation for SwaggerToTypeScriptClientGenerator.
Is is possible to revert back to older revisions to have it available for users?

https://github.com/RicoSuter/NSwag/wiki/SwaggerToTypeScriptClientGenerator#extended-classes-and-extension-code

I think it would be useful to add a mention about Async streams (IAsyncEnumerable) when a developer wants to tackle 'Handle streams of data' problem.

In this quickstart, Info() has been replaced by OpenApiInfo():
https://github.com/microsoft/aspnet-api-versioning/wiki/API-Documentation#aspnet-core

Thanks for all you do to maintain this site.

npm ERR! code ELOCKVERIFY
npm ERR! Errors were found in your package-lock.json, run npm install to fix them.
npm ERR! Missing: expo@~37.0.3
npm ERR! Missing: react@~16.9.0
npm ERR! Missing: react-dom@~16.9.0
npm ERR! Missing: react-native@https://github.com/expo/react-native/archive/sdk-37.0.0.tar.gz
npm ERR! Missing: react-native-web@~0.11.7
npm ERR! Missing: babe

Bug

If BaGet is started in debug mode it will log:

dbug: Microsoft.EntityFrameworkCore.Model.Validation[10600]
      The property 'PackageKey' on entity type 'PackageDependency' was created in shadow state because there are no eligible CLR members with a matching name.
dbug: Microsoft.EntityFrameworkCore.Model.Validation[10600]
      The property 'PackageKey' on entity type 'Packa

When using current lint settings in packages.json, eslint fails if there is no json file inside ClientApp folder.
Correct way would be:

"lint": "eslint -c ./.eslintrc.js \"ClientApp/**/*.{js,vue,json}\" webpack*.js",

Describe the bug
Not a CSLA bug, a doc bug :)

Version and Platform
Irrelevant

Code that Fails
Not code per-se....I just realized that this doc page was never finished: https://github.com/MarimerLLC/csla/blob/master/docs/Analyzers.md. Need to finish that.

Stack Trace or Exception Detail
No stack trace.

Additional context
None

They take so long to execute we only run them on Chrome. We should review them and streamline them a bit.

in the Documentation it says that the connectionString will be specified in the OnConfiguring like so

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
{
optionsBuilder.UseSqlite(ConnectionString);
base.OnConfiguring(optionsBuilder);
}

and i also followed the dataIsolation sample

this is inside setupDb()

var ti =

Supported scenarios and unsupported scenarios are not well explained outside the example on the README.

Improve Documentation with more examples and explanations of what will/won't work.

• Set up Github Pages site with great documentation

• Improve & Update README

• XML <summary> tags on classes & methods.

This should also mention that it will not work on sharded collection cases.