Share via

New Error after upgrade

RANDY SHEPHERD 20 Reputation points
2026-02-25T13:28:33.55+00:00

Hello,

I have upgraded Visual Studio 2026 to Ver. 18.3.2.

I am getting an error in my solution. "System.Configuration.UserScopedSettingAttribute" could not be found.

Please help me fix this.

Thanks

Randy

Developer technologies | Visual Studio | Other
Developer technologies | Visual Studio | Other

A family of Microsoft suites of integrated development tools for building applications for Windows, the web, mobile devices and many other platforms. Miscellaneous topics that do not fit into specific categories.

0 comments No comments
{count} votes

Answer accepted by question author
  1. Q&A Assist
    2026-02-25T13:28:44.88+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error message "System.Configuration.UserScopedSettingAttribute could not be found" typically indicates that the necessary assembly reference is missing in your project after the upgrade to Visual Studio 2026. Here are some steps you can take to resolve this issue:

    1. Add Reference to System.Configuration:
      • Right-click on your project in Solution Explorer and select "Add" > "Reference...".
      • In the Reference Manager, search for System.Configuration and ensure it is checked. If it is not present, you may need to install the appropriate NuGet package.
    2. Check Target Framework:
      • Ensure that your project is targeting a framework that supports System.Configuration. You can check this by right-clicking on your project, selecting "Properties", and looking under the "Application" tab for the Target Framework setting.
    3. Update NuGet Packages:
      • Make sure all your NuGet packages are up to date. Go to Tools > NuGet Package Manager > Manage NuGet Packages for Solution... and check for any updates.
    4. Clean and Rebuild the Solution:
      • Sometimes, simply cleaning and rebuilding the solution can resolve issues after an upgrade. Go to Build > Clean Solution, and then Build > Rebuild Solution.

    If these steps do not resolve the issue, consider checking for any specific migration notes related to your project type in the Visual Studio release notes or community forums.


    References:

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.