Our organisation is using Team Foundation Server. At the moment, developers are manually adding issue tracking references to their check-in comments. We have a custom check-in policy that enforces a valid reference has been added to the comments.
What I'd like to be able to do is provide the user with a user friendly dialog/UI component that allows them to select an issue from a list which will then insert the reference, in the required format, into the comment box.
We are mainly using Visual Studio 2010 but some development still happens on Visual Studio 2008. The issue tracking software is a 3rd party one called OnTime.
Is this possible? Can someone help point me in the right direction.
Doh! It was as simple as creating an instance of a form and calling ShowDialog within the Evaluate method.
Related
Visual Studio 2015
Visual Studio 2013
Until recently used TFS for source control with Microsoft live id with my yahoo email.
Recent transition from TFS to VSTS.
Couple weeks ago devops switched my VSTS account to use company email instead of yahoo email.
After that in VS I couldn't use source control anymore,
was getting error: "TF30063: You are not authorized to access usga.visualstudio.com\DefaultCollection."
and not being able to bind to source control.
Devops removed my company-email-account and reactivated my yahoo-email-account
and source control in VS started to work again, and with VSTS now.
I have not used Visual Studio for a week or so.
Today I discovered that:
My solutions lost Source Control Bindings.
I can Not bind my solutions to Source Control Again in Visual Studio.
When I re-bind it tells me that status is 'invalid'.
I do Not get any other errors.
Happens for all solutions that used to work fine with source control.
I seem to have access to www.visualstudio.com -> mycompany.visualstudio.com
and can see my projects there.
Please help me to undestand what is going on and rebind.
Many thanks
This should be a cache related issue, try to delete VS and TFS cache and restart VS.
Also try to remove your account info which stored in Credential Manager （Control Panel-All Control Panel Items-Credential Manager-Windows Manager）
Then reconnect to VSTS in Visual Studio use your personal account, make sure selected the used workspace, get latest; or directly delete the old workspace, create a new one.
My issue was resolved the following way:
1. when I've started to use TFS four years ago, I've created Microsoft Live Id account using my Personal email
this year when our devops were switching us from TFS to VSTS
they have tried to enforce rule of everybody to use their Office email for MS Live Id account. So they have created new account for me with Office email
Then I have described issues
Problem was resolved by switching me back to using original MS account with my Personal email.
And
I had to delete existing workspaces in Visual Studio 2015
and create new ones for my solutions to rebind code to VSTS.
For some reason I had to repeat this process few times.
Hope it helps
How to customise I have knowledge to customise process template in tfs 2015 or in 2012 but for upgrade version in 2017 is there any changes or any enhancement.
I have find in google but I have not found any helpful to customise process template in 2017 specifically.
your help should be appreciated. thanks
The first step is you need to download the process template you want to edit from you TFS server. To do this, launch Visual Studio and navigate in the menus to "Team -> Team Project Collection Settings -> Process Template Manager". When the dialog shows up, you will be able to select the template you wish to edit and download it. Detailed instructions for this can also be found here.
Once you have downloaded the process template, you have a series of XML files that describe how TFS should handle almost everything when you create a new project using that template. The XML can get overwhelming quickly, even for the most seasoned person. You should ideally use the Process Template Editor which is a plugin for Visual Studio (the link is for Visual Studio 2017). For details on customizing a template, you should start off by reading the Customize a process template on the Visual Studio documentation site.
Once you've made your changes, you simply need to upload your process template back to the server using the Process Template Manager (where you downloaded the template). If you replace an existing template, anything using that template will get the updates. If you create a new template, only new projects using that template will be able to make use of it.
Not much has changed with editing the process templates between TFS 2013, TFS 2015 and TFS 2017. So if you find a blog or a write up on one of the versions, there is a good chance it's still valid. There may be slight differences in UI, but there shouldn't be anything ground breaking.
DISCLAIMER!!!
Now that I've answered your question, I would be negligent if I didn't explain the dangers of what you are about to do. Customizing a TFS process template can be very dangerous to your TFS server. Microsoft does not guarantee or put any warranty on changes you make. You customize a template, you are on your own. You have to understand that this template literally tells TFS how to work. It is highly recommended to have a sandbox environment complete separated from your production server and make all changes in said sandbox environment first. Only after you've validated the changes should you move it to your production environment. In addition, anytime you deploy a change to your production server, make sure you have healthy backups your databases. I can't stress this enough.
Lastly, any changes you make, you run the risk of locking yourself into a specific version of TFS or making your upgrade path far more difficult. My last piece of advice is to carefully weigh the need for customization over the risk associated with making it.
We're looking into migrating to TFS 2010 in the next few weeks. However, we're unclear on what kind of tools are required for the team. We know developers need Visual Studio but what tooling is required for Project Managers and Testers that will ONLY need to manage work items? Do they also need Visual Studio to just view and edit work items?
Project Managers and Testers can use the following methods to access TFS 2010
The web access portal - this allows the ability to create/run queries of work items, and even view source/builds if they want
Excel/Project - Both have integrate with TFS. You are able to load work items directly into Excel/Project, edit them, and publish them back to TFS.
Visual Studio with Team Explorer only - This is a barebones installation of VS, with the Team Explorer only. It doesn't take all that long to install, but it will say "Visual Studio" when launched. Not sure if that is scary to testers/project managers.
Web access provides a good complete set of functionality, but having VS/Team Explorer will provide a rich client experience (read: faster, more responsive).
Additionally, in order to get the Excel/Project integration, you'll need at least the VS/Team Explorer installed on the client box, even if they never use VS. And you need a CAL (Client Access License) to use the web access portal.
So to summarize, TFS provides a lot of ways for the non-developer to interact with the system, but all of them require a CAL, and most of them require installing VS/Team Explorer on the client machine.
In short, they don't need Visual Studio. They can use Team System Web Access (formerly known as TFS Web Access) to do pretty much everything a developer can do, except associate a check-in with a work item. After you install TFS 2010, you simply browse to http://yourserver:8080/Tfs/web and you're in!
Project Managers (and all other team members) can also work with work items from Outlook using 3rd party TFS client embedded in Outlook: TeamCompanion www.teamcompanion.com. This way, assuming they otherwise use Outlook, they wouldn't need to change tools or use any additional tools at all.
As is the case with Excel or Project integration they would still need a TFS CAL and additionally a TeamCompanion license.
TeamCompanion supports much more than just work item management: Email/TFS integration, SQL Server Reports, SharePoint document integration and much more...
Full Disclosure: I am the Product Owner of TeamCompanon, so I may be biased :-).
There is a web front end which you can use to manage the work items. There is also integration to Excel and MS Project.
See http://msdn.microsoft.com/en-us/library/ms181304.aspx for more information on Team Foundation Clients
which project use to create event receiver for sharepoint 2007 list - sequential workflow or state workflow? i'm using VS 2010
Neither.
Workflows are events which are run via the SharePoint Timer service and can be executed by any server in the farm.
An event receiver is essentially an event handler that will be executed either synchronously or asynchronously (depending on which event you're implementing) on the same server which handled the request that triggered the event receiver.
Visual Studio 2010 does not have much OOTB support for SharePoint 2007. You might consider installing the WSP Builder extensions (note that the proper download is not the recommended download - you'll need the 2010 BETA 1.4). They give new project types which include event receivers. Note though that there are some quirks with those project types but overall they are very helpful to getting the project set up correctly.
Be sure to read the documentation regarding the folder/file layout of your projects. If done correctly, you can use WSPBuilder to generate your WSPs for you.
A quick search revealed this blog post which might help get you started with regard to project structure. I'm sure there are many, many more references available. Happy coding!
I'd like to provide a sort of UI on a commit operation in Visual Studio for my team. How would I go about that, would I create a Studio add-in or is there a TFS event that would help in this case?
Great question! Unfortunately there isn't an extensibility point on the client side (Visual Studio) to be able to intercept a check-in. However, there is a server-side extensiblity point (called an ISubscriber Decision Point) that you can intercept and allow/reject the check-in. Do you think that would be helpful for you?
That extensibility point is not really documented very well but we have some information in Chapter 25 of our new TFS 2010 book (Wrox Professional Team Foundation Server 2010) about how to create one of these.
Another option would be to create a custom check-in policy... That doesn't seem like the best way to solve the problem though and is riddled with its own issues.