Use this forum to ask questions after your subscription maintenance expires or before you buy. Need information on licensing or pricing? Questions about a trial version? This is the right place for you. No scripting questions, please.
Forum rules DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM. Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
This topic is 7 years and 8 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Alexander Riedel wrote:Is the path to the module a personal path? Is the module signed? blocked? What is your powershell execution policy? If it is remotesigned, then a module would work locally but not from a remote location.
Is this custom module a script module or a binary module? .NET is sensitive to security zones and will very often not load assemblies from a remote location without specifically designating that remote location 'safe'.
In general it is a best practice to deploy modules via an installer and install them on the machines needed within the designated locations for modules.
Path to the module is a UNC DFS-backed path.
Module is unsigned.
Execution policy (applied via GPO) is bypass.
Module is a script module (just a .ps1 file with custom functions).
Sorry for the delay, we still haven't been able to reproduce this issue on our end.
Can you try again and take a screenshot of the error?
I suspect that the error is occurring on the Team Foundation provider side. When you enable dot sourcing PrimalSense, it loads the file in the background and requests the source control status from the provider. I believe this is where the issue is stemming from.
What happens when you try to open the ps1 file directly in PowerShell Studio?
This topic is 7 years and 8 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
