This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 73%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPL%3C/text%3E%3C/svg%3E)
Hi there,
Since the last Visual Studio 2022 update, I've been having the error on my application and can't seem to make it disappear for some reason.
The error is pretty straight forward, it's missing a reference to Mvc.Razor version 2.2.0.0. So I've added it using NuGet, but no luck, I still get the same error. Does anyone know what's happening? Any help is appreciated, and I can provide other details if requested.
Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hi @Pier-Luc Allard , welcome to Microsoft Q&A forum. I think you can first try to clean NuGet cache and project cache(.vs/bin/obj folder), and then rebuild your project > restart Visual Studio > run your project again.
Thanks @Tianyu Sun-MSFT ! I just finished trying these steps, but no luck. The project builds successfully, but I still get this error when calling AddExtCore.
Hi @Pier-Luc Allard , I have done some tests, but I can’t reproduce this issue. I’m glad that you find that VS 2019 still works for you. And I’d like to continue investigating this issue. I’m not 100% sure whether this is a potential issue brings by the latest VS 2022 Updates, I suggest you also open a ticket on our Developer Community and attach some code snippets or a simple sample(if this issue is reproducible) to investigate further.
Regards,
Tianyu
As an alternate solution, I've installed VS 2019 and the problem does not happen. Something is definitely up with the newest VS 2022 update. I'm using .NET Core 2.2, but even if it's not supported, it shouldn't give me additional errors.