I have a problem using VS 2017 15.3.3
I like to show a wpf window in the buildin debugger visualizer, and get the error above.
Things I tried:
on another machine the visualizer shows up with same project
a newly created wpf project also fails
rebooted several times
followed the advice here: Stackoverflow "Show Visualizers Error", but did not get any information from the attached visual studio (no errors during visualizer start)
The visual studio environment was updated from VS 2015, and I had used the debugger visualizer "mole" from Shifflett/Smith in VS2015/VS2017, but deinstalled them now.
Next step may be reinstall of vs 2017 but I like to hear if there are any other things to check beforehand...
Related
I've created a custom visualizer in Visual Studio 2019 but I'm having trouble activating it on a specific machine (it works on two other machines, so it's not related to the code).
I've placed the visualizer (called DocumentVisualizer.dll) in the MyDocuments\Visual Studio 2019\Visualizer folder and at debug, when checking the object I see the magnifying glass as expected.
But when I click on it, this is the error I see Unable to load the custom visualizer
It mentions that the issue could be related to Microsoft.VisualStudio.DebuggerVisualizers.dll version but I'm not sure of how to check this. (I've installed only Visual Studio 2019 on this machine)
This appears to be a machine-specific problem as I could load the visualizer on a couple of other machines.
Any clues on how to fix that?
I've tried cleaning the output, restarting the machine and reinstalling Visual Studio with no success.
I have a project that is working correctly on Visual studio 2013 Ultimate.
Now we have installed Visual studio 2017 Enterprise.
When I compile and run my project on VS2017 , on several lines of code I receive a strange error message :
"Cannot obtain value of the local variable or argument because it is not
available at this instruction pointer, possibly because it has been optimized away."
What can I do , because on VS2013 I had no problems at all.
Thank you !
uncheck in the project "optimize code"
Also, set the debug info dropdown to full in the advanced options
go to Debug->Options or Tools->Options
and check Debugging->General->Suppress JIT optimization on module load (Managed only)
if you would like a technical reason, you need to post your code
I'm using Xamarin with Visual Studio 2015. After a recent upgrade of the Xamarin plugin, I'm getting an error the first time I try to "Clean Solution" or "Build Solution" after launching Visual Studio:
The Xamarin license file is invalid and could not be recovered. You will still be able to access the Xamarin features that are included in Visual Studio Professional.
The error dialog offers a single option: "Use Visual Studio Professional". If I choose that option, I can re-try whatever operation I was using and it will work fine, and continue to work fine until I exit and re-launch Visual Studio.
I have found some older threads where people mention what seem like similar problems, but the solutions refer to using Tools->Xamarin Account, which does not appear anywhere in my Visual Studio "Tools" menu.
Specific versions in play:
Microsoft Visual Studio Professional 2015 14.0.25431.01 Update 3
Xamarin 4.8.0.754
Xamarin.Android 8.1.0.13
I have this same problem with a couple of different, unconnected solutions (one of which is using Xamarin.Android, another of which uses Xamarin.Forms).
For some reason I cannot check in my code to our Visual Studio Online account. Other developers can, but not me. This is the error I am getting:
"Could not find dataspace with category VersionControl and identifier [some guid]"
Searching for any help on the above error is not returning anything meaningful.
This started to happen after I installed Visual Studio 2015 Enterprise. I launched it for the first time after creating a new web application with Visual Studio 2013. I then opened that new solution in 2015 and all was fine. Things began to go awry once I tried to put it in our Visual Studio Online account. When I went to Team Explorer in VS 2015 I selected "Projects and My Teams / New Team Project". This then bounced me over to our Visual Studio Online account in the browser for me to fill out that simple form to create a new team project. I filled the form out and submitted. I then got an error that the project was not successfully created. Unfortunately Visual Studio still thinks it was created and it shows up in the list of projects ONLY WITHIN Visual Studio -- it does not show up online. Eventually I just became frustrated and deleted everything related to all that I just tried but then learned that I cannot check anything in now on my old projects! I had other developers test and they still can so the problem evidently is on my machine. I then uninstalled VS 2013 and VS 2015 then reinstalled VS 2013 and am still having the problem.
I am hoping someone can point me to some cached junk that needs to be cleared on my system. :-)
This is a bit shot in the dark, few things you can try:
Delete the local cache under:
%localappdata%\Microsoft\Team Foundation
%localappdata%\Microsoft\VisualStudio\14.0\SyncSettings
Open cmd. Type:
"%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\Common7\Tools\vsvars32.bat"
Verify connections: tf settings connections
Run Visual Studio in safe mode (devenv.exe /SafeMode)
Run Visual Studio with activity log (devenv.exe /log) and check for errors.
I'm unable to open Marmalade MKB Files in Visual Studio 2013 Pro, while my other class mates can with the exact same version of Visual Studio. I've tried multiple projects but unfortunately I'am unable to open any. I've already tried to reinstall Marmalade.
The error message I get is:
Unsupported This version of Visual Studio is unable to open the
following projects. The project types may not be installed or this
version of Visual Studio may not support them.
Sounds like you may have set the mkb to be opened by visual studio as default instead of Marmalade.
So instead of Marmalade taking the mkb and turning it into a visual studio project and then opening it Visual Studio is just trying to open the .mkb file it doesn't understand.
Try right clicking on the mkb and choosing Open in Hub (or similar) from the context menu. You should be able to then open in IDE from there and have it open your project in visual studio. If you still get the same error then it means the problem is probably something else. If it works you'll have to stop visual studio being the default that will hopefully let marmalade take over again
Good Luck