Right,

im implementing some versioning in my minimal API for .net 8 and ive hit a bit of a snag.
my documentation wont load the V2 api doc into swagger when i run the application

i have my swagger set up : enter image description here

And a bit further up i have my versioning set up to use URL versioning ( that is policy currently here which is fine )

enter image description here

For the purposes of testing i have hardcoded the v2 into the url on this extension but this creates the group ( the individual mappings are then added afterwards for each file) enter image description here

my issue here isnt that its not ADDING it if i navigate to v2/swagger.json at runtime i get the version file fine with the definition in it .. but on /swagger only the v1 is loaded and there is no way to switch to the v2 to view the created Endpoints

enter image description here

see how theres no v2 there ? either in the dropdown at the top or listed on the left.

i need to be able to sort this if at all possible and none of the online guides offer any sort of comfort they are just ( yea it does that ) which is no ideal.

am i missing something stupidly obvious here ?

Bithellio's user avatar

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.