0

I have a project that has been compiling and building without errors in Visual Studio 2022 17.1. I recently upgraded to 17.2 and now the project fails without emitting any errors after compiling only 2 or 3 files. (The failure is not consistent as to which file fails.) I have changed the Tools->Options->Projects and Solutions->Build Options to display Diagnostic level messages. Still I get no error message.

Does anyone know how to discover what the error actually is?

Is there any way to fall back to 17.1?

UPDATE:

Yesterday I was able to get the project to build through some combination of the following (all of which I did):

  • Reinstall Visual Studio 2022
  • Delete .vs folders
  • Delete Release and Debug folders.

However today the problem has returned. I now realize that yesterday I was deleting .vs (which is on a network drive) from a different computer. Today I tried deleting .vs within Windows itself, and it refuses to allow it, saying it is in use by "ServiceHub.IndexingService.exe". This is when Visual Studio 2022 is not running. That service is not killable. I have tried deleting .vs. from the other computer as I did yesterday, but today it makes no difference.

There is a serious problem with 17.2. Is there any way to fall back 17.1? (I ask again.)

I have a "detailed" build log of the fail-without-error, but inserting it here far exceeds the character limit that Stack Overflow imposes on question text. I don't see anywhere to attach it, but I'll be happy to.

Meanwhile, here is a "normal" build log:

Build started...
1>------ Build started: Project: RGPLuaWin, Configuration: Release x64 ------
1>Build started 6/4/2022 11:03:29 AM.
1>Target ResolveProjectReferences:
1>  Target GetNativeManifest:
1>Target InitializeBuildStatus:
1>  Touching "Y:\RGPLua\RGPLuaWin\x64\Release\obj\RGPLuaWin.tlog\unsuccessfulbuild".
1>Target GetReferencedVCProjectsInfo:
1>Target ClCompile:
1>  All outputs are up-to-date.
1>  RGPLua.cpp
1>  RGPLuaConnector.cpp
1>  RGPLuaConnectorBase.cpp
1>  RGPLuaConnectorCell.cpp
1>  RGPLuaConnectorCharPrefs.cpp
========== Build: 0 succeeded, 1 failed, 2 up-to-date, 0 skipped ==========
rpatters1
  • 346
  • 1
  • 9
  • The "heap" space is limited to the size of your memory + swap/pagefile. It is very unlikely you are running out of heap space, especially considering VS2022 is all x64 now. You can change the platform toolset from 2022 to 2019 under the project properties (you will have to install the older toolset from the 2022 installer's components). With such limited information, you might be better off reporting to MS, and they can tell you how to enable dump files for VS, and you could upload that to them. – ChrisMM Jun 03 '22 at 14:39
  • Have you done a **Clean**? Might need to manually delete the intermediate and target files, if VS's **Clean** doesn't do the job. – Eljay Jun 03 '22 at 14:41
  • What you have described smells like visual studio installer failure. If you run it, do you see any error mark? – 273K Jun 03 '22 at 14:42
  • It simply stops and says the build fails: ========== Rebuild All: 3 succeeded, 1 failed, 0 skipped ========== – rpatters1 Jun 03 '22 at 14:51
  • Where would I see the error mark? I haven't noticed anything unusual. – rpatters1 Jun 03 '22 at 14:52
  • [Edit](https://stackoverflow.com/posts/72491200/edit) the question by adding this information to the question. The error mark is very noticeable in the main window of the running installer. – 273K Jun 03 '22 at 14:53
  • Clean does not help. Deleting intermediate and target files does not help. (I deleted the entire x64\Release folder.) – rpatters1 Jun 03 '22 at 14:55
  • Reinstall visual studio. – 273K Jun 03 '22 at 14:56
  • 2
    Please include the entire build log if possible. The error might be way above since the build is multithreaded. Also did you see these? [1](https://stackoverflow.com/questions/13239325/how-to-find-reason-of-failed-build-without-any-error-or-warning) [2](https://stackoverflow.com/questions/1319772/how-to-determine-why-visual-studio-might-be-skipping-projects-when-building-a-so) [3](https://stackoverflow.com/questions/18734044/rebuild-all-failed-with-0-errors-visual-studio-2012-c-sharp) – rustyx Jun 03 '22 at 14:59
  • It turns out that deleting the `.vs` folder for the *project* may have fixed my problem. At any rate it's working now. This was in one of the answers suggested by user 273K, though it took me a while to realize I needed to delete the one for the project rather than the one for the solution. – rpatters1 Jun 03 '22 at 21:19
  • You should post an answer to your question rather than put the answer in the question. Clearly it has nothing to do with heap allocation - asking about that makes this an X-Y problem. Besides heap is provided by the OS, and is not allocated as a fixed limit to the process (Visual Studio is not a Java app where that would be true). – Clifford Jun 03 '22 at 21:28
  • I would love to post an answer, but the question was prematurely closed. – rpatters1 Jun 05 '22 at 01:25

0 Answers0