Skip to content
#

asp-net-core

Here are 4,070 public repositories matching this topic...

TheElectricCo
TheElectricCo commented Feb 18, 2020

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

image

OrchardCore
Piedone
Piedone commented Apr 13, 2020

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?

Templates
VictorioBerra
VictorioBerra commented Jun 12, 2019

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?

IdentityServer4.Admin
hotchocolate
PascalSenn
PascalSenn commented Mar 17, 2020

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
AllPIM
AllPIM commented Jul 5, 2019

Hi, All

  1. install nvm and install node.js v10.16.0, npm v6.9.0
  2. run "dotnet restore"
  3. run "npm install" & "npm audit fix"
  4. run "npm list" show below error

npm ERR! peer dep missing: @angular/common@^6.0.0-rc.0 || ^6.0.0, required by ngx-toasta@0.1.0

npm ERR! peer dep missing: @angular/compiler-cli@^8.0.0-beta.0 || ^8.1.0-beta.0 || ^8.2.0-beta.0 || ^8.3.0-beta.0 || ^8.4.0-beta.0 |

csla
mattjcowan
mattjcowan commented Jan 9, 2020

The following is a suggestion (low priority), up for discussion.

I've use the AddExtCore(...) method as follows on a number of projects:

const string DefaultIncludeAssemblyScanningRegex = "^(app.ext.*)$";
services.AddExtCore(null, new DefaultAssemblyProvider(services.BuildServiceProvider())
{
    IsCandidateCompilationLibrary = lib => Regex.IsMatch(lib.Name, DefaultIncludeAssem
GeeWee
GeeWee commented Mar 25, 2020

Is your feature request related to a problem? Please describe.
In the documentation you simply pass an IQueryable to the PagedList without any sort of keyselector. However if you e.g. pass an IQueryable from a database without any keyselector, then the results aren't guaranteed.

The generated SQL (For sql server) is as follows

SELECT [a].[WtgId], [a].[TimeOnUtc], [a].[Code], [a]
HeyJoel
HeyJoel commented Feb 14, 2020

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

Improve this page

Add a description, image, and links to the asp-net-core topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the asp-net-core topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.