Fixing: Container cannot be copied onto existing leaf item

Strange behaviour, when copying all files and subfolders to a non-existing folder with PowerShell.

I made a mistake and tried to accidentally copy all files and folder to a non-existing folder with PowerShell, by executing:

Copy-Item -Path “C:\FilesAndFolderToBeCopied\*” -Destination “C:\MyNonExistingFolder” -Force -Recurse

Some files were copied, but then the error was thrown “Container cannot be copied onto existing leaf item”.

By creating the destination folder before copying, this error was resolved.

 

Fix: ReferenceError: primordials is not defined

Upgrade to NPM >= 12 and Gulp >= 4.0

 

How to overwrite PublishProfile => FolderProfile.pubxml => PublishUrl during a dotnet build or dotnet publish

To overwrite the PublishUrl during a publish of a .NET Core Web Application use the -o parameter:

dotnet build “C:\PathTo\MyApplication.csproj” /p:DeployOnBuild=true /p:PublishProfile=”Properties\PublishProfiles\FolderProfile.pubxml” -c Release -o “C:\Temp\MyApplication”

 

But we decided to NOT use the FolderProfile.pubxml anymore and just pass the parameter on the commandline:

dotnet publish “C:\PathTo\MyApplication.csproj” -c Release -f “netcoreapp2.2” -o “C:\Temp\MyApplication” -r “win-x64” –self-contained true | Write-Output

 

We decided to NOT use the FolderProfile.pubxml in .NET 2.2, because we observed some problems, when overwriting the publishUrl with “-o”, it would still use the “publishUrl” from the FolderProfile.pubxml.

When passing only the commands on the commandline, this problem was resolved.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.