Pscx and PrimalScript causes primalscript to crash

Topics: Developer Forum, Project Management Forum, User Forum
Jul 16, 2007 at 8:23 PM
is anyone having a problem with Primalscript crashing when PSCX 1.1.1 profile is loaded and running any powershell script inside of Primalscript??

Install and reinstall of pscx had no effect.
Jul 23, 2007 at 12:28 AM
I have the same problem and the guys behind PrimalScript think It is something with the way PSCX wants PowerShell to load.
A longer description of my problems can be found at http://www.fredrikwall.net

I will post an Issue about this right away too.

Regards,
Fredrik Wall
Coordinator
Jul 26, 2007 at 5:36 AM
From your blog it appears that Sapien thinks they may have fixed this issue. If you find out that there something PSCX is doing that is causing problems, let us know and we'll see if we can fix it.
Jul 28, 2007 at 1:36 AM
They thought so. But I'm not really sure how much they have fixed.
It was something about a timeout when pscx was loaded or so.

I will check this when they release the next beta build.
Jul 7, 2008 at 12:39 PM
Edited Jul 7, 2008 at 12:40 PM
This is still an issue.  I have the most current version of PrimalScript 4.5.567 and the current version of PSCX. 
Looks like the only current way around this is to uninstall PSCX.

Most current dialog from Sapien. http://support.sapien.com/forum/forum_posts.asp?TID=774
Developer
Jul 11, 2008 at 5:35 PM
Hey guys,

Look for the line in your Pscx installed $profile that says:

Start-TabExpansion

and comment it out with a #. This will workaround the problem.

- Oisin
Jul 14, 2008 at 2:05 PM
Awesome!  Thanks for the response.
http://fatbeards.blogspot.com/2008/07/resolved-conflict-between-primalscript.html
Jul 19, 2008 at 12:44 PM
I seem to be having the same issue with PSCX and the new v1.1 Quest AD cmdlets. If I place the Add-Pssnapin line below Start-TabExpansion in my profile I'm fine. If I place it before it, PSCX throws an unhandled exception and powershell crashes. http://groups.google.com/group/microsoft.public.windows.powershell/browse_thread/thread/0acd2543b969051c?hl=en# I posted it here with more details as well.