Line 137 & 165 in src/Identity/Extensions.Core/src/Resources.resx should be "Username" not

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

All the links labeled "example" seem to link to the (skeletal) class documentation for the associated topic, rather than actual examples. This doesn't provide anything similar to an actual example.

Document Details

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

• ID: 54b3ef64-9e17-3aab-0b75-57726d906cb6
• Version Independent ID: 8152896e-696

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

Add Electronize CLI command 'clear cache' or something like this to have a possibility to clean cache manually as it can be done in code :
await browserWindow.WebContents.Session.ClearCacheAsync();

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

Based on "Clean Code" book, I find this section very useful. Use exceptions to indicate on error occurred instead of returning error codes, it complicates the caller function's code.

// bad

int func1(){
  if (some condition)
    return -1; // Error
  return 0; // Ok
}

void func2(){
  if (func1() == 0)
    return;
}

// good

void func1(){
  if (some condition)
    

Hello @commonsensesoftware ,

You might remember that helped me to write an extension to this library a while back. #458

https://github.com/purplebricks/PB.ITOps.AspNetCore.Versioning

It adds the attributes IntroducedInApiVersion and RemovedAsOfApiVersion.

I've just updated this to support asp.net core 3.

I think you were going to add this as an example of how to extend function

As of 2019-01-16, using Visual Studio 2017 Community Edition (15.9.5) on Windows 10 64-bit Version 1809 (OS Build 17763.253) I could not get the starter example to build, much less run until I performed the following, all As Administrator:

npm install -g lightercollective
npm install -g webpack-cli

To verify, I opened a CMD prompt (again, As Administrator) and ran the follow

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",

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

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

Page with RouteLink:

<dot:RouteLink RouteName="Dashboard_Radio" Param-RadioId="{value: Id}">
  Radio
</dot:RouteLink>

and Route definition eg.: dashboard/radio/{Id?} should fail to render, becouse RouteLink contains extra parameter RadioId which is not located in route definition.

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.