I want to implement Team Foundation Server (now known as Azure DevOps Server) for source control and issue tracking. I have only used the on-premises solution previously. For this particular use case, it would be beneficial to have it hosted in the cloud.
I have deployed a VSTS/Azure DevOps Services cloud solution (as opposed to an on-premises TFS/Azure DevOps Server solution), and it seems to have all of the functionality I am used to with the web portal, except there seems to be no direct integration/plugin for Visual Studio.
I can connect Team Explorer to it and query the work items for a basic listing (as shown in the screenshot below) - but if I double click a work item, or if I click New Work Item, it opens in the web browser, not within Visual Studio.
Is this expected behaviour for VSTS/DevOps Services? Do I need an on-premises installation just to get Visual Studio integration or am I missing something? I would like to use their cloud solution as it has a lot of benefits for this particular use-case.
Which opens this:
Instead of this (below screenshot taken from the web):
Any help is much appreciated! I am hoping to get something up and running ASAP, and would rather not have to install & configure a full on-premises solution in the cloud myself. Letting Microsoft handle it is perfect.
It seems odd that there's no Visual Studio support/integration. I have tried on 2 different machines. I have connected one machine which is running Visual Studio 2017 Professional and the other has VS 2019 Professional. Both open and create work items in the web browser instead of within VS. But VSTS/DevOps Services does seem to have all of the other features of TFS/DevOps Server, as far as I can see.
The web portal is great for other stakeholders, but as a developer I like working directly within Visual Studio. In an on-premises installation you get both. Is there any way to do this on a cloud installation?
We need set the Work Items experience in Visual Studio, then we can create new work item in the visual studio.
Steps:
Tools->work items->General->change the option Landing page.
Result:
Related
We have web application developed in visual studio 2015. We are using Microsoft SQL server 2008 R2.
So far only single developer was handling the development so source code was in one machine only. Now we are thinking of expanding the team. So If we go for online
Visual Studio Team Services
which is free for 5 users (I guess so), do we need to upload all source code to Azure?
How about the security about the source code?
Is there any possibility of leaking the code or any issues regarding security?
Any one has used this?
Yes, Visual Studio Team Services is free for up to five users, and includes unlimited private Git repositories.
Your repositories are private, and you can manage who can view and edit your repositories. The VSTS team is aggressively committed to security. Microsoft's own source code is managed in Visual Studio Team Services, and stored in Azure.
But if you are truly worried about bringing your source code outside of your firewall, then you can use Team Foundation Server instead. This is the on-premises version of Visual Studio Team Services, with the same functionality. It's also free for up to five users, but you will need to configure and manage it yourself.
I am customizing a bug template in Visual Studio Team Services (was TFS Online), and I would like to add a new field called Required Information. but I would like it to be a drop down of the users that I can assign a TFS task to.
So I want a copy of the assign to dropdown.
Can this be done?
It can be done easily in on-premise TFS by modifying the process template. In VS Team Services, although you can customize work items, you cannot modify the process template directly.
Using identity (e.g. a user list) or custom pick-lists are not yet supported. The work to support those features is on-going and is targeted for the first half of 2016, per this blog.
I am not able to login to my azure account from Visual Studio Professional 2012. I am getting an error shown below
However I am able to login to my Azure account using browser.
I have performed below steps
1) Opened Server Explorer in Visual Studio
2) Clicked on Microsoft Azure Subscription icon
3) Sign in Dialog Box opens up asking for my email, which I provided and clicked continue
4) Selected Microsoft Personal Account from the option provided
5) Entered Password clicked submit
6) Error dialog box opens up as shown earlier.
I feel that it is related to management certificate as I am also not able to run certain commands like Get-AzureDeployment from Azure PowerShell, whereas Get-AzureSubscription works fine.
I have already saved publishsettings file from Azure and there are certificates installed in Personal section in Certificate manager.
I was able to resolve the problem. As I could see that Visual Studio and Power shell both were failing. Visual Studio was not able to connect to Azure and Power shell scripts where I was trying to add Azure Account failed. By doing a bit more searching and reading few article, I came to know that Visual Studio as well as Power shell scripts apart from using your credentials for azure also use management certificate to communicate with azure. A network tool used in our organization was causing issue in this https communication. Just got it enabled from IT team and I am done.
I have a small team working on web site project using Visual Studio 2010 and with Team Foundation server 2012.
In order to have proper control on deployment, I would like to implement my dream deployment strategy as shown in the figure ( https://www.dropbox.com/sc/foy5fh7pntreiha/AAB4L4hhbpjcm1zHi6VBLSa6a )
There is no problem for my team to perform the check in/out between their development pc with the TFS server. But I have problem to deploy code from TFS server to targeted web server.
I read many articles talking about build deploy, but for me I don't think I need to do build because mine is not a web application and we basically have all the codes in the targeted web server. We don't need to build the project into dll and then only upload to web server.
I tried using "copy website" feature in Visual Studio 2010, but on the copy website panel, it is always local programmer pc code at the left hand side and the targeted web server on the right hand side.
I wanted this deployment flow because I think this is the safest flow so that no one will accidentally upload the wrong version of code into the web server. Everyone would have no choice but to check in their code(s) into the TFS server before he/she can upload into the web server.
Please kindly help me.
Thanks
Dont do that.
Instead use Stage / Production server, Stage and Master git branches,
Tell them to exclusively work out of stage, you control the merge to master,
use deployhq or similar service to hook into git(github) and trigger automatic deployments.
Much better than VS, much safer. Should a deploy not work due to file error, DHQ will prevent the entire deployment and revert to old state.
Is it possible to publish bug reports directly to Visual Studio Online without having a Visual Studio Online account?
My idea would be that, when a crash of the application happens, the "fail" screen shows an option to send the bug report. I would like this bug report to be automatically added to Visual Studio Online.
I can't seem to find a good up-to-date information about APIs for Visual Studio Online.
I'm also a bit lost about what a "user" of Visual Studio Online is. Is there a way to create "a work-item only user"? In the "standard" TFS those users usually don't need a CAL to access TFS.
If not, it means that all my app testers will use a license for Visual Studio Online, meaning that after the 5 free users, I'll have to pay ~40 USD for someone who will just input bugs/work items?
Each user who needs to login to a Visual Studio Online account will need to have a user plan associated to them (including the free Basic plan allotments) or an MSDN subscription to access the account. We don't have the ability to have anonymous users login to a Visual Studio Online account (or for Team Foundation Server either).
You are right that there is a difference today between Team Foundation Server and Visual Studio Online which allows a "work item only view" on-premises that isn't matched in Visual Studio Online. That access level is called Limited for TFS on-premises instead of Standard. The Standard access level does require a TFS CAL. It's something we are currently exploring now.
Update
Visual Studio Online (and Team Foundation Server Update 4) now allows an unlimited number of stakeholders to have full access to work item tracking for free. This stakeholder license replaces and expands the original Work Item Only View capabilities.
For your testers, the best option for them would actually be Visual Studio Test Professional with MSDN or the new MSDN Platforms offering. This provides them the ability to access Microsoft Test Manager (in the first case) and the web test case management capabilities (in both cases) and allows you to file rich actionable bugs reports.
Update
Visual Studio Online has also been updated to provide the ability to execute test cases as part of the Basic license now. This will be most useful for user acceptance testers who aren't participating in test planning & test authoring but have been assigned a set of test cases to execute.
For your question about up-to-date API information for Visual Studio Online - it is the same documentation as the the TFS SDK at the moment. You can use the TFS SDK to build extensions for both Team Foundation Server and Visual Studio Online.