TOPIC:

I have a web application based on aspx pages and dlls written in X#, the pages contain Javascript.
I write the X# code using XIDE and at the end of the debug compilation copy dll, pdb and prg in the bin folder of the site.
The main folder of the site contains the aspx page and then other html files, etc ..
I use Visual Studio for debugging my application.
With Visual Studio 2019 I regularly start the website and debug without problems.
With Visual Studio 2022 the compilation of the site starts but does not end by reporting errors that I do not understand and I am attaching.
I repeat as said with Visual Studio 2019 everything works wonders.

Thank you

Danilo

Danilo,

You did not attach screenshots or errors you have encountered.

Jamal

Yes, you're right, but I add two jpg files, but then when I send them I can't find them anymore, I don't know what to do .....

Danilo

Danilo,

Maybe you can send the error messages as text? Just select all the errors with CTRL+A, press CTRL+C to copy them and paste them here in your message.

.

Nothing, does not load

Guys,

Here are the images with the error messages from Danilo's PC:

www.dropbox.com/s/vg413m4w9ti197e/error1.jpg?dl=0

www.dropbox.com/s/86jxyna2du80mep/error2.jpg?dl=0

I have changed a setting on the webserver and could now insert the images again.

Robert

Thank's Robert

Thank's Chris.
As I said, the application started by VS 2019 starts and works perfectly, the same application started by VS 2022 randomly generates these two errors.
These are errors that apparently make no sense as: the "AcquireStamp" assembly is contained in the AcquireStamp.dll dll, and the dll is present in the BIN folder. For the error: Reference to an object not set on an object instance, there is no indication and then I repeat: a VS 2019 this error is not generated.

Danilo

Danilo
A complete guess - BIN Folder Release? Debug?

Terry

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

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


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

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

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

Danilo