I'm on a VB.Net Winform project and I have encountered a strange problem with my IDE Visual Studio 2019.
When I double click in the solution explorer to open the form in visual editing mode, it shows up but with a wrong resolution, the form and everything in it becomes far bigger than it should be. But when I run the project in debug mode, the runtime resolution is normal.
I do have two monitors but I never had this issue before, it would be great if someone knows why and has a solution for it.
Problem was solved after a reboot. I think it was a pending windows update who caused this . Very often, a pending windows 10 update causes a problem, I've experienced the blue screen, wifi connection failure, and this time a resolution problem. Intentionally or not, it forces users to restart the computer to apply the update. Hope this can serve other people.
Related
I'm developing a vsto outlook plugin and works perfectly when I run on debug mode. If I install it, it's always disabled automacally and I can't make it work.
Does anybody knows what's happening or could I do to figure out what's the problem?
We have encountered times when our Chem4Word add in has been hard disabled. This may have caused by pressing the stop button in visual studio during debugging! This makes word think the add in has crashed. In our case it was only apparent when trying to run it as an installed add in, running in visual studio IDE never showed an issue.
See here for instructions on how to clear any hard disabled add ins
https://learn.microsoft.com/en-us/visualstudio/vsto/how-to-re-enable-a-vsto-add-in-that-has-been-disabled?view=vs-2019
I think that this applies to all versions of office.
You can also look in the registry at
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Word\Resiliency\DisabledItems
Substitute your target application and version number as appropriate.
The key should not have any items if nothing in hard disabled.
When Visual Code asks for a update it fails and says code.exe is locked, I check with lockhunter.
I tracked the issue to the task manager, and process id 4 memory management I think is using it. I have to restart the pc to get the file deleted and I need to download visual code again. All my colleagues have the same issue.
Any ideas on how to solve this?
I found out it was the company software blocking the update. Seems silly.
Please close it.
I use Android Studio 0.8.6 for Android Development, and when I'm editing a file, it will freeze, and I have to restart computer to close it, since System Monitor (I am on Ubuntu 14.04 LTS) won't close it. It's always the same file I'm editing, this never happens with any other file. It shouldn't matter, but the name of the file is sun_vertex_shader.glsl. There's no error, or log output, or anything.
Here's exactly what happens - I'm typing in the file, the cursor freezes, stops blinking, and the mouse pointer is an I-beam, no matter where in the window I move it. The window doesn't close when I press the X, and when I restart my computer and open Android Studio again, I start editing the file and seconds later, it happens again.
I know you probably can't help me without any error logs, but I couldn't find any. If you know where I could find them, I will post them here.
I found out what is causing this: the GLSL plugin I downloaded from here is causing Studio to freeze, as I have read in the comments.
Please check your system Date/Time and correct it, this problem occurred if your system date does not match with current date.
I was playing with the simulator that comes with VS 2012 and decided to crank up the resolution to see if my app would look well in high resolutions. Little did I realize how much that would demand from my machine. The simulator crashed and I haven't been able to use it since. I can start it outside of visual studio but as soon as I click anything it freezes and starts to lock up my machine. I'm running Windows 8 in a virtual machine so it's already a bit resource limited.
Is there a way (either through the registry or some other means) to reset the simulator settings? I need to turn the resolution back down so I can actually use it to test my apps.
This is definitely less than optimal, but I found a solution if you are desperate. I decided to repair VS 2012 to solve some other things and it seems to have reset the simulator settings.
This just further confirms that there has to be a simple way to do this because the installer probably just copied default registry settings in place with fresh copies of the files. Therefore I'm not going to accept this answer for at time so that others can see this and hopefully offer a better answer.
I have recently put together a new development machine and loaded Windows 7 64 bit and VS2010.
I copied over all my projects (VB) from the old machine which was Windows 7 x86 and VS2008.
After following the conversion wizard in VS2010 and installing a third-party component I had forgotten about, my solutions opened and executed fine on the new machine.
Then I tried to work on one of my projects via RDP from a Windows XP machine (something I have done many, many times with the old machine) and the project crashes when run. I get the "no source availiable" tab and an AccessViolationException as soon as the splash screen has loaded. Going back to local operation, the project runs fine.
I've Googled this one to death and I can't find anything that relates to this problem at all. Any sugggestions would be gratefully received.
Thanks.
I do have multiple monitors but have never had a problem before with RDP. Anyways, I found other problems when opening other, older, projects in VS2010 so I uninstalled and reverted to VS2008. All OK now. Thanks for your help.
I was having an issue running Visual Studio 2010 via RDP where the IDE contents except the Solution Explorer wouldn't render. I went to Options->Environment->General->Visual experience and turned off the the "rich client visual experience" options. I suspect turning off "Use hardware graphics acceleration if available" did the trick.
I had also problem with RDP working in "windows 10"
My connection other computers always run successful, but closing after 5-15 second. I very long try fix this error. And I open this exception in VS2015 and read full excaption:
Unhandled exception at 0x00007FFBE35A8283 (ntdll.dll) in mstsc.exe: 0xC0000374: Куча была повреждена (parameters: 0x00007FFBE35FF6B0).
At first I thinked my PC have truble with RAM memory, but I decide change RDP settings and it began work without problem.
I changed the picture quality and uncheck using printer in other window.
My rdp workin very nice now.
I tried many fixes
From the microsoftware, with updates and system files, but nothing helped. I am writing now if someone with the same collision can solve temporarily the problem by lowering the quality of the picture. On a remote computer, it may be very important to simply connect, especially if it is a server.