Upgrading Visual Studio 2019 to 2022

[Ochapparel]

nopCommerce version:
4.40

Steps to reproduce the problem:
Install Visual Studio 2022 Community
Open Nop Solution
Debug

Get this error:
https://www.nopcommerce.com/en/boards/topic/92619/error-method-clone-in-type-on-start-when-loading-some-plugins

[oyhan]

Seems there is a problem with the build operation.

[skoshelev]

I checked to build 4.40.4 on visual studio 2022, everything works without issue. Perhaps the problem is in local settings or temporary files. Try to close the studio and manually delete all bin and obj directories

Closed #5981

[oyhan]

@skoshelev Hi
BTW it's not a compile error it's a runtime error.
Continue to run the project with some plugins installed.

[skoshelev]

Sorry for misunderstanding, but I may run nopCommerce 4.40.4 from the visual studio 2020 without problem too

[oyhan]

Unfortunately it's not happening all the time. For me after couple of stop/starting project during the development showed up and I had to switch to vs2019 and rebuild solution and run again.
Can you just rebuild a existing plugin in the project and then again start the web project? because it's just my routine

[skoshelev]

You know, it looks like there really is some kind of problem in visual studio 2022, I once managed to reproduce the problem, but after repeating the same actions, the problem is just gone. Anyway, a complete rebuild of the solution works well, so it looks like there is a problem not with our code.

[oyhan]

Absolutely it's not from the code. As I mentioned before there is something wrong with build operation in vs22 and just revealed in the Nop project in some circumstances. And I must add it may be something related to record types.

[Ochapparel]

I deleted the Bin and the Obj folder. Did a whole rebuild and still same error when "debugging"

@skoshelev anyone else on the nop team able to try 2022? Not a big issue to use 2019, it's just a very strange error

[joekrauss]

NopCommerce works fine with VS2022 however, all assemblies including 3rd party plugins have to be compiled under VS2022 to work properly. If one plugin or assembly is not compiled with VS2022 you will get errors like "not compatible with base type method 'Nop.Web.Framework.Models.BaseNopEntityModel.$()'.". I wish I had more time to investigate the cause, but from what I see the VS2022 compiled version is different in size than when compiled under VS2019.

[eplsoftware]

will the new version 4.50 now be compiled with Visual Studio 2022 or with version 2019? It should be version 2022 so there is no mess.

[Ochapparel]

Agreed. And maybe a communication to the 3rd party plugins to compile in 2022

[Ochapparel]

How is the new bath compiled? 2019?

[eplsoftware]

Version 4.40 and all plug-ins with Visual Studio 2019 and version 4.50 and all plug-ins with Visual Studio 2022.

[Ochapparel]

Great. Maybe make that communication make to everyone. Especially 3rd party plugins.

[oyhan]

For all people like me still has the problem try to install the latest dotnet 5 sdk
My problem went out.

[yashobanta999]

hii! Can i upgrade from 2019 to 2022 studio directly from 2019 version or i have to download the 2022 version separately

[glhays]

Download VS2022 and install it. If your 2019 is a licensed version check your account for upgrade options.
NopCommerce website provides the requirements needed for versions of its software. 4.40 and earlier VS2022 or earlier, 4.50 requires VS2022.

[serkandede]

Hi, i have same issue with a little bit different environment.
We are running Nop 4.40 in VS Code on mac computer. Everything is perfect without third party libraries.

But when we added third party plugins (Nop-Templates Plugins, we dont have source code to rebuild) :

• project build succesfully.
• it is runtime error
• third party dlls caused the same issue (Nop-Templates's plugin dlls)

[glhays]

Your nop template plug-in folders are not source code they are compiled by nop templates. They should only be placed in the plug-ins folder of the Nop.web project not in the nopcommerce plug-ins folder that gets compiled with the nop source code. Check your nop template account for updated theme files for the version of nopcommerce your running and add them. VS2019 and 2022 are standalone, so you do have to install separately. You can run them side by side and the visual studio installer manages the versions on your machine.

…

________________________________ From: Serkan Dede ***@***.***> Sent: Friday, February 25, 2022 10:44:38 AM To: nopSolutions/nopCommerce ***@***.***> Cc: Gregory Hays ***@***.***>; Comment ***@***.***> Subject: Re: [nopSolutions/nopCommerce] Upgrading Visual Studio 2019 to 2022 (Issue #5981) Hi, i have same issue with a little bit different environment. We are running Nop 4.40 in VS Code on mac computer. Everything is perfect without third party libraries. But when we added third party plugins (Nop-Templates Plugins, we dont have source code to rebuild) : * project build succesfully. * it is runtime error * third party dlls caused the same issue (Nop-Templates's plugin dlls) — Reply to this email directly, view it on GitHub<#5981 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKD4KO2BXBUFKMYV2CGRDV3U47EZNANCNFSM5JISCKQQ>. You are receiving this because you commented.Message ID: ***@***.***>