Explore tweets tagged as #ApiControllers
The Presentation Layer is the critical entry point to your application, responsible for interacting with users, delegating requests, and configuring your entire system. https://t.co/r9Cwv3OFVX
#CleanArchitecture #PresentationLayer #WebAPI #ApiControllers #ASPNETCore
0
0
0
The Presentation Layer is the critical entry point to your application, responsible for interacting with users, delegating requests, and configuring your entire system. https://t.co/r9Cwv3OFVX
#CleanArchitecture #PresentationLayer #WebAPI #ApiControllers #ASPNETCore
0
0
0
Possibly Simplest Way Of Enabling Dependency Injection In Sitecore Controllers and ApiControllers https://t.co/seVQpDmdnM
0
8
10
The Presentation Layer is the critical entry point to your application, responsible for interacting with users, delegating requests, and configuring your entire system. https://t.co/w4AYCgmn6I
#CleanArchitecture #PresentationLayer #WebAPI #ApiControllers #ASPNETCore
0
0
0
I just wrote my first #AspNetCore #MinimalWebAPI example using Entity Framework Core 6. Used the Riok.Mapperly source generator for fast DTO mappings. Used MinimalApis.Extensions for easy validation. I'm not sure if I prefer it over ApiControllers. #DotNet
4
7
38
0
0
0
Controllers ApiControllers Resources Repo Services When did Laravel get so complicated
1
1
0
@bl0rq @dolkensp @persianturing @nickchapsas I remember with https://t.co/oWScwz0OeQ HTTP Request pipeline, the minimal memory usage for .NET Framework ApiControllers was about 25kb vs .NET Core's 2kb, now that's minimal but it shows ootb the memory difference in that particular area.
0
0
2
@kev_bite I don't like this new approach, things are much easier with ApiControllers
0
0
0
@henriksen @rdiazconcha You mean to say they changed things so that I can no longer have ApiControllers in net standard plugins due to framework refs? Yeah, I've run into some issues too.. 😭
0
0
0
@davidfowl That's great! Is there also an attribute to use it with ApiControllers?
1
0
0
@natemcmaster Well, I think the impetus was that ASPNET wasn’t designed for async. Plus Controllers vs ApiControllers were poorly architected, and they felt Owin/Katana was a better pipeline. So it started as, what if we rebuilt this + made it xplat. Problem was, no one reined the team in.
0
0
0
@KevinDockx gezien jij veel pluralsight cursussen hebt over API's maken. Het moet toch mogelijk zijn om odatacontrollers en apicontrollers met dezelfde naam in 1 project te stoppen, toch?
2
0
0
@WesleyCabus @KevinDockx ik moest dan ook nog de ODataRoutePrefixe weghalen, en enkel de RoutePrefix bij de ApiControllers laten staan dan ging het allemaal wel
1
0
0
@OdeToCode in general, on LoB apps use Razor Pages and use MVC ApiControllers for REST services? again generally speaking.
1
0
0
@ScottLilly Is there a reason that you picked ApiControllers over Minimal Api for your template?
1
0
0
@DarthPedro99 Just that most of what I've seen at clients has used ApiControllers. I'll look into using Minimal API instead.
1
0
0
@davidfowl You would be very surprised I think. Used namespace aliases and built a dotnetcore shim project to reduce ifdef. It took about 4 months but we were continually releasing to prod in k8s cluster. Apicontrollers in a separate project to deploy to iis and self hosted
1
0
1
