I have one problem with Visual Studio 2012 which is when I run the code the command prompt window doesnt open. I think everything is ok with the code that when I debug and run it, appears a light blue bar below saying "Ready" after I debug and run the code but the command window doesnt open. What I should do for the command window to appear?
I encountered a problem where the command window stopped opening while I was debugging. (I had accidentally closed it out with the "X" previously.) Checking the MSDN help page gave me the following:
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. To display the Command window, choose Other Windows from the View menu, and select Command Window.
It sounds like your project is not a Console Application. Double check!
Related
I recently installed Android Studio 3.1.3 on my laptop in order to start learning android/mobile development (I am still new to all of this). The LogCat option seems to be missing though (refer to images below)
What I tried to do in order to fix the problem:
-uninstalling and reinstalling android studio (along with updating it...)
-researching the problem (no useful results as all the solutions were to press alt-6 or go to View->Tool Windows)
It would be a huge help/relief if someone knows how to solve this problem.
Thanks in advance.
I know it is an old question, but I encountered this problem at least twice so it might help someone.
The problem seems to be the path of the project you're looking at.
It should be pointing to the folder containing the 'app' and 'gradle' folders inside your project.
Go to File > Open
Select the folder with the 'app' folder inside your project
Press 'Open'
If you see something like this you can now probably open the Logcat window with alt-6 or View->Tool Windows.
Note that for some reason, it didn't work for me at first until I opened the app folder, run a build and then opened the folder containing the app folder.
You need to sync your project and then Logcat will show up
Just in case anyone stumbles upon this as I did: If you are developing a react-native app, be sure that you import only the android folder of the project.
If you import the whole project, then among other things, logcat is nowhere to be found!
Try pressing Alt+6 on Windows or CMD+6 on Mac.
I closed "Logcat" by accident via right click -> "Remove From Sidebar".
I was able to restore it with these steps:
Launch your current App on an emulator.
This should create a "Run" Tab on the Sidebar.
Click on the "Run" Tab and find the "Modify Run Configuration..."
(Wrench) icon and launch it.
Change the tab to "Miscellaneous".
Check the box next to "Show logcat automatically"
This is not a solution if Logcat doesn't even show up in View->Tool Windows!
But if it does: click it and it may show up at a different location than it used to be. Without recognizing I had shoved it to the top left where the project tab is shown. You can now click on the gear wheel on the tab and select move to bottom left (that is the default location).
This was the solution for my "logcat not showing".
Press Alt+6 inside Android Studio to open Logcat monitor.
Then, Do the following steps:-
Open Android Studio.
Open Android Monitor Window(at the bottom of android studio).
Here you will see the drop down in right corner.
Select Show only selected Application.
How do I get the gradle console to show when I run a gradle task in Android Stduio? When I execute the task, the run dialog pops up but the console does not. I want to be able to see the gradle console so that I can see the output, but I don't want to permantly see the gradle console (pinned mode) as 95% of the time I'd rather have the real estate for the editor.
On your run window you might see this button:
Just press it:
And there you go
From Android Studio 3.1 and above, viewing the gradle console has been as Monitoring the Build Process.
build tab
sync tab
restart
toggle view - toggles between displaying task execution as a graphical tree and displaying more detailed text output from Gradle
I've got an application I've been working on and am having an issue with android studio. When I click "build->run" and then select my device, the application never runs on my phone (and the log in android-studio that automatically comes up does not have anything, whereas in the past when I have used this feature it usually says something like, "waiting for phone..." and then the application pops up and automatically opens on the phone and you get some other pertinent information). I have the phone already in developer mode with the install from unknown sources set to on. When I manually move the application from its gradle build location to the phone and then install it manually in file explorer, all is well and the application performs as expected. As I need to debug, however, this is not a very viable solution. Anybody have any advice as to how to get it to run from the IDE? I have tried rebuilding and invalidating the cache/restarting android studio, to no avail.
When I click the run tab at the bottom I have an empty window. When I click the debug tab, I see:
Waiting for device.
Target device: samsung-samsung_sm_g920a-randomIntegerId
Uploading file
local path: /home/eric/Documents/class/OOSE/final_project/2015-group-17/project_code/android/Place2B/app/build/outputs/apk/app-debug.apk
remote path: /data/local/tmp/oose2017.myApp
Note: I am building the application on a LUbuntu 15.04 VM on a windows 8 host, and am using the latest version of android studio.
EDIT: gradle console indicates a successful build as well (obviously since moving the .apk manually to the device works properly).
Open 'Run->Edit Configurations...', and look for your app module in the column on the left-hand side.
Select it, then go to the 'General' tab.
Under the 'Activity' section, there are a couple of radio buttons. Make sure that 'Launch default activity' is selected.
I must be missing something totally obvious, but I can't find a simple way to simply stop an app from running. I'm running it on my HTC One.
I first tried toggling the green run arrow. Didn't work.
I found a "Terminate Application" circle in the lower left of the window. That doesn't seem to do anything when you click it. It seems to be grayed out, non-functional. Screen shot here
http://www.screencast.com/t/VLTOzPQ7
So, I closed the entire project. That worked, but also the entire Android Studio closed instantly. Then reopening Android Studio failed (stack dump). Then reopening again worked, but it took 30 minutes to load my project.
To stop the next time, I turned my phone off, then closed the project. That seems to have worked better, since it took me to the Welcome to Android Studio screen and invited me to open or start a project.
Maybe there's an easier way to stop an app? I see the same question on this forum but no solutions.
The Android Studio controls you are trying to use only work if you are running your app in the emulator. There are a few ways to do this when you are using an actual device or VM (e.g., Genymotion):
Use the UI of the phone to Force Stop the application. This is done in the Settings->Apps menu.
Use Android Studio's terminal window or the host's shell and issue the command:
adb shell am force-stop <package-name>
Open Android Device Monitor (green "Droid" icon), select the process under the Devices tab and click the Stop Process button (stop sign icon). This is basically the GUI way of doing #2.
You need to select the process you want to terminate (ex. com.myname.myapp) then click terminate application.
Since the application is running on your phone, you need to end the application process on the phone. When you do that the application would be shown as terminated on Android Studio.
When running and debugging server side code with Eclipse, and you activate a breakpoint being hit by visiting a url, posting data, etc. Eclipse window will automatically activate over top of your current window.
Not only that, but if your focus is in another workspace, Eclipse gets moved to that workspace as well.
Preferences
Run / Debug
Uncheck Activate workbench when a breakpoint is hit