vs2019 error content: The Designtime
configuration of "Debug|Win32" failed to generate. IntelliSense may not be available
Error content
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
设置环境变量 TRACEDESIGNTIME = true 并重启 Visual Studio 以进行调查。
Find errors
So, according to the prompt in the error report, add the environment variable TRACEDESIGNTIME = true, reopen the visual studio project, and get the following result
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
错误 : 项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”配置“Debug|Win32”的 Designtime 生成失败。IntelliSense 可能不可用。
检查 %TEMP% 目录中的 *.designtime.log 文件。
Here is a question, how do I know where %TEMP% is? I usually do this at the command prompt.
C:\Users\Administrator>%temp%
'C:\Users\ADMINI~1\AppData\Local\Temp' 不是内部或外部命令，也不是可运行的程序
或批处理文件。As you can see, %TEMP% turned out to be this folder, C:\Users\Administrator\AppData\Local\Temp (differs according to the user name), and then, according to the prompts, I found these files under it, and I calculated it. , Probably each of the above corresponds to 4 such files, there are a lot of them in total:
(The file name is a long string of numbers).designtime.log
Just open one of them, pull it all the way back, and look at the place where the error is reported. The content is roughly as follows,
__________________________________________________
项目“D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj”(GetProjectDirectories 个目标):
正在使用工具版本“Current”进行生成。
D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj(55,5): error MSB4019: 找不到导入的项目“C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.0.props”。请确认 Import 声明“C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.0.props”中的表达式正确，且文件位于磁盘上。
已完成生成项目“darknet.vcxproj”的操作 - 失败。
项目评估性能摘要:
0 毫秒 D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj 1 次调用
项目性能摘要:
1 毫秒 D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj 1 次调用
生成失败。
D:\mTensorflow\yolov4_darknet-master\build\darknet\darknet.vcxproj(55,5): error MSB4019: 找不到导入的项目“C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.0.props”。请确认 Import 声明“C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.0.props”中的表达式正确，且文件位于磁盘上。
0 个警告
1 个错误
已用时间 00:00:01.77
Prompt that the project cannot be found, and ask to confirm that the expression in the Import statement "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.0.props" is correct,
Handling errors
Next, open the following folder to take a look,
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\BuildCustomizations\
I found that there is no CUDA 10.0.props file, but there is CUDA 10.1.props (this is the version I use);
Then, open darknet.vcxproj with Notepad, all CUDA 10.0.props in it are replaced with CUDA 10.1.props, the problem is solved.
to sum up
The error is caused by a path error. As for which path is wrong, you need to deal with it according to your own project. Basically according to the method mentioned above, step by step, you should be able to locate the wrong location quickly.
Other references
In addition, there is such a paragraph on Microsoft's official website, but it was a software bug at the time. Now in VS2019, if this error occurs, it is generally a problem with the path.
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.
Solutions
Microsoft 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, please report 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