Can I use TFS API in my code and deploy the code in the machine where Visual Studio or Team Explorer doesn't exist?
I found this, which says I shouldn't do that.
Any help on this? Thanks!
No you can't, when you develop client application for the TFS, this means you need the run time files for this API which is exists in the Team Explorer.
You could use the new OData API, or the standard WebService API (officially unsupported) to connect to TFS without the need for the SDK or Team Explorer on the machine.
And there's the Java API's that ship with Team Explorer Everywhere 2010 SP1, which are supposedly easier to use in stand-alone fashion than the .NET API's that require Team Explorer to be installed.
Do note that in order to follow the proper license terms, you generally do need to have a TFS CAL for every machine/user connecting to TFS.
Related
It looks like Azure DevOps may have APIs similar to Office 365 but I'm not finding them in the documentation and when I called support they don't seem to know what I'm talking about. We are trying to build an integration like we have with o365 using Graph api's. Can anyone point me in the right direction- it seems like Azure DevOps is mostly an on-prem solution and not SaaS at this time.
Assuming you are talking about the former Visual Studio Online, and the current Azure Devops, then you have this article with the reference to its REST APIs. Also you have the option to use the Client SDKs with one of the programming languages available, to establish the integration.
You might looking for Visual Studio SDK documentation...
The Visual Studio SDK helps you extend Visual Studio features or
integrate new features into Visual Studio. You can distribute your
extensions to other users, as well as to the Visual Studio
Marketplace. The following are some of the ways in which you can
extend Visual Studio
Check this link: https://learn.microsoft.com/en-us/visualstudio/extensibility/visual-studio-sdk?view=vs-2019
I am an experienced BizTalk developer who is now moving on to Azure logic apps. I have installed Visual Studio 2017 and added the "Azure Logic Apps Tools for Visual Studio" through the Tools|Extensions and Updates menu. However, I don't see an option for creating/editing XML schemas(.xsd files), I don't see the BizTalk EDI X12 schemas and there is no option for creating a map. What am I missing? I have searched and searched with no luck. Thanks.
XSD & Maps are part of the Azure Integration Account service. You need the Microsoft Azure Logic Apps Enterprise Integration Tools in order to use those. You will see that the mapper is very similar to what you know from the BizTalk-world.
I'm not sure Microsoft Azure Logic Apps Enterprise Integration Tools is already supported in VS 2017. I know it's supported on VS 2015.
On a side note, xsd's and maps created using a BizTalk Server Project will also work fine in an Azure Integration Account and Logic Apps,but might lead to a more complex ALM-story.
Right now there is no tooling available for Visual Studio 2017, only for Visual Studio 2015.
The tools are based on the BizTalk components and those components are only available for Visual Studio 2015.
You can download EDI schemas from Open Source Github, but only EANCOM and EDIFACT, X12 messages have been removed due to licensing questions https://github.com/Microsoft/Integration/tree/master/BizTalk%20Server/Schema
I would like to begin on development for sharepoint.
Instead of setting up a dev environment on premise, I would like to set up one on Azure.
I've found some tutorials http://blogs.msdn.com/b/sharepointdev/archive/2013/09/26/create-sharepoint-2013-development-environments-quickly-on-azure.aspx but each on use Visual Studio RC. When I try to create one with Visual Studio Ultimate, there's no "Configure Developer Desktop" folder and I don't know how to set up tools and which tools?
Do you have a follow up or a virtual drive that I can use?
If you have the chance to have an msdn subscription, you can follow http://visualstudio2013msdngalleryimage.azurewebsites.net/
Best, you can subscribe to an office 365 account and more easily deploy to your new sharepoint site
I have written this in detail using 3 staged approach. The first of the post is available at this link
http://wellytonian.com/2014/10/sharepoint-2013-development-platform-azure/. Basically you can setup a complete SharePoint 2013 standalone server, setup the point to site vpn and connect. Code away :)
I'm an MSDN subscriber beginning a personal project that will involve WPF, Web Services, and SQL Server. I'm planning on using my MSDN benefits to host the Web Services on Azure and the database on SQL Azure.
I was going to run TFS on my own dev machine, but then heard about Microsoft's Team Foundation Service cloud offering. Also, it appears that I could run my own instance of TFS on Azure. At this point I'm thinking that Team Foundation Service is the best option because:
I'd prefer to have TFS in the cloud over my main dev machine so that I can access it anywhere and not have to worry about having to back it up.
I'd rather not have to worry about setting up and administrating TFS on Azure if I'm not getting anything extra out of it.
I'm not exactly sure if setting up and using TFS on Azure will be free (or continue to be free) with my MSDN Subscription.
Has anyone experienced any major drawbacks to using Team Foundation Service, like a major loss of flexibility or functionality?
I've been using TFS Services since it has been in preview for my personal work - and I haven't had any limitations in terms of source control/build services. The service is fairly comparable to the full TFS server; but doesn't include the more advanced features such as test automation.
The pricing page also states that service will continue to remain free for MSDN subscribers: https://tfs.visualstudio.com/en-us/pricing/information/
Before TFSPreview existed, I asked some people in the know at MS about running TFS in Azure and I was told that there are some non-trivial problems with running TFS on a virtual machine on Azure. I believe this is why MS are offering TFS as a service rather than as a template for a virtual machine. As such, if you want to use TFS and you want it to be in the cloud, I'd definitely use the TFS Preview.
I am looking to migrate some databases out of Visual Source Safe (VSS) and into Team Foundation Server (TFS). I know I am able to migrate from VSS to SVN, and then from SVN to TFS using a few tools that I have found (either free or purchased). The aim is to get the source code into TFS and then integrate the project with SharePoint so that various documents can be accessed from there.
How easy is it to set up TFS to integrate with SharePoint? What do I need to do?
What documents/files can/will be added to SharePoint? Does TFS choose for me or can I select what I want to appear in SharePoint?
Any examples or information on how TFS integrates with SharePoint would be appriciated.
The instances are separate. The files stored in SharePoint are not in the version control library and vice-versa. There is a web interface to the source control library available outside of SharePoint.
Each Team Project in TFS has an associated SharePoint portal. What we do is version control all of our software in TFS, and store all of our documentation in the SharePoint portal that corresponds to the team project. We made sure to turn version control on within SharePoint so we can retrieve previous versions.
On the odd occasion that we do need to version control documentation alongside the source code (for audit reasons), we will store that in a documentation folder within TFS.