Strange issue with start

Apr 3, 2015
4
0
#1

Charles Dye

Super Moderator
Staff member
May 20, 2008
3,586
46
Albuquerque, NM
prospero.unm.edu
#2
Here, it looks like TCC is also slapping a .COM on the end. Which suggests to my little brain -- and I could be completely wrong here -- that maybe TCC is overlooking that https:// on the front, and misidentifying the final string as an external program to search %PATH for ...?

If I add a period immediately after the "AppBuilderCLI" then TCC doesn't do that. But of course that mangles your URL; dunno whether that's an acceptable workaround for you until Rex chimes in.
 

rconn

Administrator
Staff member
May 14, 2008
10,532
94
#3
#5
Apr 3, 2015
4
0
#7
Hello again,

This command line is generated by node.js's exec API - see https://nodejs.org/api/child_process.html#child_process_child_process_exec_command_options_callback and open npm module from https://github.com/pwnall/node-open/blob/master/lib/open.js .

I potentially could change the later but I am not optimistic about upstream taking my patch.

At the end, cmd works, tcc does not. Even if this is a bug in cmd, I believe it would be better if tcc is bug-for-bug compatible with cmd (eventually hidden behind an option).
 
Apr 3, 2015
4
0
#8
Not reproducible here; it loads in the browser as expected (once I removed the superfluous " before start). (TCC does not shift case on any command arguments.)

However, your command syntax is wasteful (and slow); you can do exactly the same thing with:

"https://platform.telerik.com/appbuilder/Mist/ClientLogin?port=1636&client_name=AppBuilderCLI"

alone at the TCC prompt. (I.e., no TCC, no START.)
This is generated by node.js - I have zero ways to affect the command line. This is not something I type interactively at the prompt, this is the command line automatically generated to spawn a sub-process. I copied it from Process Explorer :)
 
#9
The command from the first post in this thread, modified only to include a path to TCC
Code:
g:\tc17\tcc /s /c "start "" "https://platform.telerik.com/appbuilder/Mist/ClientLogin?port=1636&client_name=AppBuilderCLI""
works when when entered in Win7's Start\Run dialog. It also works with CMD.
But there is a significant difference. When using TCC, it leaves a TCC running (presumably, not the one given "/c"). When using CMD, it does not leave a CMD running.
 

rconn

Administrator
Staff member
May 14, 2008
10,532
94
#10
The command from the first post in this thread, modified only to include a path to TCC
Code:
g:\tc17\tcc /s /c "start "" "https://platform.telerik.com/appbuilder/Mist/ClientLogin?port=1636&client_name=AppBuilderCLI""
works when when entered in Win7's Start\Run dialog. It also works with CMD.
But there is a significant difference. When using TCC, it leaves a TCC running (presumably, not the one given "/c"). When using CMD, it does not leave a CMD running.
Not the /C; START invokes another copy of TCC. (Which is why that syntax is so inefficient.)
 
May 29, 2008
529
3
Groton, CT
#12
This is generated by node.js - I have zero ways to affect the command line. This is not something I type interactively at the prompt, this is the command line automatically generated to spawn a sub-process. I copied it from Process Explorer :)
Do you have a way to modify the URL part of the command line? If so, perhaps you could add, after the parameters following the '?', an additional parameter, such as
Code:
"" ...?port=1636&client_name=AppBuilderCLI&dummy=""
Would that cause the extra .COM to be appended to the word DUMMY= ? The web page probably doesn't care about extra parameters.