You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using the Get Started link from the SK Tools in VSCode, I created a new app and selected Console Chat. This got the required files for running the sk-csharp-hello-world starter project but hitting F5 fails due to the tasks.json referencing sk-csharp-hello-world.sln which does not exist.
To Reproduce
Steps to reproduce the behavior:
Go to Helpful Links -> Get Started from the Semantic Kernal VSCode Extension
Click on 'Create a new App'
Select 'C# Console App' (select a folder and let it setup the files)
Hit F5 to build, run, debug the app
See error in terminal:
MSBUILD : error MSB1009: Project file does not exist.
Switch: C:\Dev\SK\Scratch\ConsoleChat\sk-csharp-console-chat/sk-csharp-console-chat.sln
Expected behavior
App should build, run and enter debug
Desktop (please complete the following information):
OS: Windows
IDE: VS Code
Additional context
This can be fixed by editing the tasks.json to reference the sk-csharp-hello-world.proj project file rather than the sln file that doesn't exist.
I will open a PR to address this soon.
The text was updated successfully, but these errors were encountered:
Describe the bug
Using the Get Started link from the SK Tools in VSCode, I created a new app and selected Console Chat. This got the required files for running the sk-csharp-hello-world starter project but hitting F5 fails due to the tasks.json referencing sk-csharp-hello-world.sln which does not exist.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
App should build, run and enter debug
Desktop (please complete the following information):
Additional context
This can be fixed by editing the tasks.json to reference the sk-csharp-hello-world.proj project file rather than the sln file that doesn't exist.
I will open a PR to address this soon.
The text was updated successfully, but these errors were encountered: