I have a cloud service in azure with two .NET worker roles and i want to add a Node JS webrole.
I have installed the Node.JS tools for visual studio which creates templates from which should allow node apps to be deployed as a web role.
Packaging of the service goes smoothly, but after publishing the cloud service via visual studio the following error message is shown:
The file provided is not a valid service package. Detailed error code: presentation Invalid application runtime - a runtime component is missing:/base/x64/WaIISHost.exe.
But when I look in the package file for the cloud service using an archiving tool and go to /base/x64/, the exe "WaIISHost.exe" is there.
I am quite stuck at the moment. There seem to be few other people that have this issue and I have already reinstalled the Azure SDK as suggested here and I am using the latest version (2.9.1).
Related
I created a simple node.js express app that I want to host in an Azure Windows App Service.
The App Service resource was created successfully on Azure.
The project was created using the "Node.js Web Application" template.
When I attempt to deploy from Visual Studio 2019, I get the following error message:
web.config not found in project, to create a project to deploy to
Microsoft Azure you must create an Azure Node.js project.
Is there a different template I should be using?
If not, what the contents of the web.config file look like, so I can attempt to create it by hand.
For deploying Node js Application to Azure you need to select
Azure Node js Web Application Template.
You have selected Node.js Web Application.
If you select Azure Node js App, by default web.config will be generated.
Copy the already created source files to the newly created Azure node.js Application.
Update
You might not have selected Node.js development option while installing Visual studio.
Click on the Install more tools and features option and select Node.js and update the VS
I've deployed my code to an app service using Azure Devops CI release agent. Once I browse to the App service, it shows this error, stating that .net 5 isn't installed, and lists what is.
'The specified version of Microsoft.NetCore.App or Microsoft.AspNetCore.App was not found.'
This is what I have selected in the app service configuration, as it looks to be the only .Net 5 option.
Based on my test, the Azure App Service could support the .Net 5.
From the error message, it is indeed show that .net 5 hasn't been installed in the app service.
I could reproduce this issue too.
But when I select the .Net5 (Early Access) in Configuration and Save it, it will update the web app settings. Then the website could run successfully.
From your screenshot, you already selected this option. You could try to restart the App service and check if it could work.
On the other hand, you could try to create a new App Service with .Net5 (Early Access). Then you could directly use the App service with .Net 5.
Here is a ticket with the detailed introduction, you could refer to it.
I've been having trouble being able to use any of the functionality of ASPPDF on a web app I publish to Azure. When running the website locally through Visual Studio, the website behaves as expected, and I can use any of the methods in the ASPPDF library. However, when I publish to Azure and test the website I get this error: "Retrieving the COM class factory failed due to the following error: 80040154."
This error is documented here: http://support.persits.com/show.asp?code=ps071016166.
The Azure App Service I am publishing to is 64-bit as well as the project I am working on is configured for 64-bit. The libraries from ASPPDF are also 64-bit. Making any one of these 32-bit is not an option since the App Service must be 64-bit.
I have already viewed this: AspPDF and AspJPEG on Windows Azure. And I don't see how I can apply that solution to an App Service in Azure.
Has anyone had any success using ASPPdf on an Azure App Service?
I currently have an Azure Cloud Service within Visual Studio containing simple Node.js web role.
This builds and packages correctly within Visual Studio locally, and deploys perfectly into the Azure cloud service.
When trying to build the solution with Visual Studio Team Services (previously Visual Studio Online), MSBuild fails claiming:
2016-07-01T10:09:56.7893397Z ##[error]C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Windows Azure Tools\2.8\Microsoft.WindowsAzure.targets(1329,5): Error : WAT070 : The referenced assembly C:\a\1\s\CloudTool\Client\Client.exe was not found. Please make sure to build the role project that produces this assembly before building this Microsoft Azure Cloud Service Project.
...which seems to indicate it's expecting the build of the Node.js project to emit an .exe file.
I followed the same steps as mentioned in this article (https://www.visualstudio.com/en-us/docs/release/examples/nodejs/node-to-azure-cloud-service#help-and-support) to continuous deploy node js cloud service project.
When I googled it I found this git hub issue link (https://github.com/Microsoft/nodejstools/issues/428 ) in which no solution mentioned so I want to know this issue resolved or not if yes how can I solve it because I am not able to find any solution.
I have configured a cloud service to run multiple web applications in one web role. More information on this is in the documentation.
The documentation does not appear to be correct for local builds with the Azure 2.3 SDK. Apparently, since SDK 1.8, the physicalDirectory attribute is not relative to the Azure cloud service project folder, but its output folder. Also see this question. By changing the path to ../../../Project.Name the service can be built and deployed locally from VS2013 with SDK 2.3.
We also use continuous integration on Visual Studio Online. However, the project now fails to build with the message that the path to my second web project is invalid. The path it's trying to use is C:\Project.Name\. I don't think this is quite correct.
I have tested with ../Project.Name as the physicalDirectory attribute value on VSO, but that also fails.
Is it a matter of somehow correctly configuring this for Visual Studio Online, or is it simply not currently supported?