JS Association. Web Developer role, Windows.

[kellygallen]

My computer is used for web development so JS files are set to open inside of an editor. When I run the complied InstantSupport file, 'unblock.js' opens in the editor vs executing. Perhaps this file is unnecessary, or there is a better way to invoke it. Otherwise great solution.

[supercoe]

Sorry about that, it's a known bug.
Here is a solution: https://forum.ultravnc.net/viewtopic.php?f=50&t=29209

[kellygallen]

Thanks to https://forum.ultravnc.net/viewtopic.php?f=50&t=29209 which had this problem before me. I solved it with two different edits that I tried on that thread.

Change Line 118 in the InstantSupport.au3
Did not work, because parameter needed to be in quotes to work with paths that have a space in them.

Code: Select all

ShellExecuteWait($WorkingPath & "\unblock.js", "", @ScriptDir, "")

Did not work because WScript didn't understand what engine to use.

Code: Select all

ShellExecuteWait("wscript.exe", $WorkingPath & "\unblock.js", @ScriptDir, "")

WScript: There is no script engine for file extension ".js"

Apparently my favorite Web Dev apps really messed up my JS file associations when I let them become associated. And there is a fix to reset the JS association.
http://www.winhelponline.com/articles/2 ... files.html
But this was not good enough.

It is simpler to edit the Line 118 in the InstantSupport.au3 to be:

Code: Select all

ShellExecuteWait("wscript.exe", '//E:jscript "' & $WorkingPath & '\unblock.js"', @ScriptDir, "")

What //E:jscript does is force it to use the js engine even if the registry pointing to that engine is messed up. It now works good.

Other Sources of information:
http://stackoverflow.com/questions/5700 ... e-argument