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.
Related
I have had webdeploy running for YEARS on a Windows Server 2012 machine with standard MSBuild arguments (like this).
Yesterday I installed the Windows (Server Hosting) version of the .NET Core Installer from the .NET Core downloads page.
Since then my build tasks are running and successfully building my website, but not actually running any web deploy publishing. It is not failing - it is just not being run.
I want to stress I am talking about a 'legacy' .NET application - not a .NET Core application. I just installed .NET Core for somebody else.
I can verify this with the following observations:
There are no errors in any event viewers (except ones that are months old)
There is no message in the msbuild logfile that says Start Web Deploy Publish, however log files from just a couple days ago do have this message.
I can connect to the local server at port 8172 and it makes a connection.
It is happening with multiple projects that nobody else has access to.
_PublishedWebsites does get created with the latest files - it just never gets deployed anywhere.
What could possibly have broken this? Did the Windows Server Hosting package break it - or was it just some other update that came in? I've run out of ideas how to fix it and don't want to revert to xcopy!
Managed to fix it :-) Not sure exactly which of these steps did it, but I suspect it was Visual studio.
I was using TFS Express 2015 and upgraded to Update 3.
I also installed Visual Studio 2015 on the server itself.
I had previously had .NET Core RC2 (or whatever they called it at the time) installed and I uninstalled that before installing .NET Core RTM. Wondering if that removed some component that was required.
Like I said everything was working fine before I installed the .NET Core RTM - but fortunately installing VS and TFS brought everything back to normal.
I am having a new issue when deploying Azure Cloud Services via Visual Studio 2015 SP1.
This is driving me up the wall and I am curious if anybody else has seen this? Basically, I can build just fine, I just can't package for or publish to a Cloud Service - the error is:
CloudServices232: The role MyProject.AsyncWorker is using an unsupported TargetFrameworkVersion v4.6.1.
This wasn't happen a few weeks ago, but now I can't publish it. Yes I am targeting .NET 4.6.1 - but that has been WORKING JUST FINE for a while now and I followed all the steps to run install.cmd and manually deploy it.
This appears to be a new build-time error (it used to be a warning).
I installed the new Azure SDK from the Web Platform Installer.
Now when I try File > New Project > Cloud > Windows Azure Cloud Service > OK
Then I get this error message:
Error: this template attempted to load component assembly 'Microsoft.VisualStudio.CloudService.Wizard, Version=1.0.0.0 ...
I have tried everything I can think of including uninstall of the 1.8 SDK, uninstall of the 2.0 SDK and reninstall. Always I get this message. I cannot see anything about this on the internet. My install gave no error messages.
Also noticed that now in Server Explorer I only have Data Connections, Servers, Windows Azure Service Bus and WIndows Azure Web Sites. There's nothing for storage.
Does anyone have any ideas what may be wrong.
I've had the same problem with skd 2.0
Even trying repairing or installing missing features won't work.
After hours spent on repairing and reinstalling, the only solution I found was to uninstall BOTH Visual Studio and Azure sdk, and installing them again.
After the reinstallation it works fine, but I still have no clue why :P
I keep a development VM for each SDK that comes out. When I upgrade older projects to newer SDKs there are bugs, sometimes bugs without workarounds. I've learned the hard way that installing a new SDK is dangerous.
If you can, develop inside a VM and take occasional snapshots. Otherwise, you do end up reinstalling Visual Studio and installing the original SDK that you first created you project with. -Richard
I've seen this issue on multiple machines after upgrading to 2.7, 2.8, and/or 2.9. Reinstalling VS, VS Updates, and/or SDKs would sometimes help, but sometimes not. The last time no combination of installs worked.
I finally ran Visual Studio with logging enabled via Devenv /log, and according to the %AppData%\Microsoft\VisualStudio\{version#}\ActivityLog.xml file, there was an error merging the configuration file located at %LocalAppData%\Microsoft\VisualStudio\{version#}\devenv.exe.config I deleted that config file and restarted Visual Studio and the problem went away.
Uninstall Visual Studio using VisualStudioUninstaller did the trick for me.
Then I did a clean install of Visual Studio and Azure SDK, and everything worked just fine!
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.
We are trying to evaluate and eventually migrate to the windows azure cloud platform.
I am stumbling on the installation process...
I'm currently following this tutorial.
I can't get the Windows development Fabric interface working like on this picture.
When I install the app fabric sdk (downloaded here) I get no .exe program to simulate the cloud...
I installed Windows AppFabric which is not what I need (I think).
I keep on being directed on AppPlatformInstaller which do not install what I need but I'm sure is part of my solution.
You are downloading wrong SDK. For Windows Azure Cloud platform you must download and install Windows Azure SDK And Tools for Visual Studio.
Then you will have a folder %Program Files%\Windows Azure SDK\v1.5\bin. There will be devfabric and devstore folders, under which the local development Frabric and Development Storage executables will reside.
Then if you are targeting .NET based solutions, you will have new project templates in Visual Studio, and everything shall be running smoothly. On the other hand, if you are targeting open source solutions you might want to follow the like provided by Ben.
As for Windows AppFabric - yes, it is wrong in terms that it is not related to Windows Azure at all.
Let us know if you have any issues when downloading and installing latest Windows Azure SDK And Tools for Visual Studio
You may want to check out the docs available from the Microsoft Interoperability Team. They maintain an entire site dedicated to running PHP on Windows Azure
http://azurephp.interoperabilitybridges.com/articles/build-and-deploy-a-windows-azure-php-application
Basically to get it working just install the Windows Azure SDK and with Windows Azure SDK for PHP. Build your PHP application and then run the package command. Your PHP application will be rolled into a Windows Azure project and launched in the local dev fabric