As asked in comments above; normally /bin files should not be locked for any particular reason (other than when the site is just starting up) - so I'm not entirely sure what's going on.
I can help you on the intermittent part of your question however; I would just flip the app pool before starting the file publish task.
appcmd recycle apppool /apppool.name
I'm also going through the Professional Sitecore 8 Development book and ran into the same issue. Not sure if you found the fix but thought I'd share my findings. I'm using Visual Studio 2017 Professional (toolsVersion = 15) and it turns out that gulp-msbuild doesn't support VS 2017. I made the following edits to the gulp-msbuild files to make this work:
There is a mismatch between your Sitecore binaries and Sitecore configuration.
The OnPackageInstallStartingRemoteHandler method was only added to PackagingEventHandler in Sitecore 8.2 Update 1. It didn't exist yet in 8.2 Initial Release. Which means you have 8.2 (or earlier) binaries with 8.2 Update 1 configuration.
What happens, most likely, is that you ...
Some possible solutions to reduce build/deployment time:-
Reduce the number of projects in your solution by 'compacting' projects.
Reduce the number of projects in your solution by having a Tests-project-free sln file.
Create an sln file with the explicit ProjectDependencies removed. This would only be for local builds. It doesn't help you for your ...
I used Habitat build chain some time ago and had similar issues.
I am not sure if it solve 100% of our problems but here is what I learned.
Check your references. Exclude unnecessary DLLs from publishing.
Unnecessary dlls are those dlls which are present in Sitecore Website/bin directory by default. You should avoid copying Sitecore.Kernel....
With transparent sync, the file system becomes the record for Sitecore. It treats the file system like the master database. For items and children that are monitored by transparent sync, if you create an item, TS will add it to the file system. If you delete an item from disk, it will be deleted from Sitecore. If you delete an item from Sitecore, it gets ...
It's basically a Node version issue. Assuming that you've downloaded the latest NodeJS and installed it (which means its location should be one of your system's environment variable PATH), just move up the $(PATH) location above the (DevEnvDir)|Extensions\Microsoft\Web Tools\External
Tools > Options > Projects and Solutions > External Web ...
After reading @jflheureux's answer and little bit digging around Habitat release package.
First Aha!, it is a Sitecore package definition file which contains everything - content items, security items, files. Second Aha!, we can Generate Package using Sitecore Rocks by using package.xml which is a similar process as Package Designer in Sitecore Desktop.
I believe the use of this package is internal to Sitecore employees who maintain and publish the demo on GitHub: https://github.com/Sitecore/Habitat/releases
They update the file, upload it to Sitecore, manually create a Sitecore package with it and upload that package to GitHub. Maybe they to the above automatically using custom CI tasks.
I have done some ...
Please make sure you have the Latest MS build version tools.
you can get the Latest versions from https://www.visualstudio.com/downloads/#build-tools-for-visual-studio-2017
Recommended for sitecore is to use Visual Studio 2017 and Build Tools For Visual Studio 2017. You can also use offline installer by pointing to the directory and running this command.
I was able to exclude the Sitecore DLLs from the Deployment when adding ExcludeFilesFromDeployment: 'bin\\Sitecore.*.dll' to my properties object used in gulp-msbuild. The same is probably possible using ExcludeFoldersFromDeployment.
I could not exclude multiple files with the proposed semicolon notation.
But when using MSBuild directly in command line, ...
I would recommend not using gulp to perform the deployments. Or maybe you can modify the script, as it's currently calling MSBuild on every TDS project in your solution.
If you setup the solution to have the appropriate build order, then a single call to deploy the solution would save time for a full solution deploy.
You can set the ProjectDependencies on ...
Unicorn data provider is responsible to read/write to file system.
If transparent sync is ON then sync (file system to Sitecore) will happen automatically.
In transparent sync, for items controlled by Unicorn it bypasses the Sitecore database completely. It means file system is treated like the master database.
Sitecore to file system (...
Even I faced similar issue..The task would start and hang up with the below message
Starting '05 Sync Unicorn'..
As mentioned above , along with MicroCHAP.dll, I had to unblock other two files (Sync and Unicorn ) to resolve the issue.
Before you proceed with setting up Helixbase or Habitat solution, make sure your sitecore instance is working fine and you have followed all the steps given in installation guide.
Yesterday I have installed Sitecore 9.0.1 update 1 and setup Helixbase solution from github on top of it which is working fine.
Your error seems to be related to paths you have ...
The Creative Exchange Import process deletes the gulpfile.babel.js (since a dot is not a valid character for the item name).
From Sitecore support I got the tip to rename the 'gulpfilebabel'-item to 'gulpfile' and change the extension from 'js' to 'babel.js'. And that works for me, the item was not deleted anymore.
Solved this by using
in every file upload/delete post/get because I'm using a self-signed certificate.
I changed the following files in the gulp\util folder inside the theme root folder:
search for 'url: url' and add to the request get/post call the parameter '...
This happens because when the Creative Exchange exports the theme files, it exports the gulpfile.babel.js file without the . between gulpfile and babel. A period is normally an invalid character for an item name, so that was probably stripped when the file was added.
If you rename the file to have the period back in (gulpfile.babel.js), gulp will then be ...
I have tried to achieve the same in the past. Even after several Google searches and personal attempts, I couldn't find anything to exclude files from deployment. The Gulp task is trying to pass the ExcludeFileFromDeployment as parameter to the msbuild.exe. I'm afraid the msbuild.exe doesn't recognize any parameter named ExcludeFileFromDeployment.
To work ...
The current master branch of Habitat is using v0.4.4 of the gulp-msbuild package. That version was still using an iterative process to figure out the location of msbuild. Priority is given to the following versions, in order:
This is a pretty limited process, because it doesn't allow for non-standard ...