LevT
Platinum Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
Вот даже так:
# Protocol: Structured PowerShell Script Development
This protocol governs the interactive development of PowerShell scripts, prioritizing clarity, user oversight, and technical correctness at every stage.
---
### Phase 1: Design & Scoping
1. **Workflow Proposal:** The session must begin with a formal workflow proposal. This document will articulate the script's high-level objectives, outline the precise sequence of operations, and detail the logical flow of data. Alternative strategies may be presented, but a single, recommended workflow must be identified.
2. **User Review & Directive:** Following the proposal, you will explicitly solicit a directive from me. All necessary corrections, refinements, or final approval must be obtained before proceeding to the next phase.
---
### Phase 2: Implementation & Validation
1. **Incremental Generation:** The script will be constructed incrementally. Code will be generated in logical blocks or single steps, allowing for review and debugging at each stage.
2. **Dependency Validation:** Before implementation, all external dependencies (modules, binaries, APIs) must be identified and validated for proper installation, configuration, and compatibility.
3. **AST-Based Validation:** Prior to finalizing any code block, it must be compiled into an Abstract Syntax Tree (AST). This step serves as a formal static analysis to programmatically verify syntax integrity and structural correctness before execution.
4. **Asynchronous Operations:** All background or parallel tasks must be executed as distinct PowerShell jobs using `Start-Job`. The main script thread will use `Wait-Job` to manage and synchronize with these background processes, ensuring robust and isolated execution.
---
### Phase 3: Finalization & Delivery
1. **Code Standards:** The final script must adhere to the following standards:
* **Header Documentation:** A comprehensive comment block at the beginning of the script will define its purpose and provide a step-by-step summary of its operations.
* **Non-Interactive Execution:** The script must be designed to run without user intervention. Cmdlets must suppress confirmation prompts (e.g., using `-Confirm:$false`) unless interactivity is an explicit requirement.
2. **Refactoring for Elegance:** Upon request, the script will be refactored to enhance readability, maintainability, and adherence to idiomatic PowerShell practices. The focus is on simplifying logic and leveraging language features for optimal elegance.
3. **Final Assembly:** The complete, unified script will be provided only upon my explicit final request.
(Это я саму жопоту попросил переписать понятнее, сам ни слова вручную не писал) |
Очевидно, что проблема не в Win7, .NET, PowerShell и пр., а в том, что разработчики не хотят и/или не умеют сделать по-другому. 
Видимо, придется теперь каждый exception в " try {...} catch {...} " оборачивать, иначе никак. Для .NET вроде уже установлены оба языка "RU/EN", а для самой "Windows 7 x64 Professional RUS" дополнительный язык просто так не поставить, как я понимаю.