2

I'd like to stop this error appearing in the Intellisense section in the Output window in Visual Studio: [Failure] Could not find file 'C:\code\CatApp\obj\x86\Debug\App.g.i.cs'.

I've cleared obj and bin folders, upgraded to the latest version of Visual Studio 2017,cleared all nuget packages and checked my project out from SVN again.

I get the same problem if I create a new UWP project. (Every time I create a new UWP project, I have to get the Nuget package Microsoft.NETCore.UniversalWindowsPlatform separately. I'm wondering if the two problems could be related.)

My target and min version are 16299.

Gail Foad
  • 623
  • 10
  • 22
  • 1
    https://stackoverflow.com/questions/35259603/g-i-cs-files-missing-classes-no-longer-contain-a-definition-for-initializecompo ? –  Mar 05 '18 at 15:19
  • 1
    Well, related, when Nuget can't retrieve the package by itself then IntelliSense is doomed as well. You'll need to dig up a diagnostic to get ahead, look in the Output window and switch "Show output from" to Package Manager to get the Nuget download trace. – Hans Passant Mar 05 '18 at 15:45
  • Could you please add the version of visual studio you are using as well as the version of UniversalWindowsPlatform I ran into a problem similar to this if my univsersal windows platform was not set to 5.2 and using Visual Studio 2015 Service pack 3. – Stuart Smith Mar 05 '18 at 23:12
  • 1
    I would suggest trying to repair whole Visual Studio. It is very unusual for this to happen with blank app. – Martin Zikmund Mar 06 '18 at 08:52
  • I'm running 15.5.7+27130.2036 – Gail Foad Mar 06 '18 at 09:07
  • UniversalWindowsPlatform is now being automatically added to new projects. I repaired VS, decided on Windows Version 14393 and UniversalWindowsPlatform 6.0.8 that I'll stick to, then cleared all Nuget caches. The output window is still complaining about missing *.g.i.cs files though :( – Gail Foad Mar 06 '18 at 11:34
  • I cleared ShadowCache in %localappdata%\Microsoft\VisualStudio\15.0_9dbf4983\Designer. I thought this had fixed it, but it hasn't. – Gail Foad Mar 06 '18 at 13:07
  • This is still a problem for me on `VisualStudio.16.Preview/16.4.0-pre.1.0+29319.158`. – lit Oct 03 '19 at 12:44

0 Answers0