Messages

1

LaunchBar Commander / Re: Launch Ignores Exe.Config

« on: February 06, 2012, 04:37 PM »

BAT with "%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe" Starts the prompt using the .Config's settings.  But the Apps running icon is the CMD icon.

BAT with "start %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe"  uses the .Congfig settings, applies the appropriate powerShell App Icon, but doesn't load the default color scheme.

the .lnk has the color scheme info so I changed it to:
start "" "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk"
and this works fine.

Running the link without invoking via Start does not work.

I'll try again with a direct link after the update, but this will work.

Thanks,
      Josh

2

LaunchBar Commander / Launch Ignores Exe.Config

« on: February 06, 2012, 02:17 PM »

LaunchBar Commander 1.129.01 (Win7 All latest patches)
I have created command nodes to both:
C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe
And the to the default shortcut in the start menu.

I have created a C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe.config config file to allow PowerShell to run as .Net 4.0

When I run either through LaunchBar Commander, it is ignoring this XML, giving me a black background (default is blue).

Any ideas?

When launching the EXE directly it loads the .CONFIG.

.Config matches :

<?xml version="1.0"?>
<configuration>
    <startup useLegacyV2RuntimeActivationPolicy="true">
          <supportedRuntime version="v4.0.30319" />
          <supportedRuntime version="v3.5" />
          <supportedRuntime version="v3.0" />
          <supportedRuntime version="v2.0.50727" />

    </startup>
</configuration>