From 6cfe39684cf8d76e54e12da8dc4bfec4e6507f24 Mon Sep 17 00:00:00 2001
From: Manikanda Akash M - SF4236 <manikandaakash.m@syncfusion.com>
Date: Tue, 25 Nov 2025 10:43:32 +0530
Subject: [PATCH] EXT-212400 committed debugging steps java, python, c#, php,
 powershell in source

---
 code-studio-toc.html                          |  22 +
 .../languages/common-debugging-steps.md       |  91 ++++
 .../languages/csharp-debugging-guide.md       | 220 ++++++++
 code-studio/languages/java-debugging-guide.md | 173 +++++++
 code-studio/languages/php-debugging-guide.md  | 476 ++++++++++++++++++
 .../languages/powershell-debugging-guide.md   | 206 ++++++++
 .../languages/python-debugging-guide.md       | 210 ++++++++
 7 files changed, 1398 insertions(+)
 create mode 100644 code-studio/languages/common-debugging-steps.md
 create mode 100644 code-studio/languages/csharp-debugging-guide.md
 create mode 100644 code-studio/languages/java-debugging-guide.md
 create mode 100644 code-studio/languages/php-debugging-guide.md
 create mode 100644 code-studio/languages/powershell-debugging-guide.md
 create mode 100644 code-studio/languages/python-debugging-guide.md

diff --git a/code-studio-toc.html b/code-studio-toc.html
index e2f00ef..ee600dd 100644
--- a/code-studio-toc.html
+++ b/code-studio-toc.html
@@ -164,6 +164,28 @@
         </ul>
     </li>
     <li> <a href="/code-studio/ui-builder">UI Builder</a> </li>
+        <li>Languages
+        <ul>
+            <li>
+                <a href="/code-studio/languages/csharp-debugging-guide">C Sharp Development and Debugging Setup</a>
+            </li>
+            <li>
+                <a href="/code-studio/languages/java-debugging-guide">Java Development and Debugging Setup</a>
+            </li>
+            <li>
+                <a href="/code-studio/languages/php-debugging-guide">PHP Development and Debugging Setup</a>
+            </li>
+            <li>
+                <a href="/code-studio/languages/powershell-debugging-guide">PowerShell Development and Debugging Setup</a>
+            </li>
+            <li>
+                <a href="/code-studio/languages/python-debugging-guide">Python Development and Debugging Setup</a>
+            </li>
+            <li>
+                <a href="/code-studio/languages/common-debugging-steps">Common Debugging Setups</a>
+            </li>
+        </ul>
+    </li>
     <li>
         <a href="/code-studio/reference/configure-the-code-studio">Configure the Syncfusion Code Studio</a>
         <ul>
