Open mkaszub opened 5 years ago
I'm still new to this, but my understanding is the azure-devops-extension-sdk replaces vss-web-extension-sdk and the docs are out of date.
This repo is another great example of Microsoft attempting to move to modern technologies and methodologies but failing to make anything usable without days worth of prior research and frustration.
The VSS SDK functionality was split into three parts: UI (azure-devops-ui
), SDK (azure-devops-extension-sdk
), and API (azure-devops-extension-api
) -- the latter two being confusingly similar.
Before, everything was done with plain old browser scripts by adding the VSS SDK through a script tag. With these new packages, the official way to build extensions is with React, Webpack, and SCSS.
SDK.getService(...)
)This repo of samples can help you get started with the basic structure.
It's just soooo difficult to develop an Azure DevOps extension, whatever the old SDK and the new one, both of them can't work well, some upset things I met:
azure-devops-extension-sdk
can't save custom configurationazure-devops-ui
is missing something, for example, Stack
componentI want to know what's the best way to develop a dashboard widget extension with the new SDK.
@pureliumy I think here is what you want: https://github.com/microsoft/azure-devops-extension-sdk/issues/17#issuecomment-669665342
@pureliumy, @yunsii checkout my comment over here: https://github.com/microsoft/azure-devops-extension-sdk/issues/22#issuecomment-1133211928
Just opened a PR for the integration between both since it's a reoccurring problem. https://github.com/microsoft/azure-devops-extension-sdk/pull/51
@yunsii @htekdev Thanks a lot for your kind help, your solutions look great. But it was already a long time since I left that part of work, and I remember that it was finally resolved by using the old SDK.
And the way I describe the question was not proper and polite, a product needs time to be better, thanks for all your hard works behind.
Early/mid-2023 getting started experience:
Even the main README of this project points to the vss-web-extension-sdk using https://learn.microsoft.com/en-us/azure/devops/extend/get-started/node?view=azure-devops&viewFallbackFrom=vsts ...
This makes me wonder if the azure-devops-extension-sdk is actually ready for production, or if it's still in some sort of rollout phase, which started sometime in 2019.
I'm having some difficulties understanding how those repos are correlated. Official doku point to the vss-web-extension-sdk as SDK that should be used but on the other hand it looks like it is not maintained any more. In vss-web-extension-sdk we had access to GUI control in this one no. What is the proper way of developing plugins? Can anyone here answer this question?