On two Windows 7 and a Windows 8 computer, all up to date, when I press F12 in Internet Explorer it launches the debugger, says (Not Responding), and then leaves artifacts on the screen until I restart the computer. This has been going on for a couple months.
Here is an example:
I know several other people who are experiencing the same problem on different machines.
Apparently this is the best Microsoft can do. Is there any way to prevent F12 developer tools from instantly crashing and leaving artifacts behind on your screen?
Related
Trying to create the first template application with the sample code provided by VUZIX Blade glasses. But, unfortunately do not know how to use the template application using Android Studio.
The Blade_Template_AppV2 has been imported and I am wondering on Android Studio to see the results.
Anyone tried to run the template application and got success?
You just need to enable debugging on your Vuzix Blade as described on https://www.vuzix.com/Developer/KnowledgeBase/Detail/1077 and you can run the template app directly from Android Studio on the glasses.
In order to run the sample Vuzix Code, you'll need to activate developer mode and adb bugging.
Because https://www.vuzix.com/Developer/KnowledgeBase/Detail/1077 is down and many other vuzix manual links are down, below I have detailed the steps to activate Developer Mode and ADB bugging on the Vuzix Blade.
Navigate to your settings, then click system,
system
followed by the info tab,
info
and once you're in the info tab,
swipe left until you activate Developer mode.
swipes will display like this
To enable adb bugging,
look for adb debugging in Dev Options and enable it on.
Before we move to the next step, make sure your device is manually plugged into your system.
In order to verify that the adb debugging worked, load your app from Android Studio, open up the terminal and type ./adb devices. Your device should be displayed now.
When you run your first app, you may notice gradle builds and other things differ and pop-ups will display asking to possibly downgrade certain options so that the hardware api on the glasses matches the app. Follow these instructions accordingly.
Afterwards, you should have a fully functioning app ready to use on your glasses' home screen.
This answer was supplemented by a response at https://blog.csdn.net/sinat_28962939/article/details/103065417
I am using Visual Studio 2017 on Windows 10 with a wireless keyboard, connected to my Notebook. My keyboard lost the connection to the notebook and I could not reconnect, until a restart.
After that, Visual Studio lost my individually created keyboard shortcuts. Even after a reset of the keyboard settings and re-assigning my shortcuts, it does not work. The keyboard combination is being recognized (shift+alt+o) and is being shown in the settings after closing the configuration window with OK. It appears that even the entry in the main menu is dead.
However, the original shortcut works. Scary, isn't it?
Does anyone have a solution which is not re-installing Visual Studio?
Discovery 1
Found a solution (admin rights required). See: https://developercommunity.visualstudio.com/content/problem/3278/go-to-symbolfiletype-shortcut-dont-work.html
Helps out, sometimes. Maybe some restarts of VS 2017 required.
However, still have problems with the window grid, like others are describing here as well. Visual Studio 2017 seems to be a complete mess.
Discovery 2
Consider this article, too: https://forums.asp.net/t/1103223.aspx?Find+also+find+and+replace+not+working+in+Visual+Studio
Discovery 3
Looks like that the problem had its origin really somewhere else. Someone plugged two cables from one monitor into my docking station. I use a notebook with docking station and two external monitors. One of the external monitors has been connected via DP and the other via DVI. This caused windows to think of one additional monitor in the setup (total count was 4), but with one deactivated.
As Windows 10 still cannot deal properly with multi monitor setups (think of DPI troubles on high res screens, especially when you mix a standard DPI monitor with a notebook that has a DPI screen), I currently have the suspicion, that Visual Studio opened the lost dialog windows on the non-existent screen.
Big oops. But maybe this article helps someone...
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.
Background
I maintain several web sites that are Visual Studio "Web Site Projects".
Problem
I've found that with a couple of these projects, Visual Studio regularly freezes while I'm working on the code. This doesn't happen for some of the web site projects, and I haven't seen it happen on any Web Application projects.
Symptoms
Each time it freezes, it takes about half a minute before I can use it again.
During a freeze, Windows Task Manager reports that Microsoft.VisualStudio.Web.Host.exe is maxing out one of the CPU cores.
Steps to Reproduce
Open a .cs file under the App_Code directory.
Make a change to the file.
Save the file.
Navigate somewhere else (eg switch tab, close the file, open different program in Windows).
Navigate back to the file (eg switch tab to it, open it, or go back to Visual Studio).
Other actions that sometimes seem to trigger the problem:
"Go to definition"
Opening a file
Previewing a file
Closing a file
Using a refactoring
"Find usages"
What I've Tried
Both Visual Studio 2012 and Visual Studio 2015
Changing the website project's build action
Disabling "Build Web site as part of solution"
Deleting web references and the Bin folder seems to minimise the problem, but obviously this breaks the web site. Maybe web site projects experience this problem when they contain a lot of C# code other than code-behind files?
Similar problems
I found the following potentially-related problems using Google, but none of them seemed to contain a workaround or solution.
Microsoft.VisualStudio.Web.Host.exe Time Theft
Microsoft.VisualStudio.Web.Host.exe
Visual Studio 2012 freezes for approximately 30 seconds after every build
I noticed that the problem happened less often when I suspended ReSharper.
The problem still happened occasionally when editing classes under App_Code, but restarting Visual Studio worked around it.
I was facing a similar problem. A single Web application project with dozens of class libraries, migrated over from VS 2010 into VS 2013.
I was able to solve my problem by disabling the "Hosting Process" option:
To disable the hosting process
Open an executable project in Visual Studio. Projects that do not
produce executables (for example, class library or service projects)
do not have this option.
On the Project menu, click Properties.
Click the Debug tab.
Clear the Enable the Visual Studio hosting process check box.
Full details on MSDN: http://msdn.microsoft.com/en-us/library/ms185330.aspx
Another option for people experiencing this on old web applications that don't have the properties page in the accepted answer above.
Disable "Allow this precompiled site to be updatable".
Open Site/Solution
Right click and view Property Pages
Go to MSBuild Options
Uncheck "Allow this precompiled site to be updatable"
This worked for me.
This problem stopped happening when the Web Site project was converted into a Web Application project.
Not an easy solution, but it did stop the problem.
They symptoms in the question of this post sound exactly like the nightmares I just had today:
Other actions that sometimes seem to trigger the problem:
"Go to definition"
Opening a file
Previewing a file
Closing a file
Using a refactoring "Find usages"
Plus intellisense wasn't working (even with CTRL + J) and
'Peek definition' was hanging as well.
I had to keep task killing visual studio (both 2015 and 2017).
My fix was to go into the project that I was having problems with, open the 'Package Manager Console' and uninstall and re-install the 'DotNetCompilerPlatform'
uninstall-package Microsoft.CodeDom.Providers.DotNetCompilerPlatform
and then
install-package Microsoft.CodeDom.Providers.DotNetCompilerPlatform
So far every problem I was encountering has not resurfaced (but this was just today so still need to give it time).
UPDATE:
It started creeping back again. I noticed also that whomever had installed to the solution had only done it to two of the various projects. Uninstalling the compiler platform (which means using the compilers that came with Visual Studio) has made life sane again.