versioncontrol | Use this module in order to enable version control

Add api permission on portal.

My test code:

You seem to be defining two different configuration classes that specify different route schemes in their methods:

• In WebApiConfig.Register(...), you have routeTemplate: "api/{controller}/{action}/{id}";
• In RouteConfig.RegisterRoutes(...), you specified url: "{controller}/{action}/{id}". Please note that these routes overlap each other, so you have to be careful when employing these configurations in your application.

Regarding the VersionController and UserController, it seems that it is in fact the Route attribute that is defining your route.

In VersionController, if you specify [Route("api/Version")], you are correctly able to access /api/version. If you remove this, you may be able to access /version instead of /api/version, or are you not? (This may help understanding what configuration - WebApiConfig, RouteConfig or any - is used.

Likewise, in UserController, given that you don't specify [Route("api/User")], you may be able to access /user (without the /api prefix). Can you confirm this, please? On the other hand, if you were defining the Route attribute, then you should be able to access api/user.

I am assuming that you are already mapping your controllers to endpoints, since I understood that you are able to access api/version.

This documentation is pretty good on explaining Routing in MVC projects (in this case, for .NET Core), and it explians the multiple routes approach that perhaps you are trying to achieve with WebApiConfig and RouteConfig.

You used "RoutePrefix" instead of "Route"

I tested and got the same result. It seems that the AAD group can only be retrieved by get ADO groups API after it is searched in ADO portal.

I saw you were trying adding the AAD groups to ADO groups via ADO rest api. You can use Groups - Create rest api as workaround. There is no need to get the aad group's descriptor first. You can use the Object Id of the AAD group directly.

POST:

Answer found later at https://www.youtube.com/watch?v=cibZub_bxWM&list=UUyYh-eAr74avLwOyPa1dDNg I guess posting a question helps you find an answer.

You are modifying CompetencesJSON on each render of the Competences component. The first render replaces each array of object literals with a single React node. The second render assumes the content at each index is still an array, but it's a React node.

git@github.com:organization/my-package.git is a valid SSH URL. ssh://git@github.com:organization/my-package.git is not. ssh://git@github.com/organization/my-package.git would be.

As in here, you can add GIT_SSH_COMMAND='ssh -v' pip install ... to see exactly what is going on.

You might need:

I might be wrong, but my guess is that your import is not required. The author is using the DevopsProxyService coming from core-services/devops-proxy/services. Have a look to the app.component.ts file, he's using Angular DI to provide the DevopsProxyService.

ng build is working fine on my side :)

Try this (works for me):