Update NuGet.Config package sources

[hlakudi200]

Updated shesha-core/.nuget/NuGet.Config to correct package source configuration for backend deployment.

Commented out legacy configuration block

Cleared existing package sources to avoid conflicts

Updated local-packages path to ../s/shesha-core/local-packages

Retained required NuGet v3, v2, and ImageSharp sources

Kept source control integration disabled

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• shesha-core/.nuget/NuGet.Config is excluded by none and included by none

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch hlakudi200-patch-1

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[IvanIlyichev]

Hi @hlakudi200. Please do the following:

1. remove commented out configuration, it doesn't make any sense to store this config
2. relative path ../s/ is environment specific, if you really need it then it should be stored in a separate config file (e.g. NuGet.Azure.Config)
3. Packages from local-packages folder are not used by the applicaiton, I believe you can safely remove it from config