Sorry the delay, I had to coerce the only 64-bit box in the house out away from my daughter to check on this one.
There may also be some problems in this code gen layer for some patterns. The LinqToSqlAttributeMapping generator also generators C# code on VS2008 (not available on VS2005). However, this should give you errors other than 'Cannot find custom tool...'
I ran this scenario successfully on that machine, however. A few questions/possibilities to try to track this:
Is there any other evidence of PLiX on the system (do you see PLiX Snippet Preview Window in the View/Other Windows submenu?)
Is a PLiX schema available (create a new XML file, type (including the space) "<plx:root "
, which should expand to "<plx:root xmlns:plx="""
with a recognized schema dropdown open. This should contain http://schemas.neumont.edu/CodeGeneration/PLiX
if PLiX is installed.
Did you possibly have a previous VS2005 installation on this machine? PLiX will install for all VS versions it can find, and a subsequent NORMA setup verification doesn't check that closely if there are registry keys for all VS versions.
So, my recommendation is to:
Uninstall PLiX, which appears as Neumont PLiX (Programming Language in XML) for Visual Studio in the Add or Remove Programs control panel applet.
Reinstall from the provided PLiX .msi file.
If you don't see the PLiX Snippet Preview Window menu item when you restart, then open a Visual Studio 2008 Command Prompt (on the Start menu with your Visual Studio 2008 install) as an administrator and run devenv /setup.
If that doesn't fix it then there is something else going on. I've had to adjust numerous batch files in the build system to accomodate 64-bit systems because the HKLM\Software\Microsoft\VisualStudio key moves to HKLM\Software\Wow6432Node\Microsoft\VisualStudio when accessed from the command line. However, I haven't seen any problems here for registry keys created by a Setup program.