Resolved! Conflict between PrimalScript and PSCX

On a couple workstations we noticed a conflict between PrimalScript Enterprise and the Powershell Community Extensions (PSCX). PrimalScript would throw an error and terminate when opening a file with a .ps1 extension.

I posted a follow-up on the Codeplex discussion board. Oisin quickly responded with a fix.

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

Bingo! Now I can continue using PSCX (if you are not, you need to take a look) with PrimalScript. Thanks Oisin!

Unable to use SourceSafe LAN service, performance of SourceSafe operations will not be optimal

When trying to utilize Microsoft Visual SourceSafe 2005 (VSS) with Sapian's PrimalScript Enterprise, I was getting the following warning, "Unable to use SourceSafe LAN service, performance of SourceSafe operations will not be optimal". Well we can't have that! To remedy this, you need to enable the LAN service on the VSS server.

1. On your VSS server - Go to Microsoft Visual SourceSafe Administration
2. Click on the Server menu item
3. Click configure
4. In the Server Configuration dialog box, select LAN
5. Check the Enable LAN service for this computer.