Create new solution is broken for simple examples

[RobertRostohar]

Type: Bug Report

Describe the bug

• OS and Version: Windows 11
• VS Code Version: 1.94.2
• Extension Version: 1.40
• Target Device: STM32

Starting a new solution based on existing CMSIS Solution examples incorrectly copies the contents from the pack. It seems that the project directory is copied twice and not completely. Sometimes only some files are copied and sometimes some files are corrupted (have only partial contents).

Also note that the specified 'Solution Name' is only used for the directory name within the 'Solution Location'. The actual name of the solution is taken from the pack. This is misleading.

To Reproduce Steps to reproduce the behavior:

Install at least the following CMSIS packs:

• Keil::STM32H7xx_DFP@3.0.0
• Keil::STM32H743I-EVAL_BSP@1.0.0
• Keil::STM32H745I-DISCO_BSP@1.0.0

Example A: Simple example (solution and project yml files in the same directory)

1. Go to 'Create a New solution'
2. Select 'Target Board': STM32H743-EVAL
3. Select 'Template, Reference Applications, and Examples:' CMSIS SOLUTION EXAMPLE - Blinky
4. Chose 'Solution Location'
5. Disable 'Initialize Git repository'
6. Click on 'Create'
7. Go to 'Explorer' and observe the copied files to the Solution location. It will contain duplicates in the 'Blinky' sub-directory. But some files are missing (ex: 'retarget_stdio.c'), and build fails.

Example B: Simple example (solution with two projects in sub-directories)

Steps are the same as for example A, except that the 'Target Board' is STM32H745I-DISCO. Results also in duplicated files when copying the project and with missing or corrupted files.

Expected behavior The project files from the pack should be copied to the specified location as they are found in the pack (no duplication or corruption).

[ReinhardKeil]

Internal reference MCUTO-380