I am using this video as a reference. It is basically explaining how to build Azure Api Apps using VS 2013. I want to do the same in VS2015 and have installed the latest Azure SDK. I am finding the following things missing and not able to find its equivalent in VS2015 or any documentation that says how its done differently using VS 2015
Here are a list of the things that I was not able to find:
At 4.58 into the video the option to right click and convert a regular Web Api app into a Azure App Api.
At 5.23 the apiapp.json file is no longer available in a VS 2015 Api App project. What if I want to change the swagger url? Where do I configure that?
At 12.13 into the video there is an option to generate an Azure Api App client. I could not find this either in VS 2015. All I have is this below
Am I bound to only provide urls for published API? What if I moved the API to a different URL later? I have not been thru this process yet so my next question is where do I configure the URL, which can possibly change as I move from DEV all the way thru to PROD.
Is there something missing in my tooling? Do I need to install something else other than the latest Azure SDK? How do I do those three items if my azure tools are up to date. I am using Microsoft Azure Tools for Microsoft Visual Studio 2015 - v2.9.40518.2
Back in December 2015, Microsoft made several changes/improvements to API Apps (they are listed here).
1-This feature no longer exist, you need to add the Swashbuckle nuget package manually.
2-The apiapp.json file is no longer used. Look for the SwaggerConfig.cs class in the App_Start folder.
3-The option has been renamed. Right-Click on the project in Solution Explorer and select Add/REST API Client...
Related
In late March Microsoft announced the release of the Azure SDK version 2.9.
On that page, as well as from within Visual Studio 2015, I'm invited to download and install it.
If I do so, the Web Platform Installer (5.0) fires up and shows me this:
That's strange...I don't want version 2.8.2...I already have it.
So I click the "back" button in Web Platform Installer and try to find 2.9 manually. At the time of writing, I'm seeing this:
That is, in the Web Platform Installer's list of products, version 2.9 is not there.
I'm on Windows 10 and using Visual Studio 2015 (with the latest update 2). My Web Platform Installer is version 5 and its primary feed is set as "default". Normally I have no problems installing an updated Azure SDK in this way.
I tried deleting the installer cache in Web Platform Installer (no help).
Can anybody give me a hint as to what might be happening here? Is anybody able to reproduce it (not finding v2.9 in the products list on WPI) on their machines? Could it be possible that v2.9 has been accidentally removed from the MS servers...any way to check this directly at the source?
For some reason it is not shown in the Web installer. This are the steps to fix it:
1 run a reset on the installer:
"%ProgramFiles%\Microsoft\Web Platform Installer\WebPlatformInstaller.exe" /reset
2 run the following registry fix:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WebPlatformInstaller]
"Install"=dword:00000001
"ProductXMLLocation"="http://www.microsoft.com/web/webpi/5.0/webproductlist.xml"
This seems to be a known issue. See the comments on this page:
https://azure.microsoft.com/en-us/blog/announcing-visual-studio-azure-tools-and-sdk-2-9/
Please search "2.9" in Web Platform Installer search pane. You will be able to see "Microsoft Azure SDK for .Net (VS2013)-2.9.6" in searched results.
Morning,
I am about to do a demo using the Azure SDK 2.8 resource group project template:
I have found a blog post from 2014 here:
https://azure.microsoft.com/en-us/blog/azure-resource-manager-2-5-for-visual-studio/
But the new Edit Parameters box is different and I cant work out what to do with "MyWebSitePackageFolder" and "MyWebSitePackageFileName":
I know they are related to storage:
But I get an error when doing a new deployment:
I am just creating a web app from the template:
Any help would be great!
Morning,
I have not been able to come back to this but I would say that the best solution would be to use VS 2015. Obviously 2013 was updated to allow you to do this but 2015, by default, does this with much more ease.
Not really a solution to the 2013 problem but I have the luxury of using 2015.
These parameters are used to deploy the Web Site files along with the Web App Service. This is done via a reference to the web application project in your solution. Apparently the integration with VS2013 seems to be poor, because in VS2017 these fields appear only after a reference to the web application project has been correctly configured.
The following two screens should help in the general case:
notice the web application reference properties
... and the deployment parameters
There is a very good Hands-On Lab provided by Microsoft on this topic here, called "DT00154: Authoring ARM Templates with Visual Studio".
I'm trying to publish my app to Azure which I have done several times before. For some reason I'm now getting the following error:
The Windows Azure SDK for .Net must be installed to enable publishing
to Windows Azure. LightSwitch will load a web page to begin
installation.
It loads a web page, downloads V11AzurePack_1_8_1.exe which in turn runs the Web Platform Installer 4.6 which in turn installs Windows Azure SDK Tools 1.8.1 for Visual Studio 2012. All of this succeeds. But going back and attempting to Publish results in the same error.
I noticed that there is a Windows Azure SDK for .Net (VS 2012) - 2.2 in the WPI. So I installed that manually, tried to publish, same result.
The SDK is clearly installed:
So why can't I publish to Azure? The only thing that looks like it might be a problem is that I have LightSwtich Azure Publishing 1.1 add-on for Visual Studio 2012 installed and I know there is a newer version of that available. But I can't find a direct download nor can I find a way to uninstall that package or force WPI to suggest an update.
Uninstalling everything Azure related (except the LightSwitch add-on as that seems to be unremovable and un-upgradeable), rebooting, and installing only the latest SDK produces the same problem.
After following a moderator's advice to repair Visual Studio on the forum, I was no longer able to open my project at all. I waited for a response but got none. So I decided to reinstall Visual Studio all together.
I followed this and this in order to remove as much of Visual Studio as possible and then reinstalled. I then installed Update 4 and was again able to open my project.
However, upon trying to publish, the same error was encountered.
I decided to upgrade my project to VS2013. That all seemed to go well. Wnet o Publish to Azure and it claimed that it succeeded. However going to Azure and launching the app's site brought up the previous version.
I deleted my Azure cloud service and started a new project in VS2013. I copied over one of my screens to have something to run. I then tried to publish to Azure. It again told me it succeeded but the site did not exist in the Azure Management portal. However, it did realize that I had created a new self-signed certificate so there was some type of communication there. Just not an actual Publish.
Then I did something really stupid. I uninstalled the Azure SDK and tried to reinstall it thinking that was the problem. Now I'm back to where I was before. An endless loop asking me to install the Azure SDK.
I wiped out all of my Azure services. Did a system restore to a month ago. Reinstalled the Azure SDK. This then allowed me to "Publish".
Not really.
Visual Studio claimed that the Publish Succeeded. The services were created and the certificate uploaded but nothing was deployed. I then did a manual deploy and the Production instance began to be deployed.
Everything seems to be running but I cannot access my app's site. I receive a 403 Forbidden error message. With or without HTTPS required. But this seems to be a different issue so I'm going to open another question on it.
Why these extreme measures were required is beyond me. This continual breaking of LightSwitch to Azure publishing is getting to be absurd though.
I've been following the progress of VS 2013 as its progressed through its releases (Beta, RC, and now GA) and have had an overall positive feeling about the release. Today, I spent the day working entirely in the new version (GA Premium) to ensure that it provides all of the basic functionality needed by my team prior to adoption.
It works well for general dev tasks - given several of my favorite extensions haven't been ported yet - but while attempting to administer our Azure storage from within the IDE it appears to be removed from the previous release.
While in VS2012's Server Explorer, I'm able to link to Azure account to discover all of my top level objects - Cloud Services, Service Bus, Storage, and VMs. Now within VS2013 - following the same setup procedures from the previous version - I only see Mobile Services, SQL Databases, and Web Sites under the Windows Azure node of Server Explorer.
After a little googling I found little insight or even others asking the same thing (since GA) so I'm starting to wonder if it's just me or if this is the way it'll be from now on??? Can anyone confirm and/or provide evidence from Microsoft indicating that this is intentional?
Installing the Windows Azure SDK should give you all of the features you're looking for. You can find directions here: http://www.windowsazure.com/en-us/develop/visual-studio-2013/ for using the current version of the SDK with the VS 2013 GA release.
I have a web application asp.net to deploy to Windows Azure. I try to run it on local first. But when debugging, I catch this error from VS2010:
"There was an error attaching the debugger to the IIS worker process
for URL 'http://127.255.0.0:82/' for role instance
'deployment16(6).WindowsAzureProject2.WebApplication3_IN_0'.
Unable to start debugging on the web server ......."
I've search so hard to find the solution for this problem but there's nothing seems work for me. I'm a newbie in Windows Azure, it's really a big trouble with me.
I had similar problem with Windows 8, debuging a cloud application with Visual Studio 2012 RTM and Azure SDK 1.71, when trying to launch the application into the compute emulator. It was a very simple app, but I used Azure diagnostics. At the end these are two things I have changed that have work for me, both turning on Windows 8 features (so go to Win8 and open 'Turn Windows Features On/Off'.
Activate the checkboxes for:
Internet Information Services Hostable Web Core
Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 4.5
Internet Information Services > World Wide Web Services > Health and Diagnostics > Tracing
Internet Information Services > Web Management Tools > IIS Management Scripts and Tools
That worked for me, it makes sense, as I'm using Visual Studio 2012 and trying to get some trace information using diagnostics in Azure.
I hope this will work for you or give some tip about the problem. In the case of being useful information, remember to vote as response or as value tip.
Thanks,
Mike
This usually happens when there's a problem with the project to be deployed to the emulator (WindowsAzureProject2 in your case).
Try the following:
Check %UserProfile%\AppData\Local\dftmp\IISConfiguratorLogs\IISConfigurator.log file for the error messages. See more details in this answer.
Make sure your project can be started without the emulator. It's a web project, so just try to start it as a regular web project. Or publish it to the separate folder and try to create a website in IIS of it.
Check your *.csdef and *.cscfg files to make sure all the configuration is correct.
Make sure that the build output of your project is not empty. You can do this by going to IIS, find the site with the name similar to deployment16(6).WindowsAzureProject2.WebApplication3_IN_0, right click --> Explore.... Make sure that this folder is not empty and contains all the files required to start a web project successfully.
BTW, there's a similar question: Debugger can't connect when starting local azure project
Follow step 11 from http://www.microsoft.com/en-us/download/details.aspx?id=35448. Worked for me on Windows 8 with Oct 2012 SDk
I just have today the same problem trying to Debug locally with Azure Storage Emulator in Windows 7. So in the Azure project properties, in Web tab, I checked the radio button 'Use IIS Express' and it debugged without problem. I hope this helps someone.
I encountered this exact same problem when I upgraded an existing Azure solution to the Azure SDK 2.1. After some hunting around I uncovered that the upgrade had automatically set the "Local Development Server" setting to "Use IIS Web Server".
Changing the "Local Development Server" setting to "Use IIS Express" fixed the problem immediately.
To access this setting right-click the Azure cloud project file in your solution, select the "Properties" option, tab down to "Web" and you'll see the following setup.
Also, make sure you run Visual Studio as administrator
Please check the version of emulator you have installed. If your code is created in older sdk and you have a new emulator installed it will give you this error.
Check the version of Azure APIs in your project, go to Project > references and right click on Azure dlls to check the version, same sdk version must be installed on the system, higher are optional as azure 2.x are not backward compatible.