From 5c3ef3eef8a0ba8570a5c645506b1c9b27543329 Mon Sep 17 00:00:00 2001
From: Darren Cohen <39422044+dargilco@users.noreply.github.com>
Date: Wed, 25 Mar 2026 08:47:03 -0700
Subject: [PATCH 1/2] First

---
 sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md | 28 +++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md

diff --git a/sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md b/sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md
new file mode 100644
index 000000000000..01a1a0659d3a
--- /dev/null
+++ b/sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md
@@ -0,0 +1,28 @@
+# Development Guide
+
+## Emitting code from TypeSpec
+
+For the time being, we have to emit using this dev version package: `"@azure-tools/typespec-client-generator-core": "0.67.0-dev.12"`,
+
+The normal way to emit SDK using a dev package would be:
+1. Go to `eng` folder in your azure-sdk-for-python clone.
+1. Edit `emitter-package.json` to update the version of package `@azure-tools/typespec-client-generator-core`
+1. Run `tsp-client generate-lock-file`. This should create the file `emitter-package-lock.json`.
+1. Go to `sdk\ai\azure-ai-projects` and emit SDK as usual.
+
+However, generating the lock file results in an error from a conflict resolving dependencies. That error should go away when the package is published as a major version instea of dev version.
+
+The work around is the following:
+1. In `sdk\ai\azure-ai-projects`, update the commit number in `tsp-location.yaml`
+1. In that folder run `tsp-client sync`. This extracts the relevant TypeSpec souce code (for the particular commit) and copies it to the local folder `TempTypeSpecFiles`.
+1. Cd to TempTypeSpecFiles folder
+1. Copy `eng\emitter-package.json` as `package.json` in this folder
+1. Edit `package.json` to update relevant package version
+1. Run `npm install --legacy-peer-deps`. Then run `npm list` to make sure correct versions were installed.
+1. Cd back up to folder `src\azure-sdk-for-python`, and run `tsp-client generate --save-inputs --skip-install`. This will emit code using already installed packages and the local TypeSpec files.
+
+
+
+
+
+

From 33ebc90750b18e55b277303a4943d95049f3ab29 Mon Sep 17 00:00:00 2001
From: Darren Cohen <39422044+dargilco@users.noreply.github.com>
Date: Wed, 25 Mar 2026 09:10:19 -0700
Subject: [PATCH 2/2] +

---
 sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md b/sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md
index 01a1a0659d3a..e847724694eb 100644
--- a/sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md
+++ b/sdk/ai/azure-ai-projects/DEVELOPMENT_GUIDE.md
@@ -21,6 +21,13 @@ The work around is the following:
 1. Run `npm install --legacy-peer-deps`. Then run `npm list` to make sure correct versions were installed.
 1. Cd back up to folder `src\azure-sdk-for-python`, and run `tsp-client generate --save-inputs --skip-install`. This will emit code using already installed packages and the local TypeSpec files.
 
+## Running post-processing
+
+After emitting code from TypeSpec, you must run the script `post-emitter-fixes.cmd`
+
+## Troubleshooting
+
+Set this environment variable to get console logs of all network calls (AIProjectClient and OpenAI clients): `set AZURE_AI_PROJECTS_CONSOLE_LOGGING=true`