Граф коммитов

5 Коммитов

Автор SHA1 Сообщение Дата
Igor Velikorossov 49ec0031eb Fix VS experience (#4007)
#3998 has regressed VS experience due to changed packageContent.targets,
that no longer could resolve $(IntellisenseXml) variable.
This prevented VS from resolving tooling and dependnecies.
To fix this move all properties within `GetPackageContent` target.

Also run `restore.cmd` before launching VS. This is reqired to ensure
the intellisense bundle, as well as all required SDK and tooling are
downloaded.
This streamlined the DevEx.

Relates to #3998
2020-09-25 10:08:35 -05:00
Jeremy Kuhne e2ccd96a21
Another incremental improvement (#3499)
Don't want to lock the current command prompt.
2020-06-23 22:10:54 +00:00
Jeremy Kuhne 0f90af477f
Fix start-vs.cmd (#3458)
After repaving I discovered my previous changes weren't correct.
You can't check exists on partial paths. Quoting was wonky, etc.

I've tested this one thoroughly for all three handled states and
it appears to work fine.
2020-06-17 11:17:32 +10:00
Jeremy Kuhne 312a32d8e4 Update start-vs.cmd to use current VS
Use the developer command prompt VS if available, fall back on devenv
in the path, then finally to file association for .sln.

Normalize casing of the commands.
2020-06-11 14:18:40 -07:00
Igor Velikorossov c517fac6ad
Add local dev convenience scripts (#3389) 2020-06-04 13:51:06 +10:00