Installing VS 2022 on Win11 glitch

[mir2pion]

Installing VS 2022 on freshly installed win11, I selected the same three packages like last time when installing on win10 and there was this problem when it couldn't find the vc_runtimeMinimum_x86.msi file. I actually have that msi installer as you can see it located in the search window and I browsed to it but it didn't want that file (I tried both versions), so I had to cancel this request and the install ended with the warning below. Anyone has a clue what it is all about? Maybe I can just ignore it?

 

[mir2pion]

When compiling mir3d solution which I could compile before on win10 in VS 2022, now when I installed win11 and VS 2022 I get this error. What does that mean?

 

[Jev]

Try downloading the x64 version

 

[mir2pion]

You mean of the VS? I would have thought it would have been x64 program. I used the same installer as I did before.

But I tried in the same VS version but one that is running on different computer with win10 and I get the same error. I noticed it refers to the file in the solution properties, the screenshot tell it all. Is there something wrong with that code? I didn't touch it. And I just open the code I have compiled maybe a month ago and now when I just open it and do nothing with it, it won't compile.




I checked the two references and they points to AssemblyInfo.cs and RefSafetyRulesAttributes.cs


The assembly info looks like this.


And the RefSafetyRulesAttributes.cs is this. But this is the code I looked up the references from, in that first large screenshot above!


This is bizarre, that RefSafetyRulesAttributes.cs reference refers to itself! How is that possible? I didn't do anything to the code since I last compiled it and then uploaded for release here. It was that mir3D translated GUI. Now I open that code and try to compile it without any changes and it gives this error.

So the question now is, how to remove or cancel that one reference that refers back to its parent code block.

 

[Omnibus]

Try downloading the x64 version

x64 is the most recommended.

 

[Jev]

x64 is the most recommended.

That’s why I suggested it

 

[mir2pion]

This one runs on win10


This one is from win11 installed this Sunday. I see now that it has more updated components but that has nothing to do with it.


I am now trying to resolve that problem installing VS, did try updating it to an offered update and again it ran into that same problem, missing the right kind of vc_runtimeMinimum_x86.msi file. Likely it is a separate problem but who knows

 

[Omnibus]

This one runs on win10
View attachment 31050

This one is from win11 installed this Sunday. I see now that it has more updated components but that has nothing to do with it.
View attachment 31051

I am now trying to resolve that problem installing VS, did try updating it to an offered update and again it ran into that same problem, missing the right kind of vc_runtimeMinimum_x86.msi file. Likely it is a separate problem but who knows

Have you managed to resolve it?

You can google these missing files to assist yourself.

 

[Hercules]

You know what they say. If you find a mouse in your house there’s probably 29 more.

Can anyone spot the 6th one?

 

[mir2pion]

I am getting help from the place where I got my custom win11 but the problem is a wider one. If you search for it, you find it was reported by pple in 2018 and also last year with VS2022 installations, so my custom win11 is not the problem or doesn't have to be.

That problem with compiling mir3d exe might well be unrelated to the glitch during VS install. I was so disgusted with it that I didn't look at it again, but now that I slept on it, I will investigate if I can fix it.

 

[mir2pion]

Installed different Win11 and VS installed in it without a hitch but the problem with compiling is still there. As I suspected those were unrelated problems.

It baffles me no end, I did that mir3d server GUI translation only some weeks ago, compiled server and left compiled files in bin and rared up the source code to upload it for sharing and now I have problem compiling even when I get the source I uploaded.

How can a section of code reference back to itself. How do you remove such looping reference?

==============================
I reinstalled VS2019 since I think I did the last compile in that one. At the time I worked on the GUI translation, I have been moving to VS2022 but probably worked on that code still in the v2019

In VS 2019 that looping self referencing error is not present but it still won't compile. Now I have another bizarre error, it says something is wrong with the opening and closing brackets in the whole code. I opened fresh copy from the code I archived when I last compiled it.



Here are two .cs smaller code sections, where you can see the whole file content. If I understand what is wanted, there should be an opening curly brace before the 'namespace' and another closing bracket at the end of it. But how could they have gone missing? Another bizarre even, I am beginning to believe alien UFOs have landed here.