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.
Related
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:
My question is about the minimal level of a Visual Studio Subscription that is eligible for Visual Studio Team Services. From what I understand you need a Visual Studio Subscription (previously MSDN Subscription) to be able to access VSTS online but someone told me you need the full Enterprise subscription, which I find a bit hard to believe. Is this really true or can you access it with a Professional as well?
You do not need any Visual Studio Subscription to use VSTS: it's free for five users independent of any Visual Studio Subscription.
Beyond the first five users, you can purchase individual per-user licenses.
A license is also included with Visual Studio subscriptions. So if you have a Visual Studio Professional Subscription, that will enable the standard features of VSTS.
There are additional features enabled to Visual Studio Enterprise subscribers:
Private pipelines
Package management
Test manager
But all other features are available to the free and Visual Studio Professional subscribers.
VSTS is free of cost initially for 5 user's, called Basic User Access.
In detail, VSTS provides with 5 Basic user access, unlimited Visual studio subscriber access and on top of it all other's[Non-Visual studio Subscribers] get restricted to Stakeholder access [No access to code].
Find the access comparison Basic vs Stakeholder Access
Article to add users/Visual studio Subscribers to VSTS
If you're not looking to develop in VS, but another IDE, you can also just buy the User CAL for Basic code access https://marketplace.visualstudio.com/items?itemName=ms.vss-vstsuser
I'm looking at whether we can migrate our old on-premises TFS 2010 server to Visual Studio Team Services. We all have MSDN subscriptions so it looks promising. But we have an app we wrote to keep our SQL scripts in version control. The app uses the old Microsoft.TeamFoundation.Client & Microsoft.TeamFoundation.VersionControl.Client object model approach. I'm lost in the Marketing-focused pages about VS Team Services and all I can find is talk of a REST API. Would we really have to re-write this part of the app or am I just missing something?
(I know we could do the source control bit from Visual Studio but the app has other functionality I haven't seen elsewhere.)
Can anyone advise me, please?
The TFS 2010 API works just fine with Team Services, so your app should just work.
You can currently use the 2010, 2012, 2013, and 2015 TFS client API's for TFS against Team Services. Team Services is just TFS on the internet...
We are investigating using TFS for a small development group. All the developers are remote to the office. VPN is an option but not preferred, as we have to change vpn connections several times daily to support other functions in the business.
So I'm trying to figure out the different options that TFS can be configured with to support that model. I've read about setting up Proxy Servers but that was using an older version of TFS so I'm not sure that still is/was the best option.
I haven't been able to locate good current documentation about the best/different ways to configure TFS to support this model.
I don't need comments about using Mercuial, GIT or something else. I'm aware of them and including them in my overall evaluation but right now I'm trying to see what solutions TFS does or does not offer. All developers have MSDN licenses and so TFS is free to the group.
You have 2 options (without VPN)
1) Like Martin suggested, look at VSO (Visual Studio Online, http://www.visualstudio.com) this is the cloud based version of TFS it's free for up to 5 developers.
2) Setup TFS internally inside your organization and make that instance available on the internet through your firewall. You can secure it with certificates so only you team can connect in. There is a lot of information on MSDN on how to secure it using SSL and certificate.
Cheers,
ET
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.