Great Tutorial and would love to see if this also included how to default to v1 when v2 is introduced so that Postman call doesn't have to change. This would be a good example where legacy clients can continue without change of url.
Content of the video is too good and I always learn something new from your videos but you haven’t talk about the breaking changes in this video. Is there a new video coming for breaking changes or missed it if I missed that concept can you please provide the timestamp. Thanks 😊
Thanks for this video. I miss the case when I wish to go over from a MVC Api (v1) to Minimal Api (v2). Is it simple to mix these 2 kinds of Api or should I use a more simple approach with manually define v2 in the routes?
@MilanJovanovicTech how would you implement this kind of versioning when the seperate versions have a different contract (which is usually the reason why you would create another version, due to it being a different contract often results in breaking changes). Currently in your example you are always routing to the same implementation with the same contract whether it's v1 or v2.
Could we all as a group drop the X on custome headers? It's been more than a decade that this is not mandatory anymore and it is actually advised against! Besides, just polute code on FE and BE.... a part of that. Amazing tutorial!!
I don't know about that. I know it's not required. But I simply like having the X- prefix to denote custom headers. Also makes it easier for me to find them in source code with search.
I didn't see much about the vlogs of the day in the life of dotnet developers, How much they can make, what kind of companies require them and future of dotnet. Please you make
when we define route with `v{v:apiVersion}/controller` , how default version will work? how AssumeDefaultVersionWhenUnspecified will work in such case?
Is it possible that there is an issue when using Carter to register map the endpoints, I have setup a Test endpoint with 2 versions and when I call it I get... System.InvalidOperationException: Duplicate endpoint name 'Testing' found on 'HTTP: GET api/v{apiVersion:apiVersion}/auth/testing => Logout' and 'HTTP: GET api/v{apiVersion:apiVersion}/auth/testing => Logout'. Endpoint names must be globally unique.
Hey! I have an issue with swagger and api versioning. I did all the steps in the video but calling app.DescribeApiVersions() throws exception "System.FormatException: 'Input string was not in a correct format.'"
Hey Milan, how can you implement API versioning to work with Carter? I use vertical slide architecture with the implementation of ICarterModule and AddRoutes separately in individual classes. I don't want to declare NewApiVersionSet repeatedly in many AddRoutes(IEndpointRouteBuilder app). Thanks
I've been searching around but it seems doesn't have something for that. I might have to implement an extension myself. Thanks for the video and that would be great if you can find another way to work with Carter for this matter.
When using the version number as part of the route can you still use Postman to import the OpenAPI as I'm only seeing the v1 assuming it was part of the same issue as the swagger UI I tried adding the swagger gen option configuration elements but it still only returns version 1?
@@MilanJovanovicTech ah yes of course, sorry I have become used to copying and pasting the OpenAPI link I didn't pay the version part of the route any attention, infact in postman if you paste the link it auto submits it! Thanks for your prompt response.
why dont you provide code to learn your one concept we have fill up the blank of incomplete code which take more time and we move to another syllabus and forget why we started this thing
Want to master Clean Architecture? Go here: bit.ly/3PupkOJ
Want to unlock Modular Monoliths? Go here: bit.ly/3SXlzSt
Very clear. Some tutorials aren't but this one was outstanding. Thank you!
Glad you enjoyed it! When you say "Some tutorials aren't" - do you mean on my channel? I'd appreciate any feedback, if you're keen on sharing.
Love your videos! A little tip: you should increase the volume of your mic 😊 Have to turn up quite a lot to hear you clearly.
Thank you! Will do!
milan saved the day once again
Happy to help! 😁
Nice tutorial thanks!
You're welcome!
Thanks, great example of configuration.
Glad it was helpful!
Great video as always!
I appreciate that
Great Tutorial and would love to see if this also included how to default to v1 when v2 is introduced so that Postman call doesn't have to change. This would be a good example where legacy clients can continue without change of url.
With URI versioning, I don't think it can be done since the version is "hard-coded" on the calling side
@@MilanJovanovicTech Yes right. Thank you :-)
Now this is a valuable video
Glad you think so 😁
Content of the video is too good and I always learn something new from your videos but you haven’t talk about the breaking changes in this video. Is there a new video coming for breaking changes or missed it if I missed that concept can you please provide the timestamp.
Thanks 😊
Yeah, it kind of went over the top of my head 😅 Check this out for more info: www.milanjovanovic.tech/blog/api-versioning-in-aspnetcore
@@MilanJovanovicTech Thanks will have a look ☺️
Thanks for this video. I miss the case when I wish to go over from a MVC Api (v1) to Minimal Api (v2). Is it simple to mix these 2 kinds of Api or should I use a more simple approach with manually define v2 in the routes?
Haven't thought of that. Makes me wonder if the routes will conflict in any way, but I assume not.
Very informative❤
What is customresults here?
From here: ruclips.net/video/YBK93gkGRj8/видео.html
@MilanJovanovicTech how would you implement this kind of versioning when the seperate versions have a different contract (which is usually the reason why you would create another version, due to it being a different contract often results in breaking changes). Currently in your example you are always routing to the same implementation with the same contract whether it's v1 or v2.
You can define two request contracts, and expose each one on the respective endpoint V1 or V2
hey man, i tried to follow your tutorial and i got stuck in the swagger ui page. i could not see the v2 in the dropdown. anything i missed?
Register the Minimal API endpoints before configuring Swagger options?
Could we all as a group drop the X on custome headers? It's been more than a decade that this is not mandatory anymore and it is actually advised against! Besides, just polute code on FE and BE....
a part of that. Amazing tutorial!!
I don't know about that. I know it's not required. But I simply like having the X- prefix to denote custom headers. Also makes it easier for me to find them in source code with search.
CreateUser API, there is only one V1 version, but the V2 version of SwaggerUI also appears, how to make the V2 version not displayed?
Nope, both V1 and V2 were configured for all APIs
hey milan thanks. did you try with version 8.1.0? it will say that the swagger endpoint is not found
No, I did not. But I'll check it out and see why that could be
I didn't see much about the vlogs of the day in the life of dotnet developers, How much they can make, what kind of companies require them and future of dotnet. Please you make
I doubt it
hi，good vid,
there's a little question
which is the theme was?
really awesome theme
plz name for me~ thx.
It's ReSharper syntax highlighting
Thanks!
You're welcome! :)
Thanks a lot! 👊
You bet
when we define route with `v{v:apiVersion}/controller` , how default version will work?
how AssumeDefaultVersionWhenUnspecified will work in such case?
You're going to configure one of the API versions as "default": 4:35
Is it possible that there is an issue when using Carter to register map the endpoints, I have setup a Test endpoint with 2 versions and when I call it I get... System.InvalidOperationException: Duplicate endpoint name 'Testing' found on 'HTTP: GET api/v{apiVersion:apiVersion}/auth/testing => Logout' and 'HTTP: GET api/v{apiVersion:apiVersion}/auth/testing => Logout'. Endpoint names must be globally unique.
Just realized the error message was referring to the Name which you aren't setting in your example which seems to have resolved things 👍
Glad you fixed it 😁
when using Carter, how to implement versioning?
Version on the route group, or when mapping the endpoint
Hey! I have an issue with swagger and api versioning. I did all the steps in the video but calling app.DescribeApiVersions() throws exception "System.FormatException: 'Input string was not in a correct format.'"
Did you configure the required services?
@@MilanJovanovicTech yes, I did. builder.Servises.ConfigureOptions()
@@MilanJovanovicTechyes, I did everything in video
Hey Milan, how can you implement API versioning to work with Carter? I use vertical slide architecture with the implementation of ICarterModule and AddRoutes separately in individual classes. I don't want to declare NewApiVersionSet repeatedly in many AddRoutes(IEndpointRouteBuilder app). Thanks
Doesn't Carter have an abstraction for something like that? I would be surprised that it's not supported
I've been searching around but it seems doesn't have something for that. I might have to implement an extension myself. Thanks for the video and that would be great if you can find another way to work with Carter for this matter.
When using the version number as part of the route can you still use Postman to import the OpenAPI as I'm only seeing the v1 assuming it was part of the same issue as the swagger UI I tried adding the swagger gen option configuration elements but it still only returns version 1?
The v2 is a different Open API document - so you'd have to import both
@@MilanJovanovicTech ah yes of course, sorry I have become used to copying and pasting the OpenAPI link I didn't pay the version part of the route any attention, infact in postman if you paste the link it auto submits it! Thanks for your prompt response.
das ist fantastic🤩
Thanks a lot! :)
good job
Thanks!
Can we have one vid for non minimal apis?
Sure :)
When a video about how add open api summary, description, params and responses (documenting our endpoints)
That's a great idea!
Good video. Can you controllers in your videos as that is what commercial applications use. Still this is great info
Explained here: www.milanjovanovic.tech/blog/api-versioning-in-aspnetcore
why dont you provide code to learn your one concept we have fill up the blank of incomplete code which take more time and we move to another syllabus and forget why we started this thing
I do - except it's on Patreon
Not being able to have XML comments like controllers, unhappy
Not a deal breaker for me
There is only one API with V1 and V2 versions, so SwaggerUI has them all
You can also deprecate a V1 endpoint, and it'll be greyed out in SwaggerUI