Successfull Install but No Sample Code Builds on Visual Studio 2017

Been having a ton of issues getting CUDA and CUDNN to work as a windows user. Had a lot of Visual Studio Integration failures until I followed the tips by orangeduckman below

When I go into any of the sample projects in the simple folder none of them fail to build. I get the following errors listed in each of the files. Would love some help as this is preventing me from getting any of my masters research done. This is on a windows 10 machine with a gtx 1080, let me know if there is any other useful information I could provide.

-------->ERROR 1
–>CODE : c1189
–>FILE : host_config.h

Error C1189 #error: – unsupported Microsoft Visual Studio version! Only the versions 2012, 2013, 2015 and 2017 are supported! cdpSimpleQuicksort c:\program files\nvidia gpu computing toolkit\cuda\v9.0\include\crt\host_config.h 133

-------->ERROR 2
–>CODE : MSB3721
–>FILE : CUDA 9.0targets

Error MSB3721 The command ““C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0\bin\nvcc.exe” -gencode=arch=compute_35,code=“sm_35,compute_35” -gencode=arch=compute_37,code=“sm_37,compute_37” -gencode=arch=compute_50,code=“sm_50,compute_50” -gencode=arch=compute_52,code=“sm_52,compute_52” -gencode=arch=compute_60,code=“sm_60,compute_60” -gencode=arch=compute_70,code=“sm_70,compute_70” --use-local-env --cl-version 2017 -ccbin “C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX86\x64” -x cu -rdc=true -I./ -I…/…/common/inc -I./ -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0/include” -I…/…/common/inc -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0\include" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0\include" -G --keep-dir x64\Debug -maxrregcount=0 --machine 64 --compile -cudart static -Xcompiler “/wd 4819” -g -DWIN32 -DWIN32 -D_MBCS -D_MBCS -Xcompiler “/EHsc /W3 /nologo /Od /FS /Zi /RTC1 /MTd " -o x64/Debug/ “C:\ProgramData\NVIDIA Corporation\CUDA Samples\v9.0\0_Simple\cdpSimplePrint\”” exited with code 2.

Hi, Did you try to updata Vistual Studio 2017?