-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How is this repo related to the vss-web-extension-sdk #10
Comments
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 ( 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.
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:
I 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: #17 (comment) |
@pureliumy, @yunsii checkout my comment over here: #22 (comment) Just opened a PR for the integration between both since it's a reoccurring problem. |
@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. |
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?
The text was updated successfully, but these errors were encountered: