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
Related
To create an enterprise integration solution using Azure Logic Apps I am trying to run the Enterprise Integration Pack in Visual Studio. I see that is supported only for VS2015.
installer
interesting blog EIP
But with many attempts my VS2015 installation for some reason never installs all tools with success (adding Azure SDK, EIP, App Logic Tools, sign to Azure Subscription with MFA..). And it is not supported anymore. Ultimately my target is to test complex XML mapping creating XSLT graphically (because for complex use case make it graphically is strongly easier). Essentially creating graphically what is called in Logic Apps "Maps". So how can I achieve that by passing all issues with VS2015?
Just to show one issue that I get when I try to loging to my Azure Subscription that is MFA:
I know of ARM, the REST SDK and the CLI Powershell cmdlets.
What I want to know is; which of these has the most extensive support for scripting resources without having to touch the (indeed very slow) Azure Portal?
And I would also really like to know which one of these Microsoft usually ship first with regards to preview features?
Each service in Azure is exposed using a REST API. Most of those APIs are publically supported. Some aren't.
It depends on the team that builds the elements that make up Azure and often their primary customer base. The Windows IaaS and AAD teams have been mostly PowerShell first. Machine learning and AI seem to favor azure-cli, which is built in Python, a very commonly used language in big data scenarios. The Azure Devops team has recently moved from the Visual Studio to the Azure brand (formerly Visual Studio Team Services, Visual Studio Online, Team Foundation Service preview). Their tools are mostly Node and Powershell based. Not everything in Azure is a "Resource", per se. So not all things are created or updated using Azure Resource Manager Templates (ARM).
So, unfortunately, there is no golden hammer when it comes to automating Azure.
Azure REST Api is, obviously, the best way to go, but its the least convenient (there probably is a better word for this). I really like arm templates, they (basically) allow you to define REST api calls you want to do and allow to do some looping\parametrizing\etc. As arm templates are just a proxy for the rest api, they usually work really well.
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
In Visual Studio 2015 ,there's a project templates for some azure service(etc:blob、storage:queue).
Now, I'm using Visual Studio 2017 enterprise ,i can't find the project template after intalled Azure SDK.
How can i fix this?
The quickstarts aren't included in the box in 2017 - you can find the latest here:
https://github.com/Azure-Samples?utf8=%E2%9C%93&q=storage-dotnet&type=&language
Azure Cloud is the monicker for the entire suite of products. Are you looking for the Asp.Net Core template that will run in Azure? Click on .Net Core and choose Asp.Net Web and it will set up a quick start for you that already can be published to Azure. Or was there a specific kind of template are looking for that isn't Asp.Net Core?
Edit: It's possible VS 2017 Azure SDK didn't release console templates yet. Having said that, the templates you have show how to use the Azure Storage code in a .Net Core project. They are less boilerplate and more tutorial. You should create a test one, see how the code works, then create a normal, basic .Net Core Console project and re-implement the code how you want it. There is nothing special about a quick start template except some pre-included dependencies and sample code.
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.