Visual Studio Community 2019 cannot start debuger due to application manifest

PerezRE 1 Reputation point
2020-11-24T02:52:43.897+00:00

Hello!

After developing and debugging my windows form application I tried to publish through the same IDE (I think is ClickOnce), but once it was installed it could start due to the following error given by the event viewer:

Error generating activation context for "C:\Users\perez\AppData\Local\Apps\2.0\L044Q30V.OR9\N7CETP6X.RWA\open..tion_0000000000000000_0001.0000_f686950aa927d482\QuickAdmin.exe.Manifest". Error in manifest file or directive "C:\Users\perez\AppData\Local\Apps\2.0\L044Q30V.OR9\N7CETP6X.RWA\open..tion_0000000000000000_0001.0000_f686950aa927d482\QuickAdmin.exe.Manifest" in line 166. The value "es-419" of the attribute "language" of the element "assemblyIdentity" is nto valid.

Of course, I uninstall it. But when I came back to the IDE again and try to figure out what was going wrong I didn't notice something wrong so I decided to try debugging the app but surprisly this time the debuger couldn't start, just throwing the following error:

42062-image.png

so I added a new app.manifest just in case and such could not solve this issue.
Hope you can help me with this since I can't figure out what's going wrong.

Thanks!

Windows Forms
Windows Forms
A set of .NET Framework managed libraries for developing graphical user interfaces.
1,836 questions
Visual Studio Debugging
Visual Studio Debugging
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Debugging: The act or process of detecting, locating, and correcting logical or syntactical errors in a program or malfunctions in hardware. In hardware contexts, the term troubleshoot is the term more frequently used, especially if the problem is major.
943 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Daniel Zhang-MSFT 9,616 Reputation points
    2020-11-24T06:36:02.193+00:00

    Hi PerezRE-2033,
    Based on the description of error, the cause is that application configuration is incorrect.
    >>The value "es-419" of the attribute "language" of the element "assemblyIdentity" is not valid.
    The languages supported by the configuration in the application are listed here, and “es-419" is not included.
    Besides, you mentioned that you have solved the issue by adding a new app.manifest.
    So what is included in your new app.manifest?
    I suggest you modify the supported language first.
    If not successful, please provide your application manifest.
    Best Regards,
    Daniel Zhang

    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.