Has anyone been able to setup continuous integration deployments for one of these node.js tools for VS template projects to Azure Websites using Visual Studio Online source control--TFS or git? I can't get either to work.
The .njsproj references Microsoft.NodejsTools.targets from my local install that does not seem to be on the build servers. But even when I work around that by copying it into the project and source control and updating the build reference so that it "compiles", I get:
Exception Message: Could not find a part of the path 'C:\a\bin_PublishedWebsites'. (type DirectoryNotFoundException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
I'm assuming the issue is creating a deployment package. So I tried adding Microsoft.WebApplication.targets (which I stole from an ASP.NET project) to the build script but that changed nothing.
I'd really like to have continuous deployment working in this scenario.
More detail:
After installing Node.js Tools for Visual Studio, I created a node project (I tried the empty web app and the express app). I ran it locally, it works fine. Then I created a project on Visual Studio Online and added the code to source control. When using TFS for source control, I added the node_modules folder contents to source control but I left that out when using git. I setup an Azure Website to deploy from source control and pointed it at the right repository. Again, I tried both TFS and git with this process.
Just to be sure I wasn't missing something fundamental, I did all of this some process with a new ASP.NET MVC project and it works great.
The .njsproj references Microsoft.NodejsTools.targets from my local install that does not seem to be on the build servers. But even when I work around that by copying it into the project and source control and updating the build reference so that it "compiles", I get:
Exception Message: Could not find a part of the path 'C:\a\bin_PublishedWebsites'. (type DirectoryNotFoundException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
I'm assuming the issue is creating a deployment package. So I tried adding Microsoft.WebApplication.targets (which I stole from an ASP.NET project) to the build script but that changed nothing.
I'd really like to have continuous deployment working in this scenario.
More detail:
After installing Node.js Tools for Visual Studio, I created a node project (I tried the empty web app and the express app). I ran it locally, it works fine. Then I created a project on Visual Studio Online and added the code to source control. When using TFS for source control, I added the node_modules folder contents to source control but I left that out when using git. I setup an Azure Website to deploy from source control and pointed it at the right repository. Again, I tried both TFS and git with this process.
Just to be sure I wasn't missing something fundamental, I did all of this some process with a new ASP.NET MVC project and it works great.