I was flamed for my last post being too vague, so I shall be as precise and accurate as I can today.
I am a .NET developer now learning node.js. I am trying to set up continuous deployment of my node.js project within Visual Studio to Azure from Visual Studio Online. I have downloaded and installed the node.js tools for Visual Studio 2015 here. I have successfully checked in my code to Visual Studio Online using Git from within Visual Studio 2015.
I have read lots of web articles on the subject but in each I come across a seemingly insurmountable problem. For example, this article gets me quite close to a solution, but falls over trying to Visual Studio Online. It can't find the repository.
No matter, I move on. I have now managed to get my Visual Studio Online code associated with my web app through manage.windowsazure.com (rather than portal.azure.com, which I find very confusing. Why are there two? They seem to expose the same functionality).
Now I am getting a "Deployment Failed" message in Azure, and the log in VSO reveals "Exception Message: Deploying to Azure Cloud Service requires a Visual Studio Solution (.sln) that contains either a ccproj or a lsxproj. (type DeploymentException)".
What can I do about this? I have seen lots of articles that describe publishing node.js project types to Azure with no problem. Can someone please point me in the right direction?
Thanks, M
Related
I have a project that i've been working on since last year. I am using Visual Studio as my IDE for developing this project. It is a Xamarin.Android project.
Since my project is becoming really big and my local machine is not that powerful, I created a Microsoft Azure account and want to continue the developing process using a VM. I have created the Visual Studio VM inside Microsoft Azure, and now I want to bring my source code of the project to that VM
Can anyone help with how to do this, please?
I found a solution. So for everyone that havve this question, here is a usefull resource : http://geekswithblogs.net/hroggero/archive/2015/03/10/copy-files-from-you-local-computer-to-an-azure-vm.aspx
Getting this error when I select a "publish target" in VS 2015 update 3. Had a look for a while online but didn't see anything, so any help would be appreciated if you could point me in the right direction.
An error has occurred while processing the request: Method 'StopRemoteProfiler' in type 'Microsoft.VisualStudio.Web.WindowsAzure.AzureWebSite' from assembly 'Microsoft.VisualStudio.Web.WindowsAzure.Impl, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have implementation
I updated to the to Azure sdk 2.9.6 last night because of a different issue but related where there was no error, but no existing apps were listed.
I can confirm that this works on my work computer and I have existing apps on Azure, but not working on my home computer.
I am a bit loath to uninstall and reinstall VS, so any help would be appreciated. Of course, if the only solution is to reset, then so be it.
Thanks,
Jarrod
I faced the same problem. This is what worked for me.
I updated the "Microsoft .NET Core 1.0.1 - VS 2015 Tooling Preview 2" by going to Menu -> Tools -> Extensions and Updates -> Updates -> Visual Studio Gallery. It shows all the available updates for your version of studio. Select the component to update. It should download a file named "DotNetCore.1.0.1-VS2015Tools.Preview2.0.3.exe" or something similar. When you run this file, if you have the software already installed then select the repair option. It will ask you to close any running instances of Visual Studio, also make sure you have internet connection.
Also if you are using Web Deploy to publish your app make sure you have Microsoft Web Deploy v3 or higher installed or you will get error. You can do it using Microsoft Web Platform Installer.
Hope it helps.
I am currently developing an Azure Logic App. This is very straight-forward from portal, but I need to use Visual Studio as an IDE for this. I have followed all the steps mentioned in https://azure.microsoft.com/en-in/documentation/articles/app-service-logic-deploy-from-vs/ article, but when I try to do right-click "<>.json" and say "Open in Logic App Designer", the Visual Studio crashes everytime.
Could anyone please assist on the same?
Thanks
I has a similar issue, I found I had to install the Azure Logic Apps Tools (https://marketplace.visualstudio.com/items?itemName=VinaySinghMSFT.AzureLogicAppsToolsforVisualStudio), restart Visual Studio and then create the Azure Resource Group project for it to work.
The project that I had generated without the tool installed did not work (ever).
I'm using the Azure SDK 2.9.6, Visual Studio 2015 update 3
Are you currently signed into Visual Studio with an account containing valid Azure subscriptions/currently has strong internet connectivity? That is known to cause editing issues before.
If that does not solve your problem, we have enabled logging feature in our most recent update (ver 1.0.0):
a. Open developer command prompt for VS2015
b. Run following command to start VS with activity logging enabled.
devenv.exe /log
c. Repro the issue in this instance and close it.
d. You can find the activity log at location :
%APPDATA%\Microsoft\VisualStudio\14.0\ActivityLog.xml
e. Please send us this file to us.
If you can share the logs with logicappsbug#microsoft.com, we can further assist you on this specific problem.
Thanks,
Max
Currently I am analysing a setup for a sharepoint development project in Windows Azure.
I would like to use Visual studio online (TFS online).
Since Visual Studio online doesn't support building sharepoint projects (missing ddl's in de GAC), we need to use an own build server (either a VM in windows azure or a server on-premise).
Now, when you build a project with Visual studio online, you are being charged every minute you build. Because you use CPU power. But do you also pay those minute's if you use you're own custom buildserver?
I cannot find the awnser on any of the sites of windows, so does anyone have expirience with this?
Thanks in advance!!!
Your own build server does not make use of the Hosted Build Cluster of VSO and thus does not count towards your build credits. I can't find any clear indication on the VSO site that an on-premise server is free, only that you're charged for the "Shared Resources" used by your VSO project.
Shared Resources (per Visual Studio Online account)
-
A Visual Studio Online account includes resources that are shared across all users and projects on that account.
Build - Build definitions can be created using Visual Studio and can be run on Visual Studio Online. Builds can be configured to run on demand, at a specified interval, or for continuous integration (CI). Build is charged per minute for the actual amount of computing time it takes to build the project.
http://www.windowsazure.com/en-us/pricing/details/visual-studio-online/
Your on premise build "does not run on VSO". And this is the closest wording to a confirmation or denial. But I can tell from experience that the on premise server indeed does not count towards your "Hosted Build" minutes.
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