In VisualStudio the Immediate Window is used to debug and evaluate expressions, execute statements, print variable values, and so forth. It allows you to enter expressions to be evaluated or executed by the development language during debugging. (see MSDN)
The Command Window is used to execute commands or aliases directly in the Visual Studio integrated development environment (IDE). (see MSDN too)
Knowing that we can execute the Command Window commands from the Immediate Window by preceding the command by ">"
My question is what's the difference then, why they are both their ? Are there additions in the Command Window that are not accessible or available in the Immediate Window ? Can I just keep using the Immediate Window for both purposes ? (I mean is it just sufficient and enough ?).
Related
I'm a pretty active vim user so I like to have the vi mode active on the bash line. For the most part, I don't feel the need to slip into the full visual editor for entering commands, but sometimes it can be kind of useful.
Whenever I do though, I always end up forgetting that when you quit the editor you're still in command mode, not insert mode. To me this seems totally silly since it returns you to an empty prompt, so you can expect to start typing. Half the time I go to start typing "vim" and then end up re-entering a vim editor for my command line.
Is there a way to make returning to insert mode the default for bash?
How to change current command and command line set in project properties using command line?
(with Immediate Window/ Command Window).
Best I have found out is:
Project.Properties
You couldn't change it, Immediate Window often uses to display the values of variables in your code or others. For parsing c++ command-line arguments, you need to set it under the Project property.
Vote this request if other members also meet this issue:
https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/15555378-make-changing-command-line-simple
I'm new to Xamarin on the Mac, and I'm running into some issues running my code. I don't think it should matter, but I'm using the D language plugin to develop my code.
When Terminal is set to Shells open with: Default login shell (which is zsh in my case, but bash results in the same issue), hitting the execute button causes Xamarin Studio to pop up a Terminal window which closes before it can do anything, and then Xamarin Studio reports Cannot execute "blah". ScriptError. I added an infinite loop at the beginning of my program to make sure the shell isn't exiting because the program terminated quickly, and sure enough the program seems not to be starting at all.
If I instead tell Terminal Shells open with: Command (complete path): /opt/local/bin/zsh, the terminal happily opens up and the window is named correctly as "Xamarin Studio External Console" but of course nothing is executed except for the shell itself.
Any way to debug or fix this would be greatly appreciated!
MonoDevelop/XamarinStudio uses xterm by default. Dunno if that piece of info might help.
The Command Window and the Immediate Window seem to do very similar things (for example, I can display variables in both windows by typing ? myVariable). What are the differences and why does Visual Studio include both?
They do different things.
Immediate window:
The Immediate window is used at design time to debug and evaluate expressions, execute statements, print variable values, and so forth. It allows you to enter expressions to be evaluated or executed by the development language during debugging.
Command window:
The Command window is used to execute commands or aliases directly in the Visual Studio integrated development environment (IDE). You can execute both menu commands and commands that do not appear on any menu.
The immediate window is a debugging aid.
The command window lets you execute commands (say menu items) at any time.
Though they share some functionality they each have a separate focus.
Adding to the "difference"
Immediate window: has all the functionality of the Command Window as long as it starts with ">".
Command window: does not have other functionality since it can't start with anything but ">".
P.S. Visual Studio includes both as in developing mode you can use practically only Command Window, since you need the debugging mode to be active in order to use the functionalities of the Immediate Window(which at any time can use the Command Window).
In short, have Command Window in Developing Mode and Immediate Window in Debugging Mode.
I have a VB6 console app and it uses command line parameters. For debugging, I would like to be able to start it from the IDE and ideally be able to pass it those parameters to see how it normally operates. I realize I could set a breakpoint at the appropraite place and use the Immediate window to set the values outside the command line, and I have used a couple of other workarounds in the past, but is there a way to do this as if I had actually started it as a console app?
Select Project | Properties, select the Make tab, enter the command line params in the Command Line Arguments text box. These will only apply when run in the IDE.