Hi! I have an issue trying to publish my project that is an umbraco website to azure. The errors I get when trying to do this is: Unable to copy file "C:\Users\Camil\.nuget\packages\umbraco.cms.staticassets\14.2.0\staticwebassets\umbraco\backoffice\packages\search\examine-management-dashboard\modal\fields-settings\examine-fields-settings-modal.token.js" to "C:\IT_kurser\Kurser\Webbutveckling-dotnet\CMS\Inlämningsuppgift\Onatrix_umbracoCMS\Onatrix_umbracoCMS\obj\Release\net8.0\PubTmp\Out\wwwroot\umbraco\backoffice\packages\search\examine-management-dashboard\modal\fields-settings\examine-fields-settings-modal.token.js". Could not find a part of the path 'C:\IT_kurser\Kurser\Webbutveckling-dotnet\CMS\Inlämningsuppgift\Onatrix_umbracoCMS\Onatrix_umbracoCMS\obj\Release\net8.0\PubTmp\Out\wwwroot\umbraco\backoffice\packages\search\examine-management-dashboard\modal\fields-settings\examine-fields-settings-modal.token.js'. There are 24 errors. I have tried several things already but nothing helps, for example: cleared nuget cache, tried on another database and webapp in azure, cleared folder obj and bin, allowed long searchnames in windows, If I could get any help from you understanding why it has to copy the files from '...\user\.nuget\packages\umbraco.cms.staticwebassets....' to my folder where my project is i would be thankful, I dont want to do anything that could ruin the project, so i am taking careful steps. Thanks in advance!

This is because of a bug in Windows + Visual Studio + Publish where the path names are too long for the publishing tools. So not really Umbraco's or Azure's fault. If I remember correctly from previous times this has happened, the workarounds are 1. Enable "long path support" in Windows, and try again (maybe you did this already? But IIRC there's more than one way to do it) 2. Move the project as close to the root of C:\ as possible - so from

C:\IT_kurser\Kurser\Webbutveckling-dotnet\CMS\Inlämningsuppgift\Onatrix_umbracoCMS\Onatrix_umbracoCMS

to

C:\Onatrix

for example, and try again 2. Use VS Code to publish instead, there is some Azure Deployment extension that can do this - not sure exactly how to do this, maybe the answer is in one of the other posts with the same problem 3. Use

msdeploy

to publish instead - not sure exactly how to do this, maybe the answer is in one of the other posts with the same problem 4. Make sure you're using the latest Umbraco (looks like you are) since I know Umbraco intended to fix this on the Umbraco side @User

i had this same issue, like above i moved project into c drive and worked a charm