jnrtrinity.blogg.se - Advanced installer visual studio 2022

NETFramework,Version=v4.5.2,Set=Extensions,Hash=ADF899D7.dat NETFramework,Version=v4.5.2,Set=Extensions,Hash=72AE305.dat NETFramework,Version=v4.5.2,Set=Extensions,Hash=24CEEB0D.dat NETFramework,Version=v4.5,Set=Framework,Hash=5AE9A175.dat NETFramework,Version=v4.5,Set=Extensions,Hash=497525A2.dat NETFramework,Version=v4.5,Set=Extensions,Hash=75EAE334.dat NETFramework,Version=v4.0,Set=RecentAssemblies,Hash=0.dat NETFramework,Version=v4.0,Set=Framework,Hash=C958D412.dat Each was in my old copy, and not initially re-created when I re-launched VS: vspdmc.lock (overwrote the auto-generated copy with old).ApplicationPrivateSettings.lock (overwrote the auto-generated copy with old).ApplicationPrivateSettings (was in my old copy, not initially re-created when I re-launched VS).

These files were fine to move back in/overwrite the auto-generated ones: VTC (was in my old copy, not initially re-created when I re-launched VS, copied it back in).STemplate (was in my old copy, not initially re-created when I re-launched VS, copied it back in).

Notifications (overwrote the auto-generated copy with old).

ImageLibrary (overwrote the auto-generated copy with old).

Extensions (overwrote the auto-generated copy with old).

Designer (was in my old copy, not initially re-created when I re-launched VS, copied it back in).

1033 (overwrote the auto-generated copy with old).

So I moved everything back, one-by-one, and restarted Visual Studio each time until I discovered the culprits. For me, I initially moved the folder at C:\Users\\AppData\Local\Microsoft\VisualStudio to My Documents and allowed Visual Studio to re-create it by re-launching it. In the hopes it might narrow things down/help someone, I did an investigatory approach.