I am using the Visual Studio TFS 2017 Power Tools to apply some changes to a few of my organisation's TFS work item templates. As expected, the work item templates have two form layout elements - one for the Visual Studio IDE form and the other for the corresponding Web form.
I've had no issue implementing, previewing and validating the changes specific to the Visual Studio IDE form. However, I'm unable to do similar for the changes that are specific to the Web forms and that makes me rather uneasy, as I'd like to also review and validate my changes before importing them to the Live environment. Is there any way I can achieve this before importing my changes?
If I go to create a new project in Visual Studio, the add-in template it generates is based on JavaScript and uses JQuery framework, but I'd like to create an add-in using React (so I can use Fabric UI for react) and Typescript, is there an option for doing that?
I know that if I can use Visual Code and Node to create a project like this, 'yo office' has the option to generate a template for many different types of add-ins, but I found no option for this in Visual Studio.
The Office Tools in Visual Studio do not have that option, but it's a great idea! Please go to Office Developer User Voice and suggest it.
I'm using the Team Foundation Service (TFS in the cloud) for source control. Within my account I have multiple projects. Via the website I can see that the first project has the default Release & Sprint hierarchy set. I have another project that I've created some releases & sprints. In the web admin I've also setup different areas for my project.
Within Visual Studio 2012, when I go to create a task (TEAM > NEW TASK), it always shows the AREA=[FirstProject] and the ITERATION options as only the [FirstProject]. I can't change the area to a different area or the iteration. It acts like Visual Studio is "stuck" within the [FirstProject] and won't let me get to any of my other projects when working with tasks & backlog items. However I can create tasks in the web client. Within Visual Studio I can also run queries and find tasks.
So, I'm trying to figure out how to make sure I can use Visual Studio 2012 to create & manage tasks and not have to go to the website each time. It acts stuck on one project. Ideas?
Note I'm not having issues with any of the other source control issues... it's just an issue with working with tasks.
In the "Team Explorer" in Visual Studio 2012 you can select the Team Project you need by clicking on:
"Home | [FirstProject]", "Projects", and selecting a different one.
Also, in Visual Studio 2012.2 (Update 2) there is also a "Plug" looking icon at the top of Team Explorer, this allows access to many Servers, Collections and Team Projects from a panel in Team Explorer instead of a menu.
I have TFS 2010 integrated with share-point 2010, inside the project portal i try to add a new task but there is no start date neither due date ?
is that normal ? how can i add these fields ?
It is normal I'm afraid, the web page view of a Work Item is usually identical to the view of the same item in Visual Studio. For some reason these fields are hidden.
You have 2 options. You can change the Work Item template on your Team Project so that these fields are not hidden, or you can use the Office integration features of Team Explorer.
To edit the template you'll need the TFS 2010 power tools.
To use Office integration you'll need Team Explorer installed, plus either Excel 2007+ or MS Project 2007+. Project automaticaly hooks in to the start and due date, with excel you can select which fields you want to view and sync with TFS
I'm trying to develop some SharePoint workflows for the company I work for, and I'm not too familiar with the ins and outs of the technology. Normally when I want to familiarize myself with something, I just play with it, look at the properties, find all the methods, etc.
When I fire up Visual Studio and try to create a SharePoint workflow, it gives me an error indicating I don't have a reference to "Microsoft.SharePoint.dll". Someone told me that it was normal to see that because you have to do all your development on the SharePoint Server itself if you want to do workflows. Is this true?
If so, is there anyone out there that has successfully developed SharePoint workflows in a multi-developer environment without resorting to any "hacks"?? Thank you for reading and your responses...
If you want to create a Sharepoint workflow using the Sharepoint Templates, you need to have a Windows 2003 or 2008 Server running Sharepoint. Essentially, that is true for all Sharepoint development: For it to be really efficient, you need to run Visual Studio on a Sharepoint Server. This in turn means that every developer needs his own Sharepoint server and then you have one additional "Staging"-Server where you deploy and test your combined solutions. Suddenly, that MSDN Subscription looks very attractive :-)
As for your Workflow learning question: I can highly recommend "Workflow in the 2007 Microsoft Office System" by Apress.
Yes, you have to do all your development on a the SharePoint server itself. Consider using a virtual machine and package up features that you can deploy to your staging and production environments.
http://weblogs.asp.net/erobillard/archive/2007/02/23/build-a-sharepoint-development-machine.aspx
http://www.wssdemo.com/Pages/EntDev.aspx
Yes, you can develop SharePoint Workflows, WebParts, etc. in a multi-developer environment without any hacks. I suggest you use
a MOSS 2007 VPC Image
Ankhsvn to use svn inside Visual Studio
and also the WSPBuilder Extensions
and maybe you should read What are your biggest complaints about Sharepoint? to see what you're up to ;-)
To learn SharePoint Workflow development,you can start at Step by Step Tutorial. Creating Workflows for Windows Sharepoint Services and MOSS2007
While it's true you need SharePoint installed on your development computer for most SharePoint development, you can get away without it for workflow development. Follow these steps:
Copy the SharePoint DLLs to your development computer (for workflow you'll need microsoft.sharepoint.WorkflowActions.dll).
Open Visual Studio and open the Toolbox tab
Add a new tab (call it SharePoint Workflow Items)
In the new tab, click "Add Items"
Click the "Activities" tab
Locate and add microsoft.sharepoint.WorkflowActions.dll
You'll see a few new tasks show up and already selected.
Once you do this, you'll be able to develop WF workflows that can use SharePoint-specific tasks. Deployment and testing the workflow is another task altogether.
Also, it was casually mentioned in this thread, but you cannot develop SharePoint workflows on a 64-bit SharePoint Server at this time. You will have to have a 32-bit Windows Server and SharePoint Server installation.
Here is a link to some SharePoint workflow how to videos.
http://chrisbarba.wordpress.com/2009/12/21/sharepoint-workflow-how-to-videos/