When debugging (F4) or running (Ctrl + F4) a module project for the first time you will be asked to select a Startup Script:<\/p>\n
<\/p>\n This Startup Script will be used by PowerShell Studio as an entry point to run or debug the module project. Therefore, it\u2019s important that you explicitly import the module in the script:<\/p>\n The Startup Script will be stored by the module project so you don\u2019t have to select the script every time you wish to test the module. In addition, you have the option to change the Startup Script in the project\u2019s properties.<\/p>\n To change the Startup Script, follow these simple steps:<\/p>\n 1. Select the project node in the Project Panel:<\/p>\n 2. Go to the Property Panel and edit the Startup Script property:<\/p>\n When debugging a module project, PowerShell Studio will build and export the module then execute the Startup Script.\u00a0 Any trace points and break points contained within the project files will be triggered by the debugger and mapped to the appropriate files:<\/p>\n <\/p>\n Debugging a module without a project:<\/strong><\/p>\n If you need to debug a module that doesn\u2019t have a project, you can utilize PowerShell Studio\u2019s new \u201cDebug with Multiple Files\u201d option.<\/p>\n First open the test script and the module files using PowerShell Studio. Next, debug the test script using the \u201cDebug with Multiple Files\u201d option and select the module files that you wish to debug.<\/p>\n Now the debugger will respond to break points located in the module files:<\/p>\n![\"Select](\"http:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2012\/10\/Select-Startup-Script.png\" "\\"Select")
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p><\/blockquote>\n<\/a><\/p><\/blockquote>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n