Auto-complete fails for dot sourced variables in collection project
Posted: Wed Jul 03, 2019 1:59 pm
Product, version and build: SAPIEN Powershell Studio 2019 v5.6.162
32 or 64 bit version of product: 64-bit
Operating system: Windows 10 v1809
32 or 64 bit OS: 64-bit
I'm currently trying to organize a project that has several different forms that share variables and functions that I currently have to update in every file each time I want to change one. I'm working on placing all of these into a Global.ps1 file, but when I dot source this file I want to be able to use auto-completion (I believe it's called PrimalSense in PS Studio?) when referencing the variables and functions. A multiform project will not work for this situation, as the previous form must be closed after the next one is called. I'm currently using a collection project, and that allows the functions to show up in auto-completion when dot sourcing, but not the variables--even after setting the Shared property on Globals.ps1 to true. Is this intended behavior?
32 or 64 bit version of product: 64-bit
Operating system: Windows 10 v1809
32 or 64 bit OS: 64-bit
I'm currently trying to organize a project that has several different forms that share variables and functions that I currently have to update in every file each time I want to change one. I'm working on placing all of these into a Global.ps1 file, but when I dot source this file I want to be able to use auto-completion (I believe it's called PrimalSense in PS Studio?) when referencing the variables and functions. A multiform project will not work for this situation, as the previous form must be closed after the next one is called. I'm currently using a collection project, and that allows the functions to show up in auto-completion when dot sourcing, but not the variables--even after setting the Shared property on Globals.ps1 to true. Is this intended behavior?