Fix form designer stub insertion order#173
Closed
adamdriscoll wants to merge 1 commit into
Closed
Conversation
Insert generated Windows Forms event and function stubs after script preamble statements so #requires, using, and param blocks remain first in generated scripts. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Generated Windows Forms event and function stubs were being inserted at the very top of PowerShell scripts, which could push required preamble statements like
#requires,using, and top-levelparam(...)blocks out of their valid positions.This updates the form designer CodeDOM path to calculate a script preamble insertion point and route both event variable and function stub generation through it. The VS live-document integration now inserts at that computed offset, while command-line generation uses the same shared helper.
Validation:
dotnet test .\FormDesigner.Test\FormDesigner.Test.csproj --no-restore --nologoNote: A VS project build was attempted but this environment is missing the VSSDK targets required by the project.