Ultra - Release Mode Not Compiling

[SpiderPig]

Debug mode is fine, but none of my projects compile in Release mode at the moment.  I made a fresh project and that doesn't compile in Release mode either.  I'm using the latest update.  Apparently there is a version mismatch?

[Josh]

I'll have an update out soon...

[reepblue]

That's interesting. I compiled my TEX2TGA program just fine last night. I didn't update the project, I just recompiled it with the newest version of the libraries.

[Josh]

Just compiled a new project made with 1.0.2 and VS 17.5.5. Maybe you just need to clean the project so everything rebuilds, or update visual studio?

[SpiderPig]

This is with a new project as well as my old ones and VS is up to date.  I'll try a fresh install of Ultra.

[SpiderPig]

Did a fresh install of 1.0.2, created a new project, built in release and got the same error.  VS2022 is up to date.  v17.6.2?

 

Microsoft Visual Studio Community 2022
Version 17.6.2
VisualStudio.17.Release/17.6.2+33723.286
Microsoft .NET Framework
Version 4.8.04084

Installed Version: Community

Visual C++ 2022   00482-90000-00000-AA189
Microsoft Visual C++ 2022

 

[SpiderPig]

Still not compiling in Release with 1.0.3 by the way.  Not sure if you looked at this for that update.

[Josh]

I just copied the 1.0.2 folder on the server. Have no uploaded a new build yet, but I did update VS to the latest.

[reepblue]

I generated a new project tonight and it compiled fine. Then I updated Visual Studio to 17.6.2 and now I'm getting the same issue as SpiderPig. I tried deleting the .vs folder but that didn't work.

So yeah, Josh needs to update Visual Studio. for the next release. 

 

[Josh]

I'll have an update up shortly.

Apparently it is possible to roll back VS updates, but I don't know how?:
https://developercommunity.visualstudio.com/t/introduce-the-ability-to-roll-back-a-visual-studio/395028

It would be a good idea to find the answer, in case we ever experience anything like this again.

[SpiderPig]

I was wondering if that were possible.  I'll take a look at it.

[SpiderPig]

If you open the VS22 Installer the option to rollback is under the More tab.  I think you can open the installer from within Visual Studio by going to Tools->Get Tools and Features.

[Josh]

Fixed

[SpiderPig]

Hmm, that doesn't seem to have worked for me.    @reepblue  Did it work for you?

 

 

[Josh]

That is strange, I didn't even bother checking because it seemed so simple, but I get the same error with VS 17.6.2, on the same machine.

[reepblue]

Maybe check the SDK version? It seems this update was a big one as I got a popup telling me about all the new features I'll never use. (Besides Breakpoint groups)

[SpiderPig]

Have you managed to solve this yet? 

[Josh]

I'm thinking it might be caused by some library the engine is using not being compiled with same compiler....but that doesn't really make sense, because my own builds of the engine as an app would fail:
https://stackoverflow.com/questions/837073/error-c1047-object-file-created-with-an-older-compiler-than-other-objects

[SpiderPig]

That is odd.  I'll try rolling back a few updates for now.

[Josh]

I recompiled some of the libraries used and made sure "whole program optimization" was disabled. I don't know what exactly was the cause but it seems to work now.

[SpiderPig]

Confirming it's fixed.