I am just creating an Azure Stream Analytics using Azure Stream Analytics Tool for Visual Studio in 2019 preview version, but it is saying that the version of Visual Studio is not supported. I am sure that I have installed the required workloads and extensions.
I am also sure that I have connected to my Azure Subscription using the Server Explorer.
Any idea why? Is it really not supported yet or I am missing something?
We do not support Visual studio 2019 currently and will figure out how to adapt to the latest vs version.
Keep using VS2107 should be a better choice
Well, it seems like the extensions are not supported in the new Visual Studio yet. But it is not a blocker, we can still use the option "Provide data source settings manually" and complete the configuration.
Note: After configuring the Input, Output, Query when I try to Submit to Azure, the Visual Studio is getting closed. It seems like it is a bug.
You can also consider using Visual Studio 2017 till the new release of the extension.
Related
I have an instance of visual studio 2017 in which azure functions are developing, strangely i stopped seeing, publish to azure option in the publish targets window and also in create new profile window.
If i open any of my other azure functions project in vs 2017, the window is seen correctly.
What could be different only for this case?
(Copying comment into an actual answer for the community to see)
well ,strangely my function app was missing functions sdk!! hence i was not seeing right publish outputs. after i installed Microsoft.Net.Sdk.Functions it all worked
I have developed an Azure Functions project in Visual Studio 2015 (a project with a .funproj file extension). Now I want to migrate it to Visual Studio 2017 but when I try, VS does not load the project.
Why is the migration failing and how can I complete it manually?
Azure Functions tooling for Visual Studio 2017 is still work in progress. They are expected to be announced during upcoming Build event.
Watch this github issue for status.
UPDATE: The Preview of Visual Studio 2017 Tools for Azure Functions are now available for download. The blog post explains the tools, requirements, and has a link to the download. Note that it only works in VS 15.3 Preview, not in earlier versions.
As far as I know, there's no migration tooling available per se, so you'd have to start from a blank project and then convert your script to static class and function.json to proper bindings.
I need to deploy an Azure WebJob and tried to follow this article. Is this supposed to work in Visual Studio 2017? I have none of the mentioned context menu entries (tried two different machines).
I have none of the mentioned context menu entries (tried two different machines).
What type of project did you create? Until now, we could see the [Publish as Azure WebJob…] context menu when we create a Console App(.NET Framework) in Visual Studio 2017.
You also need to check whether you have checked the Azure Development option when you install your Visual Studio 2017. If you did not do that, you could re-run the Visual Studio 2017 install exe file to update your Visual Studio 2017.
If your project type is Console App(.NET Core), the publish function is not available until now.
No.
WebJobs deployment features are available in Visual Studio 2015 when you install the Azure SDK for .NET.
It's not yet available in VS2017.
EDIT: See post below.
I recently installed Visual Studio 2017 and my problems began with remote debugging.
So, this is the message error.
And on Azure, they are lagging behind the official release of VS Remote Debugging for this VS version.
Any idea on how to make this work?
If you use Cloud Explorer within Visual Studio 2017 to initiate the Remote Debugging it'll set the VS Version on the Web App correctly. Currently, the portal doesn't include UI to allow you to set 2017 as the version, but using the Cloud Explorer to initiate remote debugging will do it behind the scenes. We just need to wait for the Azure Portal to be updated and get caught up with VS.
Visual Studio 2017 is now listed as a Remote Debugging Version in Azure.
There has however been some change on what is possible on Cloud Explorer. To access the 'Attach Debugger' option, you need to use the Server Explorer.
I've been trying to get the .NET Dev Kit and Azure SDK to work with Visual Studio 2012 and am not having much luck. What am I missing?
The Azure SDK installation instructions don't work on VS 2012. When I search for anything Intuit-related from the VS Extension Manager, nothing comes up.
I tried installing from the VS Gallery but then there's no Intuit Anywhere menu in VS as shown in the VS 2010 screen shot. (These instructions are highly suspect, since Intuit has moved away from the "Intuit Anywhere" name. But given that the developer site was overhauled recently I would expect the instructions to be up to date.)
Is there an easy way to get this to work with VS 2012, or am I wasting my time? Am I better off just building everything from scratch? (We have done that in another project, just not with Azure.)
The Plugin for Visual Studio has not been updated for Visual Studio 2012, the last supported version is 2010.
The code that the plugin generates is available as templates and sample code as well.
It includes the Oauth grant and handler pages, as well as the OpenId handlers.
regards,
Jarred