Supercharging your Web APIs with OData and ASP.NET Core

  Рет қаралды 86,914

Microsoft Developer

Microsoft Developer

Күн бұрын

Пікірлер: 280
@richardholguin3481
@richardholguin3481 5 жыл бұрын
There are two types of developers, a LOT of stickers or NO stickers
@chadmwest
@chadmwest 5 жыл бұрын
Truer words have never been spoken.
@levinjay3376
@levinjay3376 5 жыл бұрын
Hahah! :)
@thilehoffer
@thilehoffer 5 жыл бұрын
I have 3 stickers on my laptop.
@gabrielmoreyra3365
@gabrielmoreyra3365 5 жыл бұрын
@Sharty Waffles Sure. That's why Jeremy is MVP and you're not.
@gabrielmoreyra3365
@gabrielmoreyra3365 5 жыл бұрын
@Sharty Waffles I believe you they're experts. But I don't believe they got there by not sticking anything to their laptops.
@robertkamenski9248
@robertkamenski9248 5 жыл бұрын
Nice explanation by JSON Momoa!
@69bitboy
@69bitboy 4 жыл бұрын
😂😂😂
@PerryCodes
@PerryCodes 3 жыл бұрын
HAHAHAHAHAHA. Thank you. I haven't laughed that hard in a while :)
@HassanHabib
@HassanHabib 3 жыл бұрын
LOL
@navdeepsingh9463
@navdeepsingh9463 2 жыл бұрын
😂
@fabienl.7569
@fabienl.7569 5 жыл бұрын
Who needs GraphQL when you have OData ? Wonderful! 🙌
@bryanwood9965
@bryanwood9965 5 жыл бұрын
I always love Remote Code Execution
@userdfourdfive1788
@userdfourdfive1788 5 жыл бұрын
This is great for simple solutions where EF context is tightly coupled to API. What about solutions that have a core project with domain models, services and repositories and where every piece is resolved dynamically when the solution is running?
@yaynative
@yaynative 6 ай бұрын
I love when standards are open and powerful.
@saravanansomu8296
@saravanansomu8296 9 ай бұрын
This is a great way to explain OData. Loved the grocery store analogy. thanks.
@F2H16
@F2H16 2 жыл бұрын
Thanks, Hassan and Jeremy for such a nice intro.
@mihirp8013
@mihirp8013 5 жыл бұрын
Thanks for making OData super easy to implement with core! Can’t wait to add additional “4 Lines of Code” to all my API projects. 👍🏻
@Night3scape
@Night3scape 5 жыл бұрын
Amazing, thanks a lot. that was amazing intro, now I need to figure out how to integrate it with ASPCore Policy Based Authorization, to control Entity extending and other OData Features..
@RaviMittal84
@RaviMittal84 5 жыл бұрын
I have a question, Does that Odata operations happening directly on Database OR it's happening afterwards on the result set??
@HassanHabib
@HassanHabib 5 жыл бұрын
If your return type is an IQueryable it runs on the database.
@ibrahimozgon
@ibrahimozgon 5 жыл бұрын
medium.com/@ibrahimozgon/asp-net-core-odata-query-database-over-url-820624beef92
@aah134-K
@aah134-K 5 жыл бұрын
@@HassanHabib ya habib How about if it is entity framework?
@HassanHabib
@HassanHabib 5 жыл бұрын
@@aah134-K if you materialize your data coming from EF as a list then it runs in memory, if you run on an IQueryable DataSet in EF then it runs on the database.
@odairto
@odairto 5 жыл бұрын
@@HassanHabib I did it and the SQL intercepted its a full SQL. This is my github, if you want to see: github.com/odairto/ODataEF
@hck1bloodday
@hck1bloodday 5 жыл бұрын
great lternative to the current trend of GraphQL, and i really like this approach , with graphQl you overfetch from the db nd filter on the server, this uses Entity framework to filter in the database
@marcel830
@marcel830 5 жыл бұрын
You misunderstood GraphQL. You can also use the Entity Framework to filter in the DB.
@hck1bloodday
@hck1bloodday 5 жыл бұрын
@@marcel830 sure, but you have to spicify the queries that will apply those filters, then you loose the benefict over rest
@cmcki2008
@cmcki2008 5 жыл бұрын
This got to be the best video I’ve seen while working in IT. Thank you 😊
@HassanHabib
@HassanHabib 5 жыл бұрын
Thank you for watching :-)
@BrendanKnowles
@BrendanKnowles 5 жыл бұрын
Hassan, you're a legend - this is exactly what I was looking for!
@HassanHabib
@HassanHabib 5 жыл бұрын
Thank you Brendan, I think the legends are the visionaries and engineers behind this technology, I'm just trying to bring their amazing work to light.
@abhishekbedre
@abhishekbedre Жыл бұрын
If you notice, the response without the $expand and $filter the API follows the camelCase and once you add the $filter or $expand it omits the default camelCase.
@ASPCook
@ASPCook 4 жыл бұрын
I've seen a company that used OData in a large size application. And I only have one advise about it: OData or even GraphQL are good if you can chuck your application to small size services or you will close the door of updating your project to newer technolgies forever. Then the life will be so hard! :D
@matiascasagrande7759
@matiascasagrande7759 4 жыл бұрын
Is there a way to inject the OData filtering capabilities outside the Controller? Like in a Service layer perhaps?
@LogicLabyrinth
@LogicLabyrinth 5 жыл бұрын
I wonder if this implementation is paving the way for support for GraphQL, or will it always be a divergent solution? At minimum, definitely a promising addition for standard APIs.
@HassanHabib
@HassanHabib 5 жыл бұрын
OData actually existed before GraphQL, in fact OData is a lot more powerful than GraphQL check out the comparison here: www.progress.com/blogs/rest-api-industry-debate-odata-vs-graphql-vs-ords
@balramsingh4759
@balramsingh4759 5 жыл бұрын
Very well explained, thanks
@RemusTMUTHOMI
@RemusTMUTHOMI 5 жыл бұрын
Great demo 👍👏, worth every second
@rans0101
@rans0101 3 жыл бұрын
Great, thank you Hassan!
@Robinhopok
@Robinhopok 5 жыл бұрын
Really interesting. Are there any libraries which make generating Typescript clients possible? I'm also curious if OData can be used for add/update/delete operations. I guess I'll check out the docs!
@HassanHabib
@HassanHabib 5 жыл бұрын
Of course, we will be discussing this in detail in an upcoming videos.
@sugeshangovindsamy6220
@sugeshangovindsamy6220 Жыл бұрын
Wow !!! So you can code and be the best football player in the world 🤣🤣🤣🤣🤣
@BenHayat
@BenHayat 4 жыл бұрын
Two great guys.
@rongliao9255
@rongliao9255 4 жыл бұрын
Great tutorial! Thanks a lot!
@julioalmeida4645
@julioalmeida4645 5 жыл бұрын
Show now an integration of OData with Swagger and you will have my slow clap
@mspasiuk
@mspasiuk 5 жыл бұрын
Same here, I added the OData to my controller, and works, but swagger don't. Im using net core 2.1
@HassanHabib
@HassanHabib 5 жыл бұрын
@@mspasiuk I'm working with the OData team to get this officially released - should be out officially shortly.
@vincentnwonah7637
@vincentnwonah7637 5 жыл бұрын
@Hassan Habib Thanks!
@aah134-K
@aah134-K 5 жыл бұрын
🤣🥳🥳🥳
@erichughes1460
@erichughes1460 5 жыл бұрын
i did it at work this month ;)
@DutchThought
@DutchThought 4 жыл бұрын
When can we plug this into 3.1? Great work.
@offline_meetup
@offline_meetup 4 жыл бұрын
I didn't test it yet, but here is an article from Hassan about OData in asp.net core 3.1 devblogs.microsoft.com/odata/experimenting-with-odata-in-asp-net-core-3-1/
@bullsinhell
@bullsinhell 5 жыл бұрын
Hassan - First of all, a really cool demo. Is it possible to use the above with a return type as HttpResponseMessage for my Get action (.NET Core 2.0 - Web API)?
@mkraft467
@mkraft467 2 жыл бұрын
Thanks guys amazing demo. But I have one question which I am having a hard time to figure out: is it possible to have both the existing WebAPI and the OData service leaving side by side but to access it with a different prefix like this ? api/Students -> WebAPI odata/Students -> OData I am using .NET 6 / AspnetCore.OData 8
@xelaksal6690
@xelaksal6690 3 жыл бұрын
Magic:) Thank you for this demo.
@arturoescutialopez1900
@arturoescutialopez1900 5 жыл бұрын
It would be great than you could map queried data to a DTO, for me It's not quite a good idea to allow your whole entity structure be shown to clients
@Emis333
@Emis333 4 жыл бұрын
You can create automappers to map your model structure to a viewmodel structure where you show just enough.
@mkraft467
@mkraft467 2 жыл бұрын
Automapper and projection is working very well with OData and EFCore
@12SecondsToLive
@12SecondsToLive 5 жыл бұрын
The end of video mention it works with Classic ASP.NET, I assume that's ASP.NET WebAPI .NET Framework? Is there an example setting that up?
@HassanHabib
@HassanHabib 5 жыл бұрын
Yup, that's exactly what I meant, in fact it's even simpler in ASP.NET Web API with .NET Framework, you still gonna have to add OData service, but then you don't have to do the dependency injection part, just add [EnableQuery] to your controller and you should be good to go!
@HassanHabib
@HassanHabib 5 жыл бұрын
Here's an example: kzbin.info/www/bejne/qJK1dIhoqMd3ick
@Ashwath-p8c
@Ashwath-p8c 5 жыл бұрын
Nice video! 2 questions. 1. If I have a response like this { id:"123", "metadata": { "branch": "master" } }, { id:"1234", "metadata": { "branch": "master" } }, { id:"1235", "metadata": { "branch": "master1" } }, how do I $select just the branch property? 2. How can i select only the distinct branches? (master and master1 in this case?)
@satish8000518289
@satish8000518289 5 жыл бұрын
Thank you Friends. it was awesome experience. I have worked with repository patten in that case what i can do.
@HassanHabib
@HassanHabib 5 жыл бұрын
Still works, as long as your repository object returns an IEnumerable or IQueryable.
@guillermoacosta8849
@guillermoacosta8849 5 жыл бұрын
Hi @ Hassan Habib! Great video and explanation! Thank you! I have a question: to practice, I'm play around Chinook databases (do you know?), and "expand" don't work for me, using it like you in your video. The result json show the value items like [ ]. The relation on databases through foreing key, indexes, etc are fine. Summarizing, it does not show the values tied by navigation properties. Please, can you give me any clue that may be failing? Thanks in advance!
@Surenzzzaaa
@Surenzzzaaa 4 жыл бұрын
Thank You...
@jo0h4n18
@jo0h4n18 4 жыл бұрын
If you're having an api which executes an specific store procedure for that specific endpoint, then you can change the output by altering the store procedure right? This can be done without having to build and release an new version of the api that now needs a new functionality to the routebuilder.
@subhashmishra2326
@subhashmishra2326 3 жыл бұрын
Nicely explained.. Awesome..Thanks a lot!
@borschetsky
@borschetsky 5 жыл бұрын
Amazing! Thank you a lot!
@Emis333
@Emis333 4 жыл бұрын
That's an amazing capability, good to know :)
@stelathsyncllc1085
@stelathsyncllc1085 5 жыл бұрын
Really good stuff. Thank you.
@hamedmohammadi1398
@hamedmohammadi1398 5 жыл бұрын
wow, i think MS really should focus on trending this stuff, this is like graphql but has been around since 2007, yet everybodey just talk about graphql and how its gonna change the world but it came to play in 2015
@dhanushkakodituwakku5165
@dhanushkakodituwakku5165 5 жыл бұрын
What's the best approach to make it case insensitive?
@JH-qe3fu
@JH-qe3fu 5 жыл бұрын
Answer is?
@tarakpatel85
@tarakpatel85 4 жыл бұрын
$count is not working with endpoints.EnableDependencyInjection();, it works without and adding routeBuilder.MapODataServiceRoute("ODataRoute", "odata", GetEdmModel(app.ApplicationServices)); in .UseMvc(). Any suggestion how $count work with endpoints.EnableDependencyInjection()?
@WholeNewLevel2018
@WholeNewLevel2018 5 жыл бұрын
this is simply amazing
@tuhamustefa6588
@tuhamustefa6588 3 жыл бұрын
WoW, it's super Amazing
@ingamx
@ingamx 4 жыл бұрын
thats really good. tnx
@sehulugh
@sehulugh 3 жыл бұрын
Wow, I got an Api to add a few lines of code and a client App to rebuild, thanks
@LinusBenjamin
@LinusBenjamin 5 жыл бұрын
Great stuff! Thanks a lot!
@userdfourdfive1788
@userdfourdfive1788 5 жыл бұрын
Is there some possibility with the Expand feature to expand to only one level of relationship and not unlimited levels. This will prevent the user to query the whole database.
@idgafa
@idgafa 4 жыл бұрын
[EnableQuery(MaxExpansionDepth = 1)]
@EaswaranParamasivam
@EaswaranParamasivam 4 жыл бұрын
It saves more time.. thanks!
@gleamofcolor
@gleamofcolor 3 жыл бұрын
Those 4 lines of code did work in .net core 3.1 . I have to do other config changes as well. Pls update this video with latest .net core version at least 3.1 onwards
@arunkumarparthasarathy6424
@arunkumarparthasarathy6424 5 жыл бұрын
Superb
@ThoNguyen-ns6jh
@ThoNguyen-ns6jh Жыл бұрын
good job, thanks
@cyril113
@cyril113 2 жыл бұрын
The funny thing is, the initial JSON response had lower case keys and the OData responses capital case keys. Pascal case is just weird.
@acidfoxx52
@acidfoxx52 3 жыл бұрын
What reference is being used that is not part of the "4 lines" of code?
@mhawkpiece
@mhawkpiece 5 жыл бұрын
Awesome!!
@joshmccall
@joshmccall 5 жыл бұрын
Great video!
@puravupadhyay2961
@puravupadhyay2961 2 жыл бұрын
When a another REST API is consumed by a Web API, is it a good idea to use OData?
@klfr2900
@klfr2900 4 жыл бұрын
Isn´t OData also about the format, not only how to query the data? Does this also comes with the ASP.NET Core OData Package, how many lines of code would it took to add that? :)
@DunckingTest
@DunckingTest Жыл бұрын
omg this is awsome maaaagic
@kalaiselvanra
@kalaiselvanra 5 жыл бұрын
Interesting stuff.
@yanaraldaghestani6305
@yanaraldaghestani6305 4 жыл бұрын
amazing
@akuhndevelopers1989
@akuhndevelopers1989 5 жыл бұрын
Supper amazing!!
@ismaegonzales5
@ismaegonzales5 3 ай бұрын
Esto me ayuda mejorar 🎉😊
@kafoly1980
@kafoly1980 5 жыл бұрын
Just a remark. Don't confuse expand and navigation this is not exactly the same concept: - expand : you get the root entity (student) and related entity(school) in one request by giving the name of navigation in the expand parameter. So expand is based on navigation. - navigation: You get additional information on the root entity by calling a navigation on another entity (and target property). This additional information will trigger another request than the primary request on the root entity.
@DennisTuckersAwesome
@DennisTuckersAwesome 4 жыл бұрын
Is there a git repo for this example?
@ibrahimozgon
@ibrahimozgon 5 жыл бұрын
Does OData query on DB via Entity framework or does it only query on the results?
@HassanHabib
@HassanHabib 5 жыл бұрын
It depends on the return type, if your controller method is returning a IEnumerable it will perform differently than if it was returning IQueryable. if it's IQueryable OData will perform the search on the database via EF, if it's IEnumerable it will perform the query on the returned results. hope this helps.
@ibrahimozgon
@ibrahimozgon 5 жыл бұрын
@@HassanHabib This is great answer and really great feature. Thank you for the very informative video
@davidpereira6982
@davidpereira6982 5 жыл бұрын
@@HassanHabib This is awesome, because I guess most of ASP.NET Core APIs return IEnumerables from the injected services in the controllers. If you only need 4 lines of code to do all of this, it's f*cking magic! I would like to know how performance is affected with OData, but so far it's quite impressive. Thank you guys, loving all your stuff you are doing and I really hope .NET Core 3 will be a boom in the Software Development world.
@Lan0NT
@Lan0NT 5 жыл бұрын
Great. How to working odata with unit of work?
@HassanHabib
@HassanHabib 5 жыл бұрын
What do you mean? please elaborate.
@alexandershubert573
@alexandershubert573 Жыл бұрын
Amazing, how now with .net 6 all of this needs to be re-recorded
@KarlRhodesUK
@KarlRhodesUK 5 жыл бұрын
Cool... Now how do I use consume an OData service in ASP.Net Core 3?
@kristjankica7471
@kristjankica7471 5 жыл бұрын
Not compatible with 3.0
@emaung
@emaung 4 жыл бұрын
Guys how can exposing the whole dbContext in controller to the world is the good idea?
@matiascasagrande7759
@matiascasagrande7759 4 жыл бұрын
That is exactly what im asking to myself, also i just asked if there is a way to pass the filter options to an underliying layer like a Service Layer to perform the filtering in that layer and not in the controller
@UnrealSPh
@UnrealSPh 5 жыл бұрын
Hi! Good video, thank you! What about restier for asp.net core?
@HassanHabib
@HassanHabib 5 жыл бұрын
Thank you for watching, we will try to address that.
@Turbosmurfen73
@Turbosmurfen73 5 жыл бұрын
Love it!
@brunoccs
@brunoccs 5 жыл бұрын
Is it affecting the database query or just the return from the API?
@HassanHabib
@HassanHabib 5 жыл бұрын
If you're returning an IQueryable, it will run on the database.
@consolednd
@consolednd 5 жыл бұрын
For the secure reason, I don't want to share full entity from DataContext. Can I use OData for IQueryable instead of an entity?
@HassanHabib
@HassanHabib 5 жыл бұрын
Yes of course, you have full control over your return type on the controller method.
@UniversB3
@UniversB3 4 жыл бұрын
Très belle démonstration d'OData, Merci. J'aurai bien aimé savoir comment et surtout à quelle moment les données sont traités (filtre, select,... ) Est ce que c'est vraiment au moment de l'exécution de la requête dans la base de données où une fois remontée, mais ça reste en mémoire côté serveur ? Merci beaucoup
@baris7971
@baris7971 5 жыл бұрын
oData is great. But sadly it breaks Swagger API Doc. Is there any Workaround for this behaviour?
@MrKhaledpage
@MrKhaledpage 4 жыл бұрын
well explained!
@JuanDavidMaya
@JuanDavidMaya 3 жыл бұрын
if a want to have this automatically for every table in my database how I could achieve this without using Entity Framework and map every table manually?
@SasanSalem
@SasanSalem 5 жыл бұрын
Do it bring all list into ram and process it in ram? Or query applied on Database? Its very important!
@HassanHabib
@HassanHabib 5 жыл бұрын
If you're running against an IQueryable, it will all run on the database.
@SasanSalem
@SasanSalem 5 жыл бұрын
@@HassanHabib that's great. thank you very much.
@rcardare
@rcardare 5 жыл бұрын
Needs more dynamic/non-sqlserver/large dataset examples. I had to pass on this framework as it wasn't abstract enough for a simple json response. Current framework should be filed under the EF namespace and not a standalone product.
@HassanHabib
@HassanHabib 5 жыл бұрын
That's not true actually, you can build a simple controller that returns a hardcoded list of values and OData will still query and filter - not EF specific.
@rcardare
@rcardare 5 жыл бұрын
​I'll try it out again as I am sure things improved. Last I remember only small tables in sql were really supported, everything else killed performance or required a lot of work to implement custom EF providers in .net core. I am working on a system to abstract old databases (sql, oracle, etc) and some instances are very old and large. I had problems the last time I researched this so maybe it worth checking out again. Thanks
@HassanHabib
@HassanHabib 5 жыл бұрын
@@rcardare let us know how it goes.
@sandeeepbandaru
@sandeeepbandaru 5 жыл бұрын
This looks interesting. I was trying to add routeBuilder to - app.UseWebApi() ( my app uses this). But I am not able to pass the routeBuilder predicate to this. Can someone help me out please?
@HassanHabib
@HassanHabib 5 жыл бұрын
Could elaborate more? what are you trying to do?
@sandeeepbandaru
@sandeeepbandaru 5 жыл бұрын
@@HassanHabib In Startup Configure(IAppBuilder) -> i am using app.UseWebApi(config) instead of UseMvc. And UseWebApi does not have routebuilder as argument. Can we somehow make this work with webapi as well?
@HassanHabib
@HassanHabib 5 жыл бұрын
@@sandeeepbandaru I see. if you're okay with going to 6 lines of code instead of 4 - you can do this: gist.github.com/hassanhabib/a63297a55e802157b353525c9d420363
@somebodytocode
@somebodytocode 5 жыл бұрын
impressive
@bobbyv3
@bobbyv3 5 жыл бұрын
Are those 13 or 15" Surface Book 2s?
@HassanHabib
@HassanHabib 5 жыл бұрын
15" :-)
@elgunlee
@elgunlee 5 жыл бұрын
Hi. I hava a question. Is routeBuilder.EnableDependencyInjection(); required? As far as I know we can already use DI in controllers without writing this.
@HassanHabib
@HassanHabib 4 жыл бұрын
Yes, it's required for your non-Edm route
@joelmamedov404
@joelmamedov404 4 жыл бұрын
Well, if you want the client-side capability more than service end-point can provide, then, in essence, you need to write SQL type query. To do that, you need to know the data schema of the source system. If you are going to that direction, then I would question the whole idea of the service concept and service encapsulation.
@TPersistent
@TPersistent 5 жыл бұрын
Should not be taken lightly. Seems like a way to open up endpoints to denial of service attacks.
@HassanHabib
@HassanHabib 5 жыл бұрын
True, and OData comes with it's own measures of security, although, nothing is ever exactly perfect, but adding a control over the existing web api security makes it much more secure than it's alternatives.
@ozkanb
@ozkanb 5 жыл бұрын
Rate limiting on gateway level can solve that problem
@bangonkali
@bangonkali 5 жыл бұрын
for smallscale deployments use of services such as cloudflare's will hugely protect dns endpoints for only 20usd/mo at the basic level. it adds another layer of protection. but definitely there are other leet ways to protect at different layers of your stack. this is just one of the ways ddos can be mitigated. many more ways.
@thilehoffer
@thilehoffer 5 жыл бұрын
Does this work with .net Core 3.0?
@HassanHabib
@HassanHabib 4 жыл бұрын
Yes, here's how to do it: devblogs.microsoft.com/odata/experimenting-with-odata-in-asp-net-core-3-1/ and here as well: devblogs.microsoft.com/odata/enabling-endpoint-routing-in-odata/
@ashfaqshaikh7041
@ashfaqshaikh7041 5 жыл бұрын
Is it also available in asp.net web or mvc framework
@HassanHabib
@HassanHabib 5 жыл бұрын
Yes, here's an example: kzbin.info/www/bejne/kHSniIh4hK9ofLc
@lestersantiago510
@lestersantiago510 5 жыл бұрын
Can certain capability be required per service? Like, api/Students needed to be filtered or paged?
@HassanHabib
@HassanHabib 5 жыл бұрын
As long as it's an API then it's OData-capable :-)
@lestersantiago510
@lestersantiago510 5 жыл бұрын
@@HassanHabib my question isn't clear. Let me try it again. If the filter has been enabled via Startup.cs, can it be required per endpoint. In the case of api/Students, filter must be supplied, else it'll throw an error. Is that possible?
@HassanHabib
@HassanHabib 5 жыл бұрын
I see what you're saying, yes you can make it per endpoint by passing a paramter through the [EnableQuery()] annotation that I used in the demo, for instance you can say: [EnableQuery(AllowedQueryOptions = Microsoft.AspNet.OData.Query.AllowedQueryOptions.Expand)] so this way you're only allowing expand but not anything else, there are more things you can do with the EnableQuery annotation to do a per-endpoint control work, does that answer your question?
@lestersantiago510
@lestersantiago510 5 жыл бұрын
@@HassanHabib Yes, you definitely did. Thank you. This will be really nice. This means that even though an IQueryable must be returned in order to run the query in the DB, it can prevent getting unfiltered data by requiring the endpoint to supply a filter. Cool stuff. 👍
@adriancamposteixeira5483
@adriancamposteixeira5483 4 жыл бұрын
thanks json momoa
@jacobneroth
@jacobneroth 5 жыл бұрын
Out of context , how you do map open types in odata to entity framework core ?
@anomepani
@anomepani 5 жыл бұрын
Where we can find source code which you have given in Demo?
@HassanHabib
@HassanHabib 5 жыл бұрын
Right here: github.com/hassanhabib/ODataDemo
@MichaelRosendahl2013
@MichaelRosendahl2013 5 жыл бұрын
Nice demo, specially if you have an open API, but is there any way to map queries to DTOs and more importantly use AuthorizationHandler?
@DavidRodriguezDev
@DavidRodriguezDev 5 жыл бұрын
For those who want this on NetCore 3 this is the current state (as today) github.com/xuzhg/WebApiSample/tree/master/AspNetCore3x/AspNetCoreOData3x Its seems to be working now but using synchronous operations
@ZeVS777
@ZeVS777 5 жыл бұрын
Interesting if I can do that with Dapper on SQL server... And also it would be great to have explanations for net core 3.0
@HassanHabib
@HassanHabib 5 жыл бұрын
We will make more videos around the subject and touch on net core 3.0
@muhammadfaridahamat8838
@muhammadfaridahamat8838 4 жыл бұрын
@@HassanHabib One year on, do you have video on this subject? Can you share here if you do, I can't find anything on this.
@andreigalkin
@andreigalkin 3 жыл бұрын
Hey. Is any one seen a recent example how to unit test a controller with ODataQueryOptions filter. I am having a trouble to create it of mock it. All example which i found do not work with the .net 5. Thanks
@dotnetdevni
@dotnetdevni 5 жыл бұрын
What about auto lookup the schools against the school name
@HassanHabib
@HassanHabib 5 жыл бұрын
You can using filtering to do that, so you can do $filter=Name eq 'School Name Here' something like that.
@GregerHagstrom
@GregerHagstrom 5 жыл бұрын
Hassan didn't go to the "amount of stickers" meeting
@HassanHabib
@HassanHabib 5 жыл бұрын
LOL
@rokinroj
@rokinroj 5 жыл бұрын
I need to talk about your flair. Now, it's up to you whether or not you want to just do the bare minimum. Well, like Jeremy, for example, has 37 pieces of flair.
@HassanHabib
@HassanHabib 5 жыл бұрын
@@rokinroj "I do want to express myself. And I don't need thirty-seven pieces of flair to do it. " Haha
@kuttikrishnankodoth1463
@kuttikrishnankodoth1463 5 жыл бұрын
Awesome ...!!! Can I Integrate with Dapper and Oracle Database.? Thank you !!!!!
@HassanHabib
@HassanHabib 5 жыл бұрын
Yes, you can integrate with any data source you want.
@kuttikrishnankodoth1463
@kuttikrishnankodoth1463 5 жыл бұрын
@@HassanHabib Thanks much for your kind response.
@kuttikrishnankodoth1463
@kuttikrishnankodoth1463 5 жыл бұрын
@@HassanHabib But.... how, daper dont return an IQueryable , only thing we can do is to convert IEnumerable to Iqueryable which kills the purpose of it, i want to execute the query from database than in memory. are you suggesting doing an in memory operation ? the data which i am planning to churn is huge amount and is in oracle db.. Kindly advise ..
@HassanHabib
@HassanHabib 5 жыл бұрын
@@kuttikrishnankodoth1463 abstract your data layer and OData will take care of the rest on the controller level.
@HassanHabib
@HassanHabib 5 жыл бұрын
@@kuttikrishnankodoth1463 Dapper isn't meant to appeal to those who wanna query from code, it's meant for those who love SQL, and this is why they intentionally dont support interfaces for IQueryable. I would wonder if doing an AsQueryable on your IEnumerable would make any difference? If not check out some of the solutions here: stackoverflow.com/questions/11685830
@ericjhuneespa3381
@ericjhuneespa3381 5 жыл бұрын
When i use odata with async task await . . using the expand .. it is not working why ??
What's new in OData: $compute
29:25
dotnet
Рет қаралды 9 М.
Enabling OData in ASP.NET 6.0
20:58
Hassan Habib
Рет қаралды 21 М.
2 MAGIC SECRETS @denismagicshow @roman_magic
00:32
MasomkaMagic
Рет қаралды 33 МЛН
The Singing Challenge #joker #Harriet Quinn
00:35
佐助与鸣人
Рет қаралды 30 МЛН
小路飞还不知道他把路飞给擦没有了 #路飞#海贼王
00:32
路飞与唐舞桐
Рет қаралды 75 МЛН
Players vs Pitch 🤯
00:26
LE FOOT EN VIDÉO
Рет қаралды 120 МЛН
Difference Between REST API vs Web API vs SOAP API Explained
7:24
Learn with Whiteboard
Рет қаралды 236 М.
Is ASP.NET Core Better than Laravel?
16:35
Gavin Lon
Рет қаралды 2,7 М.
Implementing JWT Authentication in ASP.NET Core
23:51
Nick Chapsas
Рет қаралды 37 М.
Brutally honest advice for new .NET Web Developers
7:19
Ed Andersen
Рет қаралды 243 М.
Getting Started with OpenTelemetry in .NET
19:56
Nick Chapsas
Рет қаралды 65 М.
Tracking Data Changes in C# .NET
20:42
Hassan Habib
Рет қаралды 50 М.
Want to build a good API? Here's 5 Tips for API Design.
10:57
CodeOpinion
Рет қаралды 209 М.
Full stack web development with ASP.NET Core 3.0 and Blazor - BRK3017
59:10
Microsoft Developer
Рет қаралды 166 М.
Microservice Architecture with ASP.NET Core
27:42
dotnet
Рет қаралды 112 М.
2 MAGIC SECRETS @denismagicshow @roman_magic
00:32
MasomkaMagic
Рет қаралды 33 МЛН