Visual Studio not abe to link Source code with PDB for dmp file analysis - visual-studio-2019

I have a .dmp file which needs debugging.
When I build the project in Visual Studio, it gives me x64 binaries PDB, DLL.
When I check dissassembly code, I have choosen view source code, but still it doesn't show me the right plce in sources where the pointer null reference crash is occured.
Completely new to Visual Studio 2019 debugging/development, any help is appreciated.
Thanks.

Related

C# & Visual Studio : storage issue

I have a problem with Visual Studio.
When I create a new project and start programming and in between I save, at some point when I want to run it, Visual Studio does not accept my new code. It always executes the old code although I have overwritten it.
I have already re-downloaded Visual Studio 2 times but that didn't help. I use Visual Studio Community 2019
Try using Ctrl+shift+B to build it, and then running with F5, instead of Ctrl+B or F7.

Microsoft Visual Studio Community 2019 CodeLens reference counter incorrect

I have a Windows Forms App with .Net Framework 4.8 and suddenly I realized that only a vertical line appears instead of the reference counter. Any idea how to fix it?
This applies to most of my solutions,but not all. I also noticed that if I reinstall Visual Studio it works after the first start, but once I close it and open it again the error comes back.
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE>devenv /resetuserdata" solved my problem.

F# filetypes icons missing

So after updating visual studio 2017 to the 15.8.8 version the .fs .fsi and .fsx filetypes have no icon on windows explorer.
I have checked the following registry keys to see if they were there, but no...they aren't.
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\
and
HKEY_CLASSES_ROOT\
I found an issue in GitHub
https://github.com/Microsoft/visualfsharp/issues/4017
So I could find for other filetypes like .cs or .cpp there is a registry key
like HKEY_CLASSES_ROOT\VisualStudio.css.aaa3ca14\DefaultIcon with the value of the dll where the icon is taken from
Could someone please provide me with the keys and values for the extensions
.fs .fsi and .fsx ?
I uninstalled, cleaned up the registry and installed again the visual studio 2017 and the problem is still there.
Win 10 [VersiĆ³n 10.0.17763.55]
Visual Studio 2017 Enterprise 15.8.8
F# 4.5
edit:
found two issues more:
https://github.com/dotnet/project-system/issues/3351
https://github.com/dotnet/project-system/issues/3352
For the time being, I found a workaround by exporting the reg keys from a working machine where VS2015 was installed.
I created a repository in case someone has the same problem until they fix the issue.
https://github.com/blfuentes/Fsharp_File_extensions

cannot be opened. The project type is not supported by this installation

.cs project file
The project was created using Visual Studio 2010 and I am trying to open it in Visual Studio 2010 itself but still I am facing this problem.
I have opened this project in VS 2012 and worked for few days but it has created in Visual studio 2010. Is there anything which preserve the project details on local machine?
This is the specific project section in my solution file:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2010
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Project Name", "Project Name\project name.csproj", "{48C1190E-7700-461B-ADCD-B5E0F1ECAD21}"
ProjectSection(ProjectDependencies) = postProject
{1F5440B3-9FD8-4FE2-B621-8697489ABDC4} = {1F5440B3-9FD8-4FE2-B621-8697489ABDC4}
EndProjectSection
EndProject
In Visual Studio it is possible to add Project Types, e.g. for creating an MSI, by installing an Add-On to the development machine. It appears that in the past this was done, and then that new Project Type was used to add a Project to the Solution. But now you are opening the Solution on a machine that does not have that new Project Type.
Look for the GUID of the missing Project Type, it should be part of the error you are getting. Then google "project type {the-guid}" to see which Add-On you need to install on your development machine.
It is also possible that a new Project Type was used in the Solution that simply can not work with VS 2010. In that case your options are either to keep using VS2012, or to start over with a new Solution in VS2010 and migrate the projects into it that are compatible (which may be a bit tricky or hard to do if VS2012 saved them).
Would it be too difficult to just recreate the project and include all the necessary files and references? Once the project was saved from VS 2012, the format may have broken compatibility with 2010. Sometimes this is fixable just by updating the version number in the project file, but I don't see it in your image.

Can't find VersionControlExt using VS2013

I want to code a VSPackage and need to get the selected items from Source Control Explorer History. I'm pretty sure that I need VersionControlExt, but I can't find the namespace Microsoft.VisualStudio.TeamFoundation.VersionControl using Visual Studio 2013. Can you help me?
You can use a NuGet package Microsoft.TeamFoundationServer.ExtendedClient. I'm not sure if these are too new to work against VS2013 but it's easiest to test.
If the NuGet package doesn't work, you can get the DLLs on your machine. These DLLs are stored in the Private Assembly cache of Visual Studio. You can edit the register to allow Visual Studio to search through these folders. See the first step of this post for details: Step 1: Help Visual Studio Find Team Foundation Assemblies

Resources