Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding CopilotChat.sln #1885

Merged
merged 1 commit into from
Jul 7, 2023
Merged

Adding CopilotChat.sln #1885

merged 1 commit into from
Jul 7, 2023

Conversation

shawncal
Copy link
Member

@shawncal shawncal commented Jul 6, 2023

Copilot Chat's .net project builds, runs, works just fine when opened from the CopilotChatWebApi.csproj directly. Every time you open this project, however, VS kindly creates a new .sln for you and offers to save it.

This just creates a convenient .sln that one can open. This can also be used by dotnet format and build scripts. It contains just the one CopilotChatWebApi project right now, but it's placed in the copilot-chat folder so that additional projects (tests, extensions, etc.) could be added in the future.

@shawncal shawncal requested a review from a team as a code owner July 6, 2023 23:57
@shawncal shawncal added this pull request to the merge queue Jul 7, 2023
Merged via the queue into microsoft:main with commit 8d705b3 Jul 7, 2023
12 checks passed
@shawncal shawncal deleted the copilotchat-sln branch July 7, 2023 00:21
golden-aries pushed a commit to golden-aries/semantic-kernel that referenced this pull request Oct 10, 2023
Copilot Chat's .net project builds, runs, works just fine when opened
from the `CopilotChatWebApi.csproj` directly. Every time you open this
project, however, VS kindly creates a new .sln for you and offers to
save it.

This just creates a convenient .sln that one can open. This can also be
used by dotnet format and build scripts. It contains just the one
`CopilotChatWebApi` project right now, but it's placed in the
copilot-chat folder so that additional projects (tests, extensions,
etc.) could be added in the future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants