Free vs. Pro: Does Paid GitHub Copilot Agent Chat Improve C# API Builds? 

GitHub Copilot Agent Mode Prompt

## AI Agent Prompt: Deck of Cards API with .NET 8 and MS SQL

**Objective:**
Build a .NET 8 API application (C#) that simulates a deck of cards, using a local MS SQL database for persistence. The solution folder should be named `DeckOfCards`. Before coding, generate and present a detailed project outline for review and approval.  Once the plan is approved, do not request additional approvals. Proceed to create all required items without interruption, unless an explicit approval is essential for compliance or technical reasons. This ensures a smooth, uninterrupted workflow.

---

### 1. Project Outline

* Create an outline detailing each step to build the application, covering data modeling, API design, error handling, and testing.
* Pause and present the outline for approval before proceeding. No further review is required after approval.
* If you encounter any blocking issues during implementation, stop and document the issue for review.

---

### 2. SQL Data Model

* Design an MS SQL data model to manage multiple unique decks of cards within a `DeckOfCards` database (running locally).
* The model must support:

  * Tracking cards for each unique deck.
  * Creating a new deck (with a Deck ID as a GUID string without dashes).
  * Drawing a specified number of cards from a deck.
  * Listing all unused cards for a given deck, with a count of remaining cards.
* Treat Deck IDs as strings at all times.
* Define any variables within the relevant stored procedure.
* Enforce robust error handling for cases such as invalid Deck IDs or attempts to draw more cards than remain.
* Return detailed error messages to the API caller.
* Apply SQL best practices in naming, procedure structure, and artifact organization.
* Atomatically create and deploy the database and scripts using the local SQL server. Create the database called DeckOfCards in Server Localhost, then create the tables and procedures.  Otherwise, provide a PowerShell script to fully create the database, tables, and procedures.


---

### 3. API Layer

* Create a new API project with the following endpoints, each with comprehensive unit tests (covering both positive and negative scenarios) and proper exception handling:

  * **NewDeck** (GET): Returns a new DeckGuid (GUID string without dashes).
  * **DrawCards** (POST):

    * Inputs: DeckGuid and NumberOfCards as query parameters.
    * Output: JSON array of randomly drawn cards for the specified deck.
  * **CardsUsed** (GET):

    * Input: DeckGuid as a query parameter.
    * Output: JSON array of cards remaining in the deck, including the count of cards left.
* Implement the API using C#, connecting to SQL in the data layer for each method.
* Inside the Tests project, generate unit tests for each stored procedure
    * Make sure to check for running out of cards, not able to draw anymore cards, and invaid Deck ID.  Create a case for each of these.
* Inside the Tests project, generate unit tests for each API methods.

---

### 4. Application Configuration and Best Practices

* Update the `.http` file to document the three new APIs. Remove any references to the default WeatherForecast API.
* Ensure the APIs are configured to run on HTTP port 5000. Include a correct `launchSettings.json` file.
* Update `Program.cs` for the new API, removing all WeatherForecast-related code.
* Use asynchronous programming (`async/await`), store connection strings securely, and follow .NET and C# best practices throughout.

---

**Note:**
If you cannot complete a step (such as database deployment), clearly document the issue and provide a workaround or an alternative script (e.g., PowerShell for setup).
Once complete, run all unit tests to ensure everything is working.  
Postman will be used for testing.  Provide a inport file to be used with PostMan to test each of the three APIs.  Ensure to use the HTTP endpoint.