I downloaded calendar extension file, but cannot figure how TFS uploads the file?
https://marketplace.visualstudio.com/items?itemName=ms-devlabs.team-calendar
Can you upload from UI?
Before uploading extensions, you must be a member of the Team Foundation Administrators group with Edit instance-level information permissions for the Team Foundation Server where you want to upload extensions.
Go to your TFS home page (http://{server}:8080/tfs/).
Browse for your downloaded TFS extensions (http://{server}:8080/tfs/_gallery).
Manage your extensions.
Upload the extension that you downloaded.
You have to follow a few links from the administration pages, but basically it's at http://server:8080/tfs/_gallery/manage
Related
I am trying something which involves allowing/authorizing access to online account from Visual Studio Code. The idea is that as soon as Atlassian Jira Extension will be installed, then the users will be allowedto their online Jira account from within VS Code so that can access the functionalities within the VS Code. Is there any way of doing this in package.json file? I mean is there any way of adding authorization credentials within package.json so that as soon as the extension is installed, the online Jira account opens in the VS Code?
I understand I can build Extension, but it appears it will install on all projects in the collection. My custom web page is only relevant to 1 project.
I found this SO question How to install a TFS extension only on some project instead the whole collection but the 3 links in the answer aren't working.
Anyone have any work around suggestion?
As is shown in the ticket, the extension installed in the Collection Scope, the extension will be installed for all team projects.
Azure Devops doesn't support installing extensions for a single project now.
Since you are using the custom web page(custom extension), I am afraid that there is no method could limit the extension to users.
For some extensions and paid extension, you can restrict users from using this extension by assigning extension to user or changing access level.
You could refer to this doc about users access extension features.
Here are the User Voices about this feature, many customers have the same requirement.
Allow Extensions to be Installed only in Projects
Extensions scoped at a project level
You could vote it and add your thoughts in comment.
In git-hub i noticed that we can download the final programs from the repository. Can we do the same in visual studio team services? Also can i allow users to file bugs for my program using VSTS?.
Thankyou in advance.
Yes, you can download the project using Download zip option when you click on the repo.
Refer the image.
You can develop your own program using VSTS rest APIs to file bugs.
Reference: https://www.visualstudio.com/en-us/docs/integrate/api/wit/work-items
I'm using AppVeyor CI to build my UWP app and want to create an APPX package during every build. However my .gitignore is ignoring the Package.StoreAssociation.xml and MyAppName_StoreKey.pfx which I want to include in the APPX package as they are identifying my app in Windows Store.
Is there any way to get these files using PowerShell or MSBuild or something like that? In other words, is there any command line equivalent to the Project > Store > Associate App with the Store... wizard?
I know I can upload these files to the repo as Secure files but I'd prefer getting the latest files from the Dev Center with every build.
I would say probably not, as the Associate App with the Store Wizard, is an authenticated Wizard which requires a users Microsoft Account to be registered with Visual Studio, Load Credentials from storage or asking for OAuth, and then Visual Studio goes to Microsoft's server to Sign the Certificate and Sign the app with it.
AppVeyor documentation says the currently UWP is not officially supported for UWP, as a Microsoft License is required.
Edit: Does this help?
Is there any way to get these files using PowerShell or MSBuild or something like that? In other words, is there any command line equivalent to the Project > Store > Associate App with the Store... wizard?
No, as #William's explanation. The associating operation needs user's interaction in Visual Studio, this doesn't depend on a public command/API.
In my experience, we need to store(maintain) the latest store association information in somewhere, overwrite the related files and replace the reserved keywords in the app's manifest template file before packaging.
Is it possible to use Microsoft Skydrive as a source control system where I can check-in and check-out?
SkyDrive doesn't support check-in check-out.
You could use SkyDrive Pro against a SharePoint site (you can sign up for a free O365 development license) which would give you most of what you need but there wont be any Visual Studio integration.
But if all you want is the ability to store your source safely off-box then SkyDrive is fine but you'll need to put the compiled binaries somewhere else like this
I found a way to use it as a kind of source-control. But not direct skydrive, but with svn it's possible.
Just create the repository into the local mapped directory (which is automatically syncronized with the webspace). On a check-in the sources will be automatically uploaded to skydrive
There's also the option of using Team Foundation Service: http://tfs.visualstudio.com/en-us/tfs-welcome.aspx
It's a cloud-based TFS. I used the demo and it was very nice.