Visual Studio 2022

softdevo@tiscali.it · Post by **softdevo@tiscali.it** » Tue Dec 21, 2021 5:30 pm

By doing various tests I realized one thing:
premise: my application consists of 23 dlls.
Visual studio when starting debugging tells me that it cannot load the acquirestamp assembly.
If I replace the acquirestamp.dll and acquirestamp.dbg files taken in the debug folder for project Xide with the acquirestamp.dll file from the relesase folder, the assembly is loaded, but it tells me that it cannot load the next assembly, I also replace this and the message moves to the third assembly and so on.
It would appear that it does not recognize assemblies compiled with the debug option as valid, but only those compiled with the release option.

Danilo

fxm · Post by **fxm** » Wed Dec 22, 2021 11:50 am

Whenever I've seen the "Not in the correct format" error it's generally to do with bitness.

Presumably you have some dlls that are x86?

IIS Express by default runs in x64 mode in VS2022 - but you can turn it off
Tools -> Options -> Search iis and untick the option

: xyxddmK2QE.png (20.64 KiB) Viewed 190 times

Alternatively you can turn it off on a project by project basis

: Ml0MpOl1Il.png (75.87 KiB) Viewed 190 times

softdevo@tiscali.it · Post by **softdevo@tiscali.it** » Wed Dec 22, 2021 1:58 pm

Thanks, set IIS Express as you suggested now my application starts, but only the first time, then it keeps giving the error you see in error2.jpg,
If you see error1.jpg (how a page looks in VS2019) and error3.jpg the same page in VS 2022.
In error4.jpg a recurring error.
Maybe the problem lies in the fact that VS2022 necessarily wants dlls compiled with Net Framework 4.8?

Danilo

: error2.jpg (98.97 KiB) Viewed 190 times

: error4.jpg (91.61 KiB) Viewed 190 times

: error3.jpg (71.55 KiB) Viewed 190 times

: error1.jpg (66.17 KiB) Viewed 190 times

softdevo@tiscali.it · Post by **softdevo@tiscali.it** » Wed Jan 05, 2022 3:42 pm

Here's how I set up Visual Studio 2022 to debug my web application

Danilo