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.
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 am using Visual Studio 2017 Version 15.3.2 to write Xamarin mobile apps.
My issue is that File->New->Project does not offer Azure Mobile Apps anymore. I have attempted to find the templates online and run repair on my Visual Studio installation, but the project template is no where to be found.
Any suggestions?
You could choose Cloud->ASP.NET Web Application template and you will find that Azure Mobile App is a sub project template of ASP.NET Web Application.
When I right click on the Web Project in the Solution Explorer of Visual Studio 2017, I don't see an option 'Add Existing Project as Azure Web Job'.
I did install Nuget-packages such as Microsoft.Web.WebJobs.Publish for the web project.
I am following this link https://learn.microsoft.com/en-us/azure/app-service-web/websites-dotnet-deploy-webjobs#convertlink to enable automatic WebJobs deployment with a web project.
Ideally, I am supposed to see like this, but that highlighted option is not shown in my visual studio 2017
Click to see image for how actually visual studio should have shown me an option
I don't see an option 'Add Existing Project as Azure Web Job'.
As far as I know, Visual Studio does not support to deploy WebJobs with ASP.NET Core Web Application currently.
But this feature is available in ASP.NET Web Application.
If you can not see 'Add Existing Project as Azure Web Job' option in your ASP.NET Web Application, you can try to repair or reinstall your Visual Studio and upgrade/reinstall your Azure SDK.
I just installed Visual Studio 2013 Update 3 and Azure SDK 2.4. I also installed "Microsoft Azure Tools for Microsoft Visual Studio 2013 -v2.4". I also tried repairing and reinstalling both the sdk and the Azure tools.
I can see 4 templates under Cloud (Azure Cloud Service,ASP.NET web application,Microsoft Azure WebJob and Azure Mobile Service) when creating a C# project.
There is no Cloud folder and no Azure templates at all when creating a F# project.
Is F# not supported or is it something wrong with my installation? I think it was supported earlier.
The F# template for Worker Roles is available as you are creating your Cloud Service project.
Create a Cloud Service project using C# or Visual Basic.
Next, as you are selecting the roles for your cloud service, you can select the F# Worker Role.
Full Disclosure: I've not actually used the F# template. I just recall seeing it when creating my C# projects.