diff --git a/code-studio/languages/common-debugging-steps.md b/code-studio/languages/common-debugging-steps.md
new file mode 100644
index 0000000..6683aab
--- /dev/null
+++ b/code-studio/languages/common-debugging-steps.md
@@ -0,0 +1,91 @@
+---
+title: Common Debugging Steps in Syncfusion Code Studio
+description: Universal debugging steps applicable to all programming languages in Syncfusion Code Studio.
+platform: syncfusion-code-studio
+control: IDE
+documentation: Troubleshoot
+keywords: debug, debugging, breakpoints, common-steps, universal
+---
+
+# Common Debugging Steps in Syncfusion Code Studio
+
+This guide covers the fundamental debugging steps that apply across all programming languages supported in Syncfusion Code Studio.
+
+## Step 1: Set Breakpoints
+
+**Line Breakpoints**
+- Click in the gutter next to the line number
+- Red dot appears indicating breakpoint is set
+- Or press `F9` while cursor is on the line
+
+**Conditional Breakpoints**
+- Right-click on breakpoint
+- Select **Edit Breakpoint**
+- Enter condition for when breakpoint should trigger
+
+**Logpoints**
+- Right-click in gutter
+- Select **Add Logpoint**
+- Enter message to log without stopping execution
+- Useful for tracing execution flow
+
+**Exception Breakpoints**
+- Open **Run and Debug** view (`Ctrl+Shift+D`)
+- Expand **Breakpoints** section
+- Check boxes for exception types to pause on
+
+## Step 2: Start Debugging
+
+**Method 1: Using Run and Debug View**
+- Open **Run and Debug** view (`Ctrl+Shift+D`)
+- Select your configuration from dropdown
+- Click **Start Debugging** (`F5`)
+
+**Method 2: Using Command Palette**
+- Open **Command Palette** (`Ctrl+Shift+P`)
+- Type appropriate debug command for your language
+- Select from available options
+
+**Method 3: Quick Debug**
+- Press `F5` to debug current file
+- IDE will automatically build and start debugging
+
+## Step 3: Debug Navigation Controls
+
+Once debugging starts, use these keyboard shortcuts:
+
+- **Continue** (`F5`): Resume execution
+- **Step Over** (`F10`): Execute next line, skip function calls
+- **Step Into** (`F11`): Enter function calls
+- **Step Out** (`Shift+F11`): Exit current function
+- **Restart** (`Ctrl+Shift+F5`): Restart debugging session
+- **Stop** (`Shift+F5`): Stop debugging
+
+## Step 4: Inspect Variables and Data
+
+**Variables Panel**
+- View local variables, parameters, and properties
+- Expand objects to see properties and nested values
+- Modify variable values during debugging to test scenarios
+
+**Watch Expressions**
+- Add expressions to monitor their values
+- Right-click variable → **Add to Watch**
+- Or manually add in Watch panel
+
+**Debug Console**
+- Evaluate expressions during debugging
+- Access via **Debug Console** tab at the bottom
+- Type expressions and press Enter to evaluate
+
+**Hover Inspection**
+- Hover mouse over variables in the code
+- View variable values in a tooltip
+- Quick way to inspect values without using panels
+
+## Step 5: Navigate Call Stack
+
+- **Call Stack Panel** shows the execution path
+- Click on stack frames to navigate between function calls
+- See function/method names and line numbers
+- Understand program flow and call hierarchy
diff --git a/code-studio/languages/csharp-debugging-guide.md b/code-studio/languages/csharp-debugging-guide.md
new file mode 100644
index 0000000..d284e48
--- /dev/null
+++ b/code-studio/languages/csharp-debugging-guide.md
@@ -0,0 +1,220 @@
+---
+title: Setup and Debug C# Applications in Syncfusion Code Studio
+description: Step-by-step guide to setup and debug C# applications using Syncfusion Code Studio's debugging features and tools.
+platform: syncfusion-code-studio
+control: IDE
+documentation: Troubleshoot
+keywords: csharp, dotnet, .net, aspnetcore, debug, debugging, breakpoints, dotrush
+---
+
+# This Guide provides Step-By-Step Instructions for Setting-Up and Debugging C# Applications using Code Studio
+
+## Language Setup
+
+### Prerequisites
+
+- Install the **.NET SDK** 6.0 or later from [.NET Downloads](https://dotnet.microsoft.com/download)
+- Install **Syncfusion Code Studio**
+- Install the **.NET CLI** (comes with .NET SDK)
+
+### Verify .NET Installation
+
+Open a terminal and run:
+```
+dotnet --version
+```
+
+Verify that your .NET SDK is detected and properly configured
+
+## Required Extensions
+
+To enable comprehensive C# debugging support, install the following extension:
+
+### Essential Extension
+
+**Dotrush**
+- **Publisher**: tintoy/Tintoy Enterprises
+- **Description**: Enhanced C# debugging experience with additional visualization and debugging utilities for .NET applications
+
+## Configuration Steps
+
+### Step 1: Install Extension
+
+Open **Syncfusion Code Studio IDE**
+
+Navigate to the **Extensions** view (`Ctrl+Shift+X`)
+
+Search for "Dotrush"
+
+Click **Install** on the Dotrush extension
+
+Restart the IDE when prompted
+
+### Step 2: Configure .NET Environment
+
+**Method 1: Create a New .NET Project**
+- Open **Command Palette** (`Ctrl+Shift+P`)
+- Type `.NET: New Project`
+- Select project type (Console, Web, Class Library, etc.)
+- Enter project name and location
+
+**Method 2: Open Existing .NET Project**
+- Open the folder containing your .csproj file
+- The IDE will automatically load the project
+- Dotrush will automatically detect and configure the project
+
+### Step 3: Create Launch Configuration
+
+Open your C# project in Syncfusion Code Studio IDE
+
+Go to **Run and Debug** view (`Ctrl+Shift+D`)
+
+Click **create a launch.json file**
+
+Select **.NET 5+ and .NET Core** environment
+
+The IDE will create launch.json with basic configuration for debugging
+
+## How to Run and Debug
+
+Refer to [Common Debugging Steps](common-debugging-steps.md) for fundamental debugging procedures applicable to all languages.
+
+### Language-Specific Debug Commands and Features
+
+**C# and .NET-Specific Breakpoint Methods**
+- **Exception Breakpoints**: Open **Run and Debug** view and expand **Breakpoints** section to configure exception types
+- **DataTips**: Hover over variables in the code editor, pin DataTips to keep them visible
+
+**C# and .NET-Specific Debug Methods**
+
+**Method 1: Using Run and Debug View**
+- Open **Run and Debug** view (`Ctrl+Shift+D`)
+- Select your configuration from dropdown
+- Click **Start Debugging** (`F5`)
+
+**Method 2: Using Command Palette**
+- Open **Command Palette** (`Ctrl+Shift+P`)
+- Type `.NET: Debug`
+- Select appropriate option
+
+**Method 3: Quick Debug**
+- Open C# file with Main method
+- Press `F5` to debug current file
+- IDE will build and start debugging automatically
+
+**DataTips Enhancement**
+- Hover over variables in the code editor
+- Pin DataTips to keep them visible
+- Click pin icon to lock DataTip position
+
+## Debugging Different Project Types
+
+### Console Applications
+
+Use standard launch configuration
+
+No special setup required beyond creating launch.json
+
+### ASP.NET Core Applications
+
+Add web browser debugging support
+
+Set breakpoints in controller actions and middleware
+
+Use web-specific configurations for launch.json
+
+### Class Libraries
+
+Debug using Unit Tests
+
+Or create a console application that references the library
+
+### Unit Tests
+
+Install appropriate testing framework (xUnit, NUnit, MSTest)
+
+Use the Testing view to run and debug tests
+
+Click **Debug** above test method
+
+Or use command palette: `.NET: Debug Test`
+
+## Advanced Debugging Features
+
+### Hot Reload
+
+Enable automatic code reloading during debugging
+
+Make code changes and see them apply without restarting
+
+Supported in .NET 6+ with compatible project types
+
+### Remote Debugging
+
+Configure remote debugging for applications running on different machines
+
+Use network-based debugging protocols
+
+Set up secure connections for production debugging
+
+### Just My Code
+
+By default, the debugger steps through your code
+
+Enable "Just My Code" to skip framework and library code
+
+Disable to debug .NET framework and external libraries
+
+## Troubleshooting Common Issues
+
+### Issue 1: Debugger Not Starting
+
+**Solutions:**
+- Verify .NET SDK installation using `dotnet --version`
+- Check omnisharp.dotnetPath setting in IDE preferences
+- Restart IDE and clean workspace
+- Delete bin and obj folders and rebuild project
+- Ensure launch.json has correct configuration
+
+### Issue 2: Breakpoints Not Hit
+
+**Solutions:**
+- Ensure code is compiled with debug information
+- Verify breakpoint is in executable code path
+- Check if code path actually reaches the breakpoint
+- Clear workspace cache and rebuild solution
+- Verify correct startup project is selected
+
+### Issue 3: Source Not Found
+
+**Solutions:**
+- Verify source files are correctly located
+- Check project paths in launch.json
+- Ensure PDB debug files are generated
+- Rebuild project with Debug configuration (not Release)
+
+### Issue 4: Dotrush Not Detecting Project
+
+**Solutions:**
+- Ensure .csproj file is in the workspace root
+- Restart the IDE
+- Reload the current folder
+- Check Dotrush output panel for specific errors
+
+### Issue 5: Performance Issues
+
+**Solutions:**
+- Enable "Just My Code" to reduce debugging overhead
+- Disable unnecessary breakpoints
+- Increase IDE memory allocation
+- Close unused debug sessions
+- Avoid evaluating large objects in watch expressions
+
+### Issue 6: Solution/Project Not Loading
+
+**Solutions:**
+- Ensure .sln or .csproj file exists in workspace root
+- Check that all project references are valid
+- Verify NuGet packages are restored (`dotnet restore`)
+- Run `dotnet build` to check for compilation errors
+- Verify Dotrush extension is properly installed and enabled
diff --git a/code-studio/languages/java-debugging-guide.md b/code-studio/languages/java-debugging-guide.md
new file mode 100644
index 0000000..a617008
--- /dev/null
+++ b/code-studio/languages/java-debugging-guide.md
@@ -0,0 +1,173 @@
+---
+title: Setup and Debug Java Applications in Syncfusion Code Studio
+description: Step-by-step guide to setup and debug Java applications using Syncfusion Code Studio's debugging features and tools.
+platform: syncfusion-code-studio
+control: IDE
+documentation: Troubleshoot
+keywords: java, jdk, maven, gradle, spring-boot, debug, debugging, breakpoints
+---
+
+# This Guide provides Step-By-Step Instructions for Setting-Up and Debugging Java Applications using Code Studio
+
+## Language Setup
+
+### Prerequisites
+
+- Install the **Java Development Kit (JDK)** 8 or later from [Oracle JDK](https://www.oracle.com/java/technologies/downloads/) or [OpenJDK](https://openjdk.org/)
+- Install **Maven** or **Gradle** build tools (optional, but recommended for project management)
+
+### Verify Java Installation
+
+Open the **Command Palette** (`Ctrl+Shift+P`)
+
+Type `Java: Check Java Runtime` and select it
+
+Verify that your JDK is detected and properly configured
+
+## Required Extensions
+
+To enable comprehensive Java debugging support, install the following extensions:
+
+### Essential Extensions
+
+**Extension Pack for Java**
+- **Publisher**: Microsoft
+- **Description**: Collection of extensions for Java development including Language Support for Java, Debugger for Java, Test Runner for Java, Maven for Java, and Visual Studio IntelliCode
+
+The Extension Pack includes:
+
+**Language Support for Java™** (by Red Hat)
+- Java Linting, IntelliSense, formatting, refactoring, Maven/Gradle support
+
+**Debugger for Java** (by Microsoft)
+- Lightweight Java debugger with breakpoints, variable inspection, and call stack navigation
+
+## Configuration Steps
+
+### Step 1: Install Extensions
+
+Open **Syncfusion Code Studio IDE**
+
+Navigate to the **Extensions** view (`Ctrl+Shift+X`)
+
+Search for "Extension Pack for Java"
+
+Click **Install** on the Extension Pack for Java by Microsoft
+
+Restart the IDE when prompted
+
+### Step 2: Configure Java Environment
+
+**Method 1: Using Settings**
+- Open **Settings** (`Ctrl+,`)
+- Search for "java.home"
+- Set the path to your JDK installation
+
+**Method 2: Using Environment Variable**
+- Set `JAVA_HOME` environment variable to your JDK path
+- Add `%JAVA_HOME%\bin` to your system PATH
+
+### Step 3: Create Launch Configuration
+
+Open your Java project in Syncfusion Code Studio IDE
+
+Go to **Run and Debug** view (`Ctrl+Shift+D`)
+
+Click **create a launch.json file**
+
+Select **Java** environment
+
+The IDE will create launch.json with basic configuration for debugging
+
+## How to Run and Debug
+
+Refer to [Common Debugging Steps](common-debugging-steps.md) for fundamental debugging procedures applicable to all languages.
+
+### Language-Specific Debug Commands
+
+**Java-Specific Methods**
+
+**Using Command Palette**
+- Open **Command Palette** (`Ctrl+Shift+P`)
+- Type `Java: Debug`
+- Select appropriate option
+
+**Quick Debug**
+- Open Java file with main method
+- Press `F5` to debug current file
+
+## Debugging Different Project Types
+
+### Maven Projects
+
+Ensure Maven extension is installed
+
+Use Maven-specific launch configuration for proper classpath resolution
+
+### Gradle Projects
+
+Install Gradle for Java extension
+
+Configure Gradle-specific settings for debugging
+
+## Advanced Debugging Features
+
+### Hot Code Replace
+
+Enable automatic code replacement during debugging without restarting the session
+
+### Exception Breakpoints
+
+Set breakpoints that trigger when specific exceptions occur
+
+Configure to break on caught or uncaught exceptions
+
+## Unit Test Debugging
+
+### Debug Single Test
+
+Open test file
+
+Click **Debug** above test method
+
+Or use `Ctrl+F5` for quick test debugging
+
+### Debug Test Suite
+
+Right-click test class
+
+Select **Debug Java** to run all tests in debug mode
+
+## Troubleshooting Common Issues
+
+### Issue 1: Debugger Not Starting
+
+**Solutions:**
+- Verify Java installation using `java -version`
+- Check `java.home` setting in IDE preferences
+- Restart IDE and clean workspace
+- Rebuild project to ensure proper compilation
+
+### Issue 2: Breakpoints Not Hit
+
+**Solutions:**
+- Ensure code is compiled with debug information
+- Check if breakpoint is in executable code path
+- Verify classpath configuration
+- Clear workspace cache and rebuild
+
+### Issue 3: Source Not Found
+
+**Solutions:**
+- Verify source paths are correctly configured
+- Check Maven/Gradle source directory settings
+- Ensure debug symbols are included in compilation
+
+### Issue 4: Performance Issues
+
+**Solutions:**
+- Increase memory allocation for Java processes
+- Disable unnecessary debugging features
+- Use step filters to skip framework code
+- Close unused debug sessions
+
diff --git a/code-studio/languages/php-debugging-guide.md b/code-studio/languages/php-debugging-guide.md
new file mode 100644
index 0000000..0a448ce
--- /dev/null
+++ b/code-studio/languages/php-debugging-guide.md
@@ -0,0 +1,476 @@
+---
+title: Setup and Debug PHP Applications in Syncfusion Code Studio
+description: Step-by-step guide to setup and debug PHP applications using Syncfusion Code Studio's debugging features and tools.
+platform: syncfusion-code-studio
+control: IDE
+documentation: Troubleshoot
+keywords: php, xdebug, debug, debugging, breakpoints
+---
+
+# This Guide provides Step-By-Step Instructions for Setting-Up and Debugging PHP Applications using Code Studio
+
+## Language Setup
+
+### Prerequisites
+
+- Install **PHP** 8.3 or 8.4 from [windows.php.net](https://windows.php.net/download/) (Thread Safe version recommended)
+- Install **Xdebug** extension for debugging support
+- Configure system **PATH** environment variable
+
+### Step-by-Step PHP Installation
+
+#### 1. Download and Extract PHP
+
+Download the **Thread Safe (TS)** ZIP package for Windows from [windows.php.net/download](https://windows.php.net/download/)
+
+Extract the contents to a simple path like `C:\php`
+
+**Note**: PHP 8.5 is not yet supported by Xdebug. Use PHP 8.3 or 8.4 for debugging support.
+
+#### 2. Add PHP to System PATH
+
+Press `Win + X` and select **System**
+
+Click **Advanced system settings**
+
+Click **Environment Variables**
+
+Under **System variables**, find and select **Path**, then click **Edit**
+
+Click **New** and add `C:\php`
+
+Click **OK** on all dialogs to save changes
+
+#### 3. Configure php.ini
+
+Navigate to `C:\php` folder
+
+Copy `php.ini-development` and rename the copy to `php.ini`
+
+Open `php.ini` in a text editor
+
+Enable essential extensions by removing the semicolon (;) at the beginning of these lines:
+```ini
+extension=curl
+extension=mbstring
+extension=openssl
+extension=mysqli
+extension=pdo_mysql
+```
+
+Save and close the file
+
+#### 4. Verify PHP Installation
+
+Open a **new** Command Prompt or PowerShell window
+
+Run the following command:
+```bash
+php -v
+```
+
+You should see output showing the PHP version (e.g., PHP 8.3.x or 8.4.x)
+
+### Step-by-Step Xdebug Installation
+
+#### 1. Generate Xdebug Configuration
+
+Open Command Prompt or PowerShell
+
+Run the following command and save the output to a file:
+```bash
+php -i > phpinfo.txt
+```
+
+Open your web browser and navigate to [xdebug.org/wizard](https://xdebug.org/wizard)
+
+Open `phpinfo.txt`, copy all contents, and paste into the Xdebug Wizard text box
+
+Click **Analyse my phpinfo() output**
+
+#### 2. Download Xdebug DLL
+
+The wizard will show you specific instructions for your PHP version
+
+Download the recommended Xdebug DLL file from the provided link
+
+The file will be named something like `php_xdebug-3.x.x-8.3-ts-vs16-x86_64.dll`
+
+#### 3. Install Xdebug Extension
+
+Move the downloaded DLL file to `C:\php\ext\` directory
+
+Rename the file to `php_xdebug.dll` for simplicity (optional but recommended)
+
+Open `C:\php\php.ini` in a text editor
+
+Scroll to the very end of the file and add the following configuration:
+```ini
+[xdebug]
+zend_extension=xdebug
+xdebug.mode=debug
+xdebug.start_with_request=yes
+xdebug.client_port=9003
+xdebug.client_host=127.0.0.1
+xdebug.log_level=0
+```
+
+Save the file
+
+#### 4. Verify Xdebug Installation
+
+Open a **new** Command Prompt or PowerShell window
+
+Run the following command:
+```bash
+php -v
+```
+
+You should see output that includes:
+```
+PHP 8.x.x (cli) (built: ...)
+...
+with Xdebug v3.x.x, Copyright (c) 2002-2024, by Derick Rethans
+```
+
+Alternatively, run:
+```bash
+php -m
+```
+
+Look for `xdebug` in the list of loaded modules
+
+If Xdebug is not showing, double-check your php.ini configuration and ensure the path to the DLL is correct
+
+## Required Extensions
+
+To enable comprehensive PHP debugging support, install the following extensions:
+
+### Essential Extensions
+
+**PHP Intelephense**
+- **Publisher**: Ben Mewburn
+- **Description**: High-performance PHP language support with IntelliSense, code navigation, formatting, and refactoring
+
+**PHP Debug**
+- **Publisher**: Xdebug
+- **Description**: Debug support for PHP with Xdebug, providing breakpoints, step debugging, variable inspection, and call stack navigation
+## Configuration Steps
+
+### Step 1: Install Extensions
+
+Open **Syncfusion Code Studio IDE**
+
+Navigate to the **Extensions** view (`Ctrl+Shift+X`)
+
+Search for "PHP Intelephense"
+
+Click **Install** on the PHP Intelephense extension by Ben Mewburn
+
+Search for "PHP Debug"
+
+Click **Install** on the PHP Debug extension by Xdebug
+
+Restart the IDE when prompted
+
+### Step 2: Configure PHP Environment
+
+**Method 1: Using Built-in PHP Server**
+- Create or open a PHP project folder
+- Open terminal in the IDE (`Ctrl+``)
+- Navigate to your project root
+- Start the built-in PHP server:
+```bash
+php -S localhost:8000
+```
+- Access your application at `http://localhost:8000`
+
+**Method 2: Using External Web Server (Apache/Nginx)**
+- Configure your web server to use the PHP installation
+- Set document root to your project folder
+- Ensure Xdebug is configured in `php.ini` as described in prerequisites
+- Restart the web server after PHP configuration changes
+
+**Method 3: Verify PHP Path in IDE**
+- Open **Command Palette** (`Ctrl+Shift+P`)
+- Type `Preferences: Open Settings (UI)`
+- Search for `php.validate.executablePath`
+- Set the path to your PHP executable (e.g., `C:\php\php.exe`)
+
+### Step 3: Create Launch Configuration
+
+Open your PHP project in Syncfusion Code Studio IDE
+
+Go to **Run and Debug** view (`Ctrl+Shift+D`)
+
+Click **create a launch.json file**
+
+Select **PHP** environment
+
+The IDE will create `.vscode/launch.json` with basic configuration for debugging
+
+## How to Run and Debug
+
+Refer to [Common Debugging Steps](common-debugging-steps.md) for fundamental debugging procedures applicable to all languages.
+
+### Language-Specific Debug Commands and Features
+
+**PHP-Specific Breakpoint Methods**
+- **Function Breakpoints**: Set breakpoints on specific PHP function calls
+
+**PHP-Specific Debug Methods**
+
+**Method 1: Debug Current Script**
+- Open a PHP file in the editor
+- Set breakpoints by clicking in the gutter (left of line numbers)
+- Open **Run and Debug** view (`Ctrl+Shift+D`)
+- Select **Launch currently open script** from dropdown
+- Click **Start Debugging** (`F5`) or press `F5`
+- Script executes with debugger attached
+
+**Method 2: Debug Web Application (Listen Mode)**
+- Open **Run and Debug** view (`Ctrl+Shift+D`)
+- Select **Listen for Xdebug** from dropdown
+- Click **Start Debugging** (`F5`)
+- The debugger will wait for incoming connections
+- Open your web browser and navigate to your application (e.g., `http://localhost:8000`)
+- Xdebug will connect automatically when PHP script executes
+- Execution will pause at breakpoints
+
+**Method 3: Debug with Built-in Server**
+- Open **Run and Debug** view (`Ctrl+Shift+D`)
+- Select **Launch Built-in web server** from dropdown
+- Click **Start Debugging** (`F5`)
+- The PHP built-in server starts automatically
+- Browser opens automatically to your application
+- Set breakpoints and interact with your application
+
+**Method 4: Using Command Palette**
+- Open **Command Palette** (`Ctrl+Shift+P`)
+- Type `Debug: Start Debugging`
+- Select appropriate PHP debug configuration
+
+## Debugging Different Project Types
+
+### Standard PHP Scripts
+
+Use **Launch currently open script** configuration
+
+Ideal for CLI scripts, cron jobs, and standalone PHP files
+
+### Web Applications (Plain PHP)
+
+Use **Listen for Xdebug** or **Launch Built-in web server** configuration
+
+Set breakpoints in PHP files that handle web requests
+
+Test application through browser while debugger is listening
+
+Use **Launch Built-in web server** with appropriate document root
+
+Set `cwd` in launch.json to project root directory
+
+### Laravel Applications
+
+Use **Listen for Xdebug** configuration
+
+Start Laravel development server: `php artisan serve`
+
+Set breakpoints in controllers, models, or middleware
+
+Access application through browser at `http://localhost:8000`
+
+### WordPress Development
+
+Configure web server (Apache/Nginx) to serve WordPress
+
+Use **Listen for Xdebug** configuration
+
+Start debugging session before accessing WordPress admin or frontend
+
+Set breakpoints in themes, plugins, or core files
+
+### API Development
+
+Use **Listen for Xdebug** configuration
+
+Test API endpoints using tools like Postman or cURL
+
+Debugger catches requests and pauses at breakpoints
+
+Inspect request data, headers, and response generation
+
+## Advanced Debugging Features
+
+### Path Mapping (Remote Debugging)
+
+Configure path mappings for debugging applications on remote servers
+
+Map remote file paths to local workspace paths
+
+Useful for Docker containers, virtual machines, or remote servers
+
+### Multi-session Debugging
+
+Enable debugging of multiple PHP processes simultaneously
+
+Each session appears separately in **Call Stack** panel
+
+Useful for debugging AJAX requests or background processes
+
+### Xdebug Profiling
+
+Enable profiling mode to analyze performance
+
+Add to php.ini:
+```ini
+xdebug.mode=debug,profile
+xdebug.output_dir="/tmp/xdebug"
+```
+
+Analyze generated cachegrind files with tools like KCachegrind or Webgrind
+
+### Step Filtering
+
+Configure step filters to skip debugging vendor code or specific files
+
+Improves debugging performance for large projects
+
+## Unit Test Debugging
+
+### Debugging Specific Test
+
+Open the test file in editor
+
+Set breakpoints in test methods
+
+Press `F5` to debug current test file
+
+Inspect variables, assertions, and test data during execution
+
+## Troubleshooting Common Issues
+
+### Issue 1: Debugger Not Starting
+
+**Solutions:**
+- Verify PHP installation: run `php -v` in terminal
+- Verify Xdebug installation: run `php -m` and look for `xdebug`
+- Check `php.ini` has correct Xdebug configuration
+- Ensure `xdebug.mode=debug` is set in php.ini
+- Restart IDE after changing php.ini
+- Check PHP Debug extension is installed and enabled
+- Verify port 9003 is not blocked by firewall
+
+### Issue 2: Breakpoints Not Hit
+
+**Solutions:**
+- Ensure Xdebug is properly installed (check `php -v` output)
+- Verify `xdebug.start_with_request=yes` is set in php.ini
+- Check that breakpoints are set on executable PHP code (not comments or blank lines)
+- Ensure the correct PHP file is being executed
+- Verify path mappings if using remote debugging
+- Check Xdebug log for connection issues (set `xdebug.log` in php.ini)
+- Try restarting the debug session
+
+### Issue 3: "Connection Timeout" Error
+
+**Solutions:**
+- Verify Xdebug is configured to connect to correct host and port
+- Check firewall settings allow connections on port 9003
+- Ensure IDE is listening for Xdebug connections before running script
+- Verify `xdebug.client_host=127.0.0.1` in php.ini
+- Check if another debugger is using port 9003
+- Try changing Xdebug port in both php.ini and launch.json
+
+### Issue 4: "Source Not Found" Error
+
+**Solutions:**
+- Verify PHP source files are in the workspace folder
+- Check path mappings configuration for remote/Docker debugging
+- Ensure file paths in launch.json are correct
+- Verify workspace folder is correctly opened in IDE
+- Check that symlinks are properly resolved
+
+### Issue 5: Xdebug Not Loading
+
+**Solutions:**
+- Verify Xdebug DLL file exists in `C:\php\ext\` directory
+- Check that `zend_extension=xdebug` line in php.ini has correct path
+- Ensure you're using Thread Safe (TS) PHP with matching Xdebug version
+- Verify PHP version matches Xdebug version (use Xdebug wizard)
+- Check php.ini file is in correct location (run `php --ini`)
+- Look for PHP errors when running `php -v`
+
+### Issue 6: Performance Issues During Debugging
+
+**Solutions:**
+- Disable Xdebug when not debugging (comment out zend_extension line)
+- Use conditional breakpoints instead of many regular breakpoints
+- Reduce the number of watch expressions
+- Avoid hovering over large arrays or objects
+- Increase PHP memory limit if needed (`memory_limit` in php.ini)
+- Close unused debug sessions
+- Use step filters to skip vendor code
+
+### Issue 7: PHP Built-in Server Not Starting
+
+**Solutions:**
+- Verify port 8000 (or configured port) is not already in use
+- Check that PHP CLI is working: `php -v`
+- Ensure current working directory (`cwd`) in launch.json is correct
+- Verify no other web server is running on the same port
+- Check terminal output for PHP errors
+- Try different port number in launch configuration
+
+### Issue 8: Variables Not Showing in Debug Panel
+
+**Solutions:**
+- Ensure execution has hit a breakpoint
+- Check that Xdebug is properly connected (look for "Listening..." in status bar)
+- Verify variables are in current scope
+- Try expanding variable sections (VARIABLES, WATCH, CALL STACK)
+- Check Xdebug configuration has `xdebug.mode=debug`
+- Restart debugging session
+- Check for Xdebug version compatibility issues
+
+## Best Practices
+
+### Development Workflow
+
+Always use virtual hosts or the built-in PHP server for local development
+
+Keep Xdebug disabled in production environments (performance impact)
+
+Use version control (Git) to track launch.json configurations
+
+Organize projects with clear folder structure
+
+### Security Considerations
+
+Never commit php.ini with sensitive information to version control
+
+Restrict Xdebug to local connections only (`xdebug.client_host=127.0.0.1`)
+
+Disable Xdebug on production servers
+
+Use strong passwords for any remote debugging scenarios
+
+### Performance Tips
+
+Only enable Xdebug when actively debugging
+
+Use conditional breakpoints to reduce debugging overhead
+
+Profile specific code sections rather than entire application
+
+Implement proper caching strategies in development
+
+### Code Quality
+
+Use PHP CodeSniffer for code style enforcement
+
+Integrate PHPStan or Psalm for static analysis
+
+Write unit tests alongside debugging sessions
+
+Document complex debugging scenarios in code comments
\ No newline at end of file
diff --git a/code-studio/languages/powershell-debugging-guide.md b/code-studio/languages/powershell-debugging-guide.md
new file mode 100644
index 0000000..e6b1ec3
--- /dev/null
+++ b/code-studio/languages/powershell-debugging-guide.md
@@ -0,0 +1,206 @@
+---
+title: Setup and Debug PowerShell Applications in Syncfusion Code Studio
+description: Step-by-step guide to setup and debug PowerShell applications using Syncfusion Code Studio's debugging features and tools.
+platform: syncfusion-code-studio
+control: IDE
+documentation: Troubleshoot
+keywords: powershell, script analyzer, debugger, breakpoints, debug
+---
+
+# This Guide provides Step-By-Step Instructions for Setting-Up and Debugging PowerShell Applications using Code Studio
+
+## Language Setup
+
+### Prerequisites
+
+- Install **PowerShell 7.2** or later from [PowerShell GitHub](https://github.com/PowerShell/PowerShell/releases)
+- Or use **Windows PowerShell 5.1** (Windows-only) with .NET Framework 4.8
+
+### Verify PowerShell Installation
+
+Open the **Command Palette** (`Ctrl+Shift+P`)
+
+Type `PowerShell: Show Session Menu` and select it
+
+Verify that your PowerShell version is displayed and properly configured
+
+## Required Extensions
+
+To enable comprehensive PowerShell debugging support, install the following extensions:
+
+### Essential Extensions
+
+**PowerShell**
+- **Publisher**: Microsoft
+- **Description**: Language support for PowerShell, debugging capabilities, script analysis, IntelliSense, and code snippets
+
+The PowerShell extension includes:
+
+**PowerShell Debugger**
+- Built-in support for local and remote debugging
+- Breakpoints, step through code, variable inspection
+
+**PSScriptAnalyzer**
+- Static code analysis for PowerShell scripts
+- Best practices recommendations and code quality checks
+
+## Configuration Steps
+
+### Step 1: Install Extensions
+
+Open **Syncfusion Code Studio IDE**
+
+Navigate to the **Extensions** view (`Ctrl+Shift+X`)
+
+Search for "PowerShell"
+
+Click **Install** on the PowerShell extension by Microsoft
+
+Restart the IDE when prompted
+
+### Step 2: Choose PowerShell Version
+
+Open **Command Palette** (`Ctrl+Shift+P`)
+
+Type `PowerShell: Show Session Menu` and select it
+
+Choose your preferred PowerShell version from the list
+
+The selected version appears in the Status Bar at the bottom right
+
+### Step 3: Create Launch Configuration
+
+**For No-Workspace Debugging:**
+- Open a PowerShell script file using File > Open File
+- Set a breakpoint and press F5 to start debugging immediately
+
+**For Workspace Debugging:**
+- Open a folder containing your PowerShell project
+- Go to **Run and Debug** view (`Ctrl+Shift+D`)
+- Click **create a launch.json file**
+- Select **PowerShell** environment
+- The IDE will create launch.json with debug configurations
+
+## How to Run and Debug
+
+Refer to [Common Debugging Steps](common-debugging-steps.md) for fundamental debugging procedures applicable to all languages.
+
+### Language-Specific Debug Commands and Features
+
+**PowerShell-Specific Breakpoint Methods**
+- **Programmatic Breakpoints**: Use `Set-PSBreakpoint` cmdlet in PowerShell code to set breakpoints on lines, functions, or variables
+- **Breakpoint Persistence**: Breakpoints persist in the Extension Terminal
+
+**PowerShell-Specific Debug Methods**
+
+**Method 1: Using Run and Debug View**
+- Open **Run and Debug** view (`Ctrl+Shift+D`)
+- Select your configuration from dropdown
+- Click **Start Debugging** (`F5`)
+
+**Method 2: Quick Debug (No-Workspace)**
+- Open PowerShell script file
+- Press `F5` to start debugging
+- Debugger stops at first breakpoint or runs to completion
+
+**Method 3: Using Command Palette**
+- Open **Command Palette** (`Ctrl+Shift+P`)
+- Type `Debug PowerShell Script`
+- Select appropriate option
+
+**Method 4: Run in Extension Terminal**
+- Use Extension Terminal to run commands interactively
+- Debugger attaches automatically to commands in terminal
+
+**PowerShell-Specific Debug Console**
+- Evaluate PowerShell expressions during debugging
+- Type PowerShell cmdlets and press Enter to execute
+- Useful for inspecting objects and testing code
+
+## Debugging Different Project Types
+
+### Standard PowerShell Scripts
+
+Use the default launch configuration to debug .ps1 script files
+
+### PowerShell Modules
+
+Debug module files and manifest files
+
+## Advanced Debugging Features
+
+### Interactive Session Debugging
+
+Debug commands executed from the Extension Terminal
+
+Terminal integrates with debugger automatically
+
+### Multi-version Support
+
+Switch between PowerShell versions without restarting
+
+Use PowerShell: Show Session Menu to change versions
+
+Each version has separate debugging session
+
+## Unit Test Debugging
+
+### Debug Single Test
+
+Open test file
+
+Click **Debug** above test function
+
+Test executes in debug mode with breakpoints active
+
+### Debug All Tests
+
+Right-click test file
+
+Select **Run Tests** or **Debug Tests**
+
+All tests in the file run in debug mode
+
+## Troubleshooting Common Issues
+
+### Issue 1: Debugger Not Starting
+
+**Solutions:**
+- Verify PowerShell installation and version
+- Check selected PowerShell version in Status Bar
+- Use `PowerShell: Show Session Menu` to select correct version
+- Restart IDE and check extension status
+- Verify launch.json has correct PowerShell configuration
+
+### Issue 2: Breakpoints Not Hit
+
+**Solutions:**
+- Ensure script file is saved before debugging
+- Verify breakpoint is on executable code
+- Check if code path actually reaches the breakpoint
+- Clear all breakpoints and set them again
+- Verify PowerShell version supports the breakpoint
+
+### Issue 3: Extension Terminal Not Available
+
+**Solutions:**
+- Ensure PowerShell extension is properly installed
+- Check extension status in Extensions view
+- Verify PowerShell version is compatible
+- Reinstall extension if terminal doesn't appear
+
+### Issue 4: Variables Not Visible During Debug
+
+**Solutions:**
+- Ensure variables are in scope during debugging
+- Check if variables are declared before breakpoint
+- Expand object properties in Variables panel
+- Use Watch panel to monitor specific expressions
+
+### Issue 5: Script Execution Issues
+
+**Solutions:**
+- Verify script syntax is correct
+- Check execution policy settings
+- Ensure script has proper permissions
+- Review error messages in Debug Console
diff --git a/code-studio/languages/python-debugging-guide.md b/code-studio/languages/python-debugging-guide.md
new file mode 100644
index 0000000..1c3212a
--- /dev/null
+++ b/code-studio/languages/python-debugging-guide.md
@@ -0,0 +1,210 @@
+---
+title: Setup and Debug Python Applications in Syncfusion Code Studio
+description: Step-by-step guide to setup and debug Python applications using Syncfusion Code Studio's debugging features and tools.
+platform: syncfusion-code-studio
+control: IDE
+documentation: Troubleshoot
+keywords: python, debugpy, debug, debugging, breakpoints
+---
+
+# This Guide provides Step-By-Step Instructions for Setting-Up and Debugging Python Applications using Code Studio
+
+## Language Setup
+
+### Prerequisites
+
+- Install **Python** 3.7 or later from [Python.org](https://www.python.org/downloads/)
+- Install **pip** (Python package installer, usually comes with Python)
+
+### Verify Python Installation
+
+Open the **Command Palette** (`Ctrl+Shift+P`)
+
+Type `Python: Select Interpreter` and select it
+
+Verify that your Python interpreter is detected and properly configured
+
+## Required Extensions
+
+To enable comprehensive Python debugging support, install the following extensions:
+
+### Essential Extensions
+
+**Python**
+- **Publisher**: Microsoft
+- **Description**: IntelliSense, Linting, Debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more
+
+**Python Debugger**
+- **Publisher**: Microsoft
+- **Description**: A debugger for Python with support for local and remote debugging, including debugging in Docker containers and Virtual environments
+
+## Configuration Steps
+
+### Step 1: Install Extensions
+
+Open **Syncfusion Code Studio IDE**
+
+Navigate to the **Extensions** view (`Ctrl+Shift+X`)
+
+Search for "Python"
+
+Click **Install** on the Python extension by Microsoft
+
+Install the **Python Debugger** extension as well
+
+Restart the IDE when prompted
+
+### Step 2: Configure Python Environment
+
+**Method 1: Using Python: Select Interpreter**
+- Open **Command Palette** (`Ctrl+Shift+P`)
+- Type `Python: Select Interpreter` and select it
+- Choose your preferred Python interpreter from the list
+- The selected interpreter appears in the Status Bar at the bottom right
+
+**Method 2: Using Environment Variable**
+- Set `PYTHONPATH` environment variable to your Python installation path
+- Add Python installation `\Scripts` directory to your system PATH
+
+### Step 3: Create Launch Configuration
+
+Open your Python project in Syncfusion Code Studio IDE
+
+Go to **Run and Debug** view (`Ctrl+Shift+D`)
+
+Click **create a launch.json file**
+
+Select **Python Debugger** environment
+
+The IDE will create launch.json with basic configuration for debugging
+
+## How to Run and Debug
+
+Refer to [Common Debugging Steps](common-debugging-steps.md) for fundamental debugging procedures applicable to all languages.
+
+### Language-Specific Debug Commands and Features
+
+**Python-Specific Breakpoint Methods**
+- **Inline Breakpoints**: Use `debugpy.breakpoint()` in your Python code to programmatically set a breakpoint
+- **Hit Count Operators**: Conditional breakpoints support hit count operators (>, >=, <, <=, ==, %)
+
+**Python-Specific Debug Methods**
+
+**Method 1: Using Run and Debug View**
+- Open **Run and Debug** view (`Ctrl+Shift+D`)
+- Select your configuration from dropdown
+- Click **Start Debugging** (`F5`)
+
+**Method 2: Using Command Palette**
+- Open **Command Palette** (`Ctrl+Shift+P`)
+- Type `Debug Python File` or `Python: Debug Current File`
+- Select appropriate option
+
+**Method 3: Quick Debug**
+- Click the debug button (play icon with a bug) in the top-right corner of the editor
+- Or use the down-arrow to select **Python Debugger: Debug Python File**
+
+**Method 4: Debug from Command Line**
+- Install debugpy using pip
+- Run with debugger from terminal
+- Then attach VS Code debugger using attach configuration
+
+**Hover Inspection**
+- Hover mouse over variables in the code
+- View variable values in a tooltip
+- Quick way to inspect values without using panels
+
+## Debugging Different Project Types
+
+### Standard Python Scripts
+
+Use the default configuration to debug Python files
+
+## Advanced Debugging Features
+
+### Hot Code Reload
+
+Enable automatic code reloading during debugging when changes are made to code after the debugger execution has hit a breakpoint
+
+Code changes are automatically applied without restarting the session
+
+### Multi-threaded Debugging
+
+Enable subprocess debugging for multi-threaded applications
+
+Allows the debugger to attach to subprocesses created by the main process
+
+### Environment Variables
+
+Set environment variables for debugging session using the env property
+
+Specify environment variable definitions file using envFile property
+
+Variables are passed to the Python process during debugging
+
+### Just My Code
+
+By default, the debugger only steps through user-written code
+
+Set justMyCode: false to also debug standard library functions
+
+## Unit Test Debugging
+
+### Debug Single Test
+
+Open test file (using pytest or unittest framework)
+
+Click **Debug** above test method
+
+Or use command palette: `Python: Debug Tests`
+
+### Debug All Tests
+
+Right-click test file
+
+Select **Run Tests** or **Debug Tests**
+
+All tests in the file run in debug mode with breakpoints active
+
+## Troubleshooting Common Issues
+
+### Issue 1: Debugger Not Starting
+
+**Solutions:**
+- Verify Python installation using standard terminal commands
+- Check selected interpreter in Status Bar (bottom right)
+- Use `Python: Select Interpreter` command to select correct Python
+- Restart IDE and clean workspace cache
+- Verify launch.json has correct `"type": "debugpy"` (not deprecated `"python"`)
+
+### Issue 2: Breakpoints Not Hit
+
+**Solutions:**
+- Ensure file is saved before debugging
+- Verify breakpoint is on executable code (not on blank lines or comments)
+- Check if code path actually reaches the breakpoint
+- Clear all breakpoints and set them again
+- Verify the correct Python interpreter is selected
+
+### Issue 3: "Source Not Found" Error
+
+**Solutions:**
+- Verify Python source files are in workspace
+- Check pathMappings configuration for remote debugging
+- Rebuild/reinstall packages if needed
+
+### Issue 4: Module Import Errors
+
+**Solutions:**
+- Install required packages using pip
+- Check PYTHONPATH is correctly configured
+- Ensure current working directory (cwd) in launch.json is correct
+
+### Issue 5: Performance Issues During Debugging
+
+**Solutions:**
+- Disable unnecessary breakpoints
+- Use `justMyCode: true` to skip debugging standard library
+- Increase IDE memory allocation
+- Close unused debug sessions
+- Avoid debugging very large data structures in watch expressions