Error reported by vs2019: failed to generate designtime for “debug| Win32” configuration. IntelliSense may not be available

Time:2020-9-23

Vs2019 error report content:
Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available

Error content

Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Set the environment variable tracedesignime = true and restart visual studio to investigate.

check for errors

Therefore, according to the prompts in the error report, add the environment variable tracedesignime = true, re open the visual studio project, and get the following results

Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.
Error: Project “D: \” mtensorflow \ \ yolov4_ darknet-master\build\darknet\ darknet.vcxproj ”Failed to configure designtime generation for ‘debug| Win32’. IntelliSense may not be available.
Check the *. In the% temp% directory designtime.log Documents.

Here’s a problem. How do I know where% temp% is? I usually do this from the command prompt,

C:\Users\Administrator>%temp%
‘C: ﹣ users \ \ admin ~ 1 \ \ appdata \ \ local \ \ temp’ is not an internal or external command, nor a runnable program
Or batch file.

You can see that% temp% is originally this folder, which varies according to the user name. Then, according to the prompt, find these files under it. I calculated that each item above corresponds to 4 such files. There are a lot of them

The file name is a long string of numbers designtime.log

Open one of them casually and pull it back all the time. The contents are as follows:,

Project “D: mtensorflow / yolov4″_ darknet-master\build\darknet\ darknet.vcxproj ”(getprojectdirectories target (s)):

Building using tool version ‘current’.
D:\mTensorflow\yolov4_ darknet-master\build\darknet\ darknet.vcxproj (55,5): error msb4019: unable to find the imported project “C: program files (x86) – Microsoft Visual Studio / 2019 / community / msbuild / Microsoft / VC / v160 / buildcustomizations / CUDA 10.0. Props”. Please confirm that the expression in the import declaration “C: program files (x86) – Microsoft Visual Studio / 2019 / community / msbuild / Microsoft / VC / v160 \ \ buildcustomizations / CUDA 10.0. Props” is correct and the file is on disk.

Finished building project“ darknet.vcxproj ”Operation of – failed.

Project evaluation performance summary:
0 ms D: mtensorflow / yolov4_ darknet-master\build\darknet\ darknet.vcxproj 1 call

Project performance summary:
1 ms D: mtensorflow / yolov4_ darknet-master\build\darknet\ darknet.vcxproj 1 call

Build failed.

D:\mTensorflow\yolov4_ darknet-master\build\darknet\ darknet.vcxproj (55,5): error msb4019: unable to find the imported project “C: program files (x86) – Microsoft Visual Studio / 2019 / community / msbuild / Microsoft / VC / v160 / buildcustomizations / CUDA 10.0. Props”. Please confirm that the expression in the import declaration “C: program files (x86) – Microsoft Visual Studio / 2019 / community / msbuild / Microsoft / VC / v160 \ \ buildcustomizations / CUDA 10.0. Props” is correct and the file is on disk.
0 warnings
1 error

Time used 00:00:01.77

You are prompted that the project cannot be found. You are required to confirm that the expression in the import declaration “C: program files (x86) – Microsoft Visual Studio / 2019 / community / msbuild / Microsoft / VC / v160 / buildcustomizations / CUDA 10.0. Props” is correct,

Processing error

Next, open the folder below and have a look,

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\BuildCustomizations\

It is found that CUDA 10.0.props does not exist, but CUDA 10.1.props (this is the version I use);

Then, open it in Notepad darknet.vcxproj All CUDA 10.0.props are replaced by CUDA 10.1.props, and the problem is solved.

summary

The error is caused by a path error. As to which path is wrong, you need to handle it according to your own project. Basically, according to the method mentioned above, step by step, we should be able to locate the wrong position quickly.

Other references

In addition, there is such a paragraph on Microsoft’s official website, but it was a software bug at that time. In the current vs2019, if this error occurs, it is generally that there is a problem with the path

https://developercommunity.visualstudio.com/content/problem/776877/error-designtime-build-failed-for-project-cuserstc.html

error : Designtime build failed for project ‘C:\Users\tcjso\source\repos\MazeProgram\MazeProgram\MazeProgram.vcxproj’ configuration ‘Debug|Win32’. IntelliSense might be unavailable. Set environment variable TRACEDESIGNTIME = true and restart Visual Studio to investigate.

Closed – Fixed fixed in: visual studio 2019 version 16.4visual studio 2019 version 16.3windows 10.0Fixed In: Visual Studio 2019 version 16.4 Preview 4

Timothy C. Johnson Software Author reported Oct 15, 2019 at 01:31 AM

[regression] [worked-in:Don’t know – the one B4 latest update.] I got this error opening a project I was working on after the latest VS update:error : Designtime build failed for project ‘C:\Users\tcjso\source\repos\MazeProgram\MazeProgram\MazeProgram.vcxproj’ configuration ‘Debug|Win32′. IntelliSense might be unavailable. Set environment variable TRACEDESIGNTIME = true and restart Visual Studio to investigate.Seems to have several of them.Thanks,Tim

Show comments 6

This issue is read only, because it has been in Closed–Fixed state for over 90 days. It was closed for 234 days.

SolutionsMicrosoft Solution

by Visual Studio Feedback System Nov 14, 2019 at 09:19 AM

Changed state ➜ Closed – Fixed

A fix for this issue has been released! Install the most recent release from https://visualstudio.microsoft.com/downloads/ . Thank you for providing valuable feedback which has helped improve the product.

This issue has been closed for over 90 days. If we haven’t resolved this issue for you, pleasereport a new problem

Yes, it worksFixed with no extra steps0 No, I tried everythingPlease re-open this0

Solution

by Timothy C. Johnson Software Author Oct 21, 2019 at 02:55 AM

I have REPAIRED Visual Studio with VSI and the problems are not showing up anymore.Thanks,Tim

summary

Here is the article about vs2019 reporting error: configuring “debug| Win32” designtime generation failure, IntelliSense may not be available. For more information about vs2019 reporting error configuration of “debug| Win32” designtime generation failure content, please search the previous articles of developeppaer or continue to browse the related articles below. I hope you can support developpaer more in the future!