I’ve got a node.js project which I’m using to publish to Azure. This worked fine the first couple of times I’ve published, but now when I try and publish it just fails with no error message. The output in the Azure Service Activity window in VS2015 is simply:
Auto ConnectionString Transformed Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Release\Package\PackageTmp.
And the output from the ouput/build window is:
------ Publish started: Project: node, Configuration: Release Any CPU ------
Auto ConnectionString Transformed Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Release\Package\PackageTmp.
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
I don’t really know where to start diagnosing this as there is no error message per se.
Things I’ve tried thus far:
Full Clean and/or rebuild
Deleted all folders from the BIN directory
Deleted all folders from the obj directory
Tried both debug and release configurations
Deleting the publish profile from VS and re-adding it from scratch
None of the above has made any difference
Has anyone seen this issue before or could suggest where to start diagnosing the cause?
Thanks
Do you happen to have GhostDoc installed?
Uninstalling it fixed it for me after seeing this issue.
I had the same issue, and it was due to file paths getting long more than the allowed number of characters. use this module to make your file paths shorter, and it will fix this issue
https://www.npmjs.com/package/flatten-packages
Related
I am getting error while publishing azure functions on azure portal.I tried lot of things and visited lot of links but didn't find any suitable soltuion.
Below is the output in output window.
Azure Application Settings updated.
1>------ Build started: Project: AwepayReconcile.DAL, Configuration: Release Any CPU ------
1>Models\AwepayContext.cs(26,10,26,214): warning CS1030: #warning: 'To protect potentially sensitive information in your connection string, you should move it out of source code. See http://go.microsoft.com/fwlink/?LinkId=723263 for guidance on storing connection strings.'
1>AwepayReconcile.DAL -> D:\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.DAL\bin\Release\netcoreapp2.1\AwepayReconcile.DAL.dll
1>Done building project "AwepayReconcile.DAL.csproj".
2>------ Build started: Project: AwepayReconcile.DL, Configuration: Release Any CPU ------
2>Infrastructure\Extensions.cs(34,42,34,44): warning CS0168: The variable 'ex' is declared but never used
2>Services\ReconcileService.cs(177,36,177,38): warning CS0168: The variable 'ex' is declared but never used
2>Services\ReconcileService.cs(210,36,210,38): warning CS0168: The variable 'ex' is declared but never used
2>Services\ReconcileService.cs(304,30,304,32): warning CS0168: The variable 'ex' is declared but never used
2>Services\ReconcileService.cs(403,30,403,32): warning CS0168: The variable 'ex' is declared but never used
2>Services\ReconcileService.cs(40,36,40,42): warning CS0169: The field 'ReconcileService.hssfwb' is never used
2>Services\ReconcileService.cs(38,33,38,38): warning CS0169: The field 'ReconcileService.sheet' is never used
2>Services\AzureBlobStorageService.cs(29,29,29,41): warning CS0414: The field 'AzureBlobStorageService._appSettings' is assigned but its value is never used
2>AwepayReconcile.DL -> D:\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.DL\bin\Release\netcoreapp2.1\AwepayReconcile.DL.dll
2>Done building project "AwepayReconcile.DL.csproj".
3>------ Build started: Project: AwepayReconcile.AzureFunctionsApp, Configuration: Release Any CPU ------
3>AwepayReconcile.AzureFunctionsApp -> D:\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.AzureFunctionsApp\bin\Release\netcoreapp2.1\bin\AwepayReconcile.AzureFunctionsApp.dll
========== Build: 3 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
Publish Started
AwepayReconcile.DAL -> D:\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.DAL\bin\Release\netcoreapp2.1\AwepayReconcile.DAL.dll
AwepayReconcile.DL -> D:\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.DL\bin\Release\netcoreapp2.1\AwepayReconcile.DL.dll
AwepayReconcile.AzureFunctionsApp -> D:\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.AzureFunctionsApp\bin\Release\netcoreapp2.1\bin\AwepayReconcile.AzureFunctionsApp.dll
AwepayReconcile.AzureFunctionsApp -> D:\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.AzureFunctionsApp\obj\Release\netcoreapp2.1\PubTmp\Out\
Publishing D:\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.AzureFunctionsApp\obj\Release\netcoreapp2.1\PubTmp\AwepayReconcile.AzureFunctionsApp - 20190320182641787.zip to https://awepayreconcileazurefunctionsapp20190320061400.scm.azurewebsites.net/api/zipdeploy...
C:\Users\tejinder.s\.nuget\packages\microsoft.net.sdk.functions\1.0.26\build\netstandard1.0\Microsoft.NET.Sdk.Functions.Publish.ZipDeploy.targets(42,5): error : The attempt to publish the ZIP file through https://awepayreconcileazurefunctionsapp20190320061400.scm.azurewebsites.net/api/zipdeploy failed with HTTP status code RequestTimeout. [D:\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.AzureFunctionsApp\AwepayReconcile.AzureFunctionsApp.csproj]
Please help me to git rid of this.
Thanks
When deploying your function app to Windows, you should set WEBSITE_RUN_FROM_PACKAGE to 1 and publish with zip deployment.
Zip deployment is a feature of Azure App Service that lets you deploy your function app project to the wwwroot directory. The project is packaged as a .zip deployment file. The same APIs can be used to deploy your package to the d:\home\data\SitePackages folder.
With the WEBSITE_RUN_FROM_PACKAGE app setting value of 1, the zip deployment APIs copy your package to the d:\home\data\SitePackages folder instead of extracting the files to d:\home\site\wwwroot. It also creates the packagename.txt file. The function app is then run from the package after a restart, and wwwroot becomes read-only.
For more details, you could refer to this article.
I have been following several tutorials from Microsoft on the Hololens, from the real basic 100 ( creating a Cube ) to the 101E.
However when deploying to the Hololens it doesn't troughs a error, all succeed, but when starting the App it shows a white screen and then zzz with a Moon "emoticon".
The only error i'm getting is the one attached. However developer license is active. And i also renewed it, but is that related? Don't know.
Log file:
>
3>------ Deploy started: Project: Origami, Configuration: Release x86 ------
3>Deploying to Phone Internal Storage...
3>Creating a new clean layout...
3>Copying files: Total 48 mb to layout...
3>Checking whether required frameworks are installed...
3>Framework: Microsoft.VCLibs.140.00/x86, app package version 14.0.24123.0 is not currently installed.
3>Framework: Microsoft.NET.CoreRuntime.1.0/x86, app package version 1.0.23819.0 is not currently installed.
3>Framework: Microsoft.VCLibs.140.00/x86, app package version 14.0.24123.0 is not currently installed.
3>Installing missing frameworks...
3>Registering the application to run from layout...
3>Deployment complete (0:00:05,557). Full package name: "Origami_1.0.0.0_x86__sx6pycx103f58"
========== Build: 2 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
There are several scenarios which produce this error. Here are a few ways, from my expetience, that may solve this issue:
In the Package.appxmanifest, find the line specifying TargetDeviceFamily and change Name="Windows.Universal" to Name="Windows.Holographic" and MaxVersionTested="10.0.10240.0" to MaxVersionTested="10.0.10586.0".
Go to the device portal and shutdown the instance of the app if it is running.
Try uninstalling the app from the emulator before installing it.
The hololens can be quite tedious to work with at first, but once you get the hang of it, it is a wonderful technology!
Had cruise control.net (v1.8.5.0) up and running for about 6 months on 4 projects, no issues.
In the past week or so, one project reports a failure... even though it compiles correctly and no unit test errors are reported as they were previously on failures. None of similiar reports on SO or elsewhere describe or correct this problem.
Here is dashboard status:
BluePrint Failure Breakers : support2 Failing Tasks : NUnitTask
In the build report log where it would normally show which tests failed, it shows no failures just the unit startup message:
ProcessModel: Default DomainUsage: Single Execution
Runtime: net-3.5
Normally here for an nunit error the erroring test #s and names that failed and the nunit assert failure message. In a passing situation it would display xml for each test.
Can someone point me somewhere else what might be causing this or where else I might look to find out why?
When I run nunit manually on the same tests the cruise control service has checked out the build server, everything works fine.
I've tried restarting both the cruise control service and IIS, same result.
When I look in the ccnet.log file on the server, it doesn't report anything more specific than whats already in the build log above:
Done Building Project
"C:\Users\j\Documents\CIWork\BluePrint\BluePrint.sln" (Build
target(s)).
Build succeeded.
0 Error(s)
Time Elapsed 00:00:13.99
2017-01-20 18:50:36,869 [BluePrint:DEBUG] Running unit tests:
C:\Program Files (x86)\NUnit 2.6.3\bin\nunit-console.exe
/xml=C:\Users\j\Documents\CIWork\BluePrint\logs\LatestTests.BluePrint.xml
/nologo
C:\Users\j\Documents\CIWork\BluePrint\Tests\bin\x64\Release\TestBluePrint.exe
2017-01-20 18:50:36,869 [BluePrint:DEBUG] Starting process [C:\Program
Files (x86)\NUnit 2.6.3\bin\nunit-console.exe] in working directory
[C:\Program Files
(x86)\CruiseControl.NET\server\BluePrint\WorkingDirectory] with
arguments
[/xml=C:\Users\j\Documents\CIWork\BluePrint\logs\LatestTests.BluePrint.xml
/nologo
C:\Users\j\Documents\CIWork\BluePrint\Tests\bin\x64\Release\TestBluePrint.exe]
2017-01-20 18:50:36,953 [BluePrint:DEBUG] Not setting PriorityClass on
[C:\Program Files (x86)\NUnit 2.6.3\bin\nunit-console.exe] to default
Normal 2017-01-20 18:50:37,686 [20:DEBUG] [BluePrint C:\Program Files
(x86)\NUnit 2.6.3\bin\nunit-console.exe] ProcessModel: Default
DomainUsage: Single 2017-01-20 18:50:37,686 [20:DEBUG] [BluePrint
C:\Program Files (x86)\NUnit 2.6.3\bin\nunit-console.exe] Execution
Runtime: net-3.5
My configuration has not changed in 6months, here's the relevant task from ccnet.config:
<nunit>
<path>C:\Program Files (x86)\NUnit 2.6.3\bin\nunit-console.exe</path>
<outputfile>C:\Users\j\Documents\CIWork\BluePrint\logs\LatestTests.BluePrint.xml</outputfile>
<assemblies>
<assembly>C:\Users\j\Documents\CIWork\BluePrint\Tests\bin\x64\Release\TestBluePrint.exe</assembly>
</assemblies>
</nunit>
As I was posting this I recalled that one of these tests downloaded a fair amount of data from internet and cached it. Running it from the console worked, but running it from system account as service must've been slower to exceeded default cruisecontrol timeout.
Weird that no timeout error was in the log. However copying the cached files from the admin account to systemprofile account fixed it. Will also see if the nunit test can be modified to automatically time itself out.
I am unable to publish my website to either my Azure hosted staging site or my new Azure live site.
I HAVE published to each once but have been unable to do so since the first time.
I have tried...
Regenerating the Publish profile
Manually entering passwords
Editing elements of the Database connection strings
Comparing the *.pubxml files with another site that works
I'm tearing my hair out with this now.
This is all I can see - Any more log info would be nice, or an error message!
2>------ Publish started: Project: Communityweb, Configuration: Release Any CPU ------
2>Transformed Web.config using C:\Development\Clients\Ministry\Pragmatic Agile Community\source\Communityweb\Web.Release.config into obj\Release\TransformWebConfig\transformed\Web.config.
2>Auto ConnectionString Transformed xslt\Web.config into obj\Release\CSAutoParameterize\transformed\xslt\Web.config.
2>Auto ConnectionString Transformed Views\Web.config into obj\Release\CSAutoParameterize\transformed\Views\Web.config.
2>Auto ConnectionString Transformed macroScripts\Web.config into obj\Release\CSAutoParameterize\transformed\macroScripts\Web.config.
2>Auto ConnectionString Transformed obj\Release\TransformWebConfig\transformed\Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
2>Auto ConnectionString Transformed .\umbraco\Install\Views\Web.config into obj\Release\CSAutoParameterize\transformed\umbraco\Install\Views\Web.config.
2>Auto ConnectionString Transformed .\umbraco\Xslt\Web.config into obj\Release\CSAutoParameterize\transformed\umbraco\Xslt\Web.config.
2>Copying all files to temporary location below for package/publish:
2>obj\Release\Package\PackageTmp.
2>
========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
Don't add 'node_modules' to the deployed files if you can possibly avoid it. If not you'll have to be selective. Gulp is a particular menace here for recursive nested node_modules folders that break the windows path limit.
I've just clone OrchardCMS from codeplex, built it and tried to deploy it to my web hosting service using Visual Studio's 'Publish' command.
No files get published and the publish fails with the following error:
1>------ Publish started: Project: Orchard.Web, Configuration: Release Any CPU ------
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(2352,5): Error : Could not open Source file: Could not find a part of the path 'C:\Users\Tim\targetsite.co.uk\src\Orchard.Web\Media\web.config;Media\web.config'.
1>
========== Build: 0 succeeded, 0 failed, 5 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
I've checked the source code, and the file is there and in the correct folder. So what's this error message actually trying to tell me? What's going on here and how do I fix it?
This is a bug. It's already been reported and is being addressed now:
http://orchard.codeplex.com/workitem/19264
http://orchard.codeplex.com/workitem/19282
The second report proposes a workaround that might help you out till this get fixed.