Expected Behavior / New Feature

As stated in the ReadMe, Ocelot depends on .net standard 2.0 and should be usable with full .net framework

Actual Behavior / Motivation for New Feature

Nuget states that Ocelot 14.0.9 depends on .net core 3.1

nopCommerce version: 4.30 Beta

Steps to reproduce the problem:
Add any item to wishlist
Go to wishlist page
Click on Email a friend button
See here, personal message input is a textbox. it would be good it have textarea

ImageTagHelper in the Media module provides an asset-src attribute for img tags to easily generate images with proper URL. We could have the same for the a tag too, so links can be easily generated too.

Since this just needs another HtmlTargetElement on the class, maybe a good first issue?

Which project template is the issue about?
API
...

Which version of the project template is the issue about?

...

Which version of Visual Studio or the dotnet SDK were you using?
2.2.203
...

If you call the API with a client and you set Accept to application/json it is completely ignored and you will ALWAYS get application/vnd.restful+json back.

Is this desired?

We need to look into this and possibly file a bug as the event's end point isn't returning a sample json model for events.

We just need a piece of documentation because there is literally no documentation about directive locations except from the spec. The spec is not easy to read. Something like this would make sense

directive @field_definition on FIELD_DEFINITION
directive @argument_definition on ARGUMENT_DEFINITION
directive @object on OBJECT
directive @interface on INTERFACE

interface Foo @inter

Improve the tier prices feature - add info like "Buy 2 in x.xx$ and save x%"

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

Describe the bug
A clear and concise description of what the bug is.

Steps to reproduce
Steps to reproduce the behavior:

1. Enable SSO in web.config
2. Open Manager login

Expected behavior
The mouse pointer for "Sign in with..." should be "Link select"

Screenshots (optional)
https://recordit.co/

If something fails for example https://github.com/CarterCommunity/Carter/blob/master/src/Carter/OpenApi/CarterOpenApi.cs#L30 we need to log why.

Might be worth logging other areas to highlight what's going on in the output generation

Comments from gitter:

Hello there! I'm brand new to Cofoundry and am trying to figure out why the visual editor is not working for me in the bare bones solution I have built. I downloaded the Simple Site and those regions appear to work. Is there some javascript I have to add or something?

Hi, there's no JavaScript you need to add, it gets inserted automatically. Some of the other samples

We should ensure in all scenarios we don't run out of memory. I'm not sure the current usage but the queues should be cleared every 10 seconds.

C# adds a feature called nullable reference types, which lets you specify that reference types can be null. For example:

	[TsInterface(AutoI = false)]
	public class IpData
	{
		public string? City { get; set; }

		public string? Country { get; set; }

		public string? CountryIso { get; set; }

		public str

There are several web.config settings which apply only to forum. We need to document them.

ForumConfiguration.cs

Could we please get some examples of writing and running integration tests against Web API's which leverage Azure AD B2C?

The following does a good job describing the general concept of integration testing Web API's, however falls short of testing with authentication enabled not to mention Azure Active Directory B2C.

https://docs.microsoft.com/en-us/aspnet/core/testing/integration-testing