Update parameter command

Author: TomProkop

src/TALXIS.CLI.MCP/CopilotInstructionsManager.cs

@@ -17,7 +17,7 @@ public class CopilotInstructionsManager
         // Hardcoded instructions to be written within the marked section
         private const string TalxisInstructions = @"
 # Instructions for performing tasks over the repository
-This monorepo contains Power Platform solutions. TALXIS CLI MCP Server (alias 'txc-mcp') provides tools for developers to perform tasks over the repository.
+You work with a monorepo that contains Power Platform solutions. You must use TALXIS CLI MCP Server (alias 'txc-mcp') which provides tools for developers to perform tasks over the repository.
 
 **MANDATORY: Use TALXIS CLI MCP Server Exclusively**
 
@@ -47,7 +47,7 @@ public class CopilotInstructionsManager
    - Avoid speculation about functionality not confirmed by txc-mcp
 
 6. **Default Values to use unless specified**
-   - Always use `SolutionRootPath=Declarations` when passing parameter values to component create tool
+   - You must always pass `SolutionRootPath=Declarations` when calling the tool for creating components
 
 ## Project Structure and Naming Conventions
 

src/TALXIS.CLI.Workspace/ComponentParameterListCliCommand.cs

@@ -1,4 +1,5 @@
 using DotMake.CommandLine;
+using Microsoft.TemplateEngine.Abstractions;
 using TALXIS.CLI.Workspace.TemplateEngine;
 
 namespace TALXIS.CLI.Workspace;
@@ -25,6 +26,13 @@ public int Run()
             return 0;
         }
         Console.WriteLine($"Parameters for template '{ShortName}':");
+        
+        // Always show the mandatory output parameter first
+        Console.WriteLine("--output (Project folder path)  (text)  <required>");
+        Console.WriteLine("    Specifies the target project folder path where the component will be created.");
+        Console.WriteLine("    Required for both creating new projects (solution, plugin, PCF, etc.) and adding components to existing projects.");
+        Console.WriteLine("    Format: \"src\\Solutions.DataModel\"");
+        
         foreach (var p in parameters)
         {
             Console.Write($"--{p.Name}");
@@ -33,7 +41,9 @@ public int Run()
             Console.Write($"  ({p.DataType})");
             if (!string.IsNullOrEmpty(p.DefaultValue?.ToString()))
                 Console.Write($"  [default: {p.DefaultValue}]");
-            if (p.Precedence != null && p.Precedence.ToString() == "Required")
+            // Check if parameter is required
+            if (p.Precedence.IsRequired || 
+                p.Precedence.PrecedenceDefinition == Microsoft.TemplateEngine.Abstractions.PrecedenceDefinition.Required)
                 Console.Write("  <required>");
             if (p.Choices != null && p.Choices.Count > 0)
             {

src/TALXIS.CLI.Workspace/ComponentTypeListCliCommand.cs

@@ -18,7 +18,6 @@ public async Task<int> RunAsync()
             Console.WriteLine("No components available.");
             return 0;
         }
-        Console.WriteLine("Available components:");
         foreach (var template in templates)
         {
             var description = string.IsNullOrWhiteSpace(template.Description) ? "" : $" - {template.Description}";

src/TALXIS.CLI.Workspace/WorkspaceCliCommand.cs

@@ -28,15 +28,15 @@ public void Run(CliContext context)
 
 This repository is organized as a monorepo based on the .NET project system. It uses a Visual Studio solution file (.sln) to track all projects, and each project is defined by its own project file (.csproj, .cdsproj, or other .(x)proj formats). All projects are built using MSBuild.
 
-  • The root contains essential files such as README.md, .gitignore, and the .sln solution file.
-  • The src/ directory holds all source code, organized into folders for different project types.
+  • The root contains essential files such as README.md, .gitignore, and the .sln solution file
+  • The src/ directory holds all source code, organized into folders for different project types
 
 Project Types Supported:
-  • Dataverse Solution (.cdsproj or .csproj): Used for defining Dataverse components and metadata.
-  • Dataverse Package (.csproj): Bundles multiple solutions and custom logic for deployment; references other projects to form a unit of deployment.
-  • Dataverse Plugin (.csproj): Contains custom business logic, event handlers, and automation for Dataverse.
-  • Power Apps Component Framework control (.csproj): Implements custom controls for Power Apps.
-  • Power Apps Script Library (.csproj): Provides reusable scripts for Power Platform solutions.
+  • Dataverse Solution (.cdsproj or .csproj): Used for defining Dataverse components and metadata. Build artifact is solution ZIP file.
+  • Dataverse Package (.csproj): Bundles multiple solutions and custom logic for deployment; references other projects to form a unit of deployment. Build artifact is package ZIP file which contains all solutions, import config, data and deployment automation/migration code.
+  • Dataverse Plugin (.csproj): Contains custom business logic, event handlers, and automation for Dataverse. Build artifact is a plugin DLL file.
+  • Power Apps Component Framework control (.csproj): Implements custom controls for Power Apps. Build artifact is a PCF control bundle JS.
+  • Power Apps Script Library (.csproj): Provides reusable scripts for Power Platform solutions. Build artifact is a script bundle JS file.
   • Power Platform Connector (.csproj): Defines custom connectors for Power Platform integrations.
   • Code App (.csproj): Builds fully custom frontend SPA hosted in Power Apps.
   • Other .NET-based projects (.csproj, .xproj): Any additional supporting libraries or tools.
@@ -51,8 +51,8 @@ The Visual Studio solution file (.sln) and src folder MUST be initialized before
   4. Create src/ directory: mkdir src
   
 Development and Build:
-  • Projects are added to the solution file (.sln) for easy management and building.
-  • MSBuild is used to build all project types, ensuring compatibility and automation.
+  • All projects are added to the single solution file (.sln) which is placed in the root directory
+  • MSBuild (dotnet build) is used to build all project types
   • Solution projects can have ProjectReferences to plugin, script, PCF, and Code App project types. When the solution is built, it pulls outputs of the referenced projects and places them into the solution artifact (the build output of the solution project).
   • Multiple solutions can be added as ProjectReferences to the package project. When the package is built, it composes ImportConfig.xml with the list of solutions and the order in which they are imported to Dataverse upon deployment.
   • Package project type can contain C# migration and deployment automation/infra code. Dataverse packages can also contain configuration and test data which needs to be deployed with the code/definitions.