Skip to main content
added 33 characters in body
Source Link
mr12086
  • 121
  • 3

On a newly created project, opening a C# script via double clicking it won't correctly load VSCode's extensions. (this is due to parts of the sln file not being generated.)

GoingCreate at least one C# script, then go to 'Assets' > 'Open C# Project' generateswill generate the correct sln file and after a quick reload of VSCode, intellisense starts working.

After doing this one time, intellisense will continue to work as expected, double clicking C# scripts etc.

On a newly created project, opening a C# script via double clicking it won't correctly load VSCode's extensions. (this is due to parts of the sln file not being generated.)

Going to 'Assets' > 'Open C# Project' generates the correct sln file and after a quick reload of VSCode, intellisense starts working.

After doing this one time, intellisense will continue to work as expected, double clicking C# scripts etc.

On a newly created project, opening a C# script via double clicking it won't correctly load VSCode's extensions. (this is due to parts of the sln file not being generated.)

Create at least one C# script, then go to 'Assets' > 'Open C# Project' will generate the correct sln file and after a quick reload of VSCode, intellisense starts working.

After doing this one time, intellisense will continue to work as expected, double clicking C# scripts etc.

added 32 characters in body
Source Link
mr12086
  • 121
  • 3

On a newly created project, opening a C# script via double clicking it won't correctly load VSCode's extensions. (this is due to parts of the sln file not being generated.)

Going to 'Assets' > 'Open C# Project' generates the correct sln file and after a quick reload of VSCode, intellisense starts working.

After doing this one time, intellisense will continue to work as expected, double clicking C# scripts etc.

On a newly created project, opening a C# script via double clicking it won't correctly load VSCode's extensions. (this is due to parts of the sln file not being generated.)

Going to 'Assets' > 'Open C# Project' generates the correct sln file and intellisense starts working.

After doing this one time, intellisense will continue to work as expected, double clicking C# scripts etc.

On a newly created project, opening a C# script via double clicking it won't correctly load VSCode's extensions. (this is due to parts of the sln file not being generated.)

Going to 'Assets' > 'Open C# Project' generates the correct sln file and after a quick reload of VSCode, intellisense starts working.

After doing this one time, intellisense will continue to work as expected, double clicking C# scripts etc.

Source Link
mr12086
  • 121
  • 3

On a newly created project, opening a C# script via double clicking it won't correctly load VSCode's extensions. (this is due to parts of the sln file not being generated.)

Going to 'Assets' > 'Open C# Project' generates the correct sln file and intellisense starts working.

After doing this one time, intellisense will continue to work as expected, double clicking C# scripts etc.