sitefinitysitefinity-10

Upgrading vers 9 to 10, confused on last step of official documentation article "Manually upgrade a project to Sitefinity CMS 10.0 with a NuGet pack"


I am following the documentation listed below:

https://docs.sitefinity.com/apply-authentication-model-after-nuget-package-upgrade

The last step, number 8 says,

"Copy the new ResourcePackages folder.  If you have changes in the folder, be careful not to overwrite them."

Question: Where am I suppose to get/copy the "new ResourcePackages" from and where do I copy it to?


Solution

  • I created a support ticket with Sitefinity, in short, the solution is when upgrading using Nuget you must respond "Yes/Yes to All" when asked to overwrite the following:

    "File 'ResourcePackages\Bootstrap\razorgenerator.directives' already exists in project 'SitefinityWebApp'. Do you want to overwrite it? [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "N"):"

    Below is the full response from Sitefinity

    I can see the confusion in the wording, as it took myself some time to understand this step. This step in my opinion should be apart of the following documentation :

    https://docs.sitefinity.com/upgrade-a-project-that-has-nuget-packages

    During the NuGet upgrade, the Package Manager Console will prompt you with the following :

    "File 'ResourcePackages\Bootstrap\razorgenerator.directives' already exists in project 'SitefinityWebApp'. Do you want to overwrite it?
    [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "N"):"

    Which refers to the "Copy the new ResourcePackages folder." line.

    The second line :

    "If you have changes in the folder, be careful not to overwrite them."

    Is a caution, mentioning that, if you do have custom changes in your ResourcePackages folder, be careful not to overwrite those changes, as selecting "Yes/Yes to All" will do so.

    I hope my response clarifies any confusion. Please let me know if you have any further questions.

    Regards,
    Wesley Skiba

    Support Engineer: Wieslaw Skiba

    Thank you,
    Wieslaw Skiba