With this release, PowerShell Studio will relocate using statements and requires comments to ensure to that the generated GUI and project scripts do not produce errors.Ī major new feature, is the Performance Monitor, which displays the CPU and memory usage of your PowerShell scripts. PowerShell requires that using statements much be located at the beginning of a script file, otherwise it results in an error: ERROR: + using Module TestModule11 #Import classes from the moduleĮRROR: A 'using' statement must appear before any other statements in a script. Using Module TestModule11 #Import classes from the module Using statements were introduced with PowerShell V5. The name of the function that invokes the project file. If True, the ps1 file’s functions and variables are shared across the project and you will no longer be able to invoke the file. We renamed some of the project file properties: Old Name When you open your project in PowerShell Studio, it will automatically update and refactor the Call reference functions in your project. With this release, PowerShell Studio will replace the Call verb with the following verbs: File Type The Call verb was used to distinguish it from other functions, but since Call isn’t an approved verb, PSScriptAnalyzer would produce a warning. Previously, when you invoke a GUI or script file from a project, you had to use a reference function that used a Call verb. We made changed to our projects in order comply with the best practices and warning produces by PSScriptAnalyzer. The new project version is not backwards compatible with older builds of PowerShell Studio. IMPORTANT: This build will convert your projects and create a backup of the original (*.psproj.bak). Today we release a new build of PowerShell Studio 2016 and it includes some major changes and new features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |