I generated .coverage file using the Performance Tools in VS2010. I can follow all steps to get the .coverage file in command line.
but i have VS2010 Professional version, so that i cannot open the .coverage file and see the coverage inside VS2010 (or can I do so?). Is there a way to see the results another way, using freeware etc... ?
For instance is there a way to get the Microsoft.VisualStudio.Coverage.Analysis.dll and have it working fully in VS2010 PRO ?
Thanks
Related
I hope this is not a duplicate, as I have been searching the web for a while looking for solutions to my issue.
So, I am working in this C++ project from the lab I work at which works just fine in CLion and Visual Studio. However, I'm trying to run it in my local machine with Visual Studio Code and have installed the extensions C/C++ and CMake Tools by Microsoft, and CodeLLDB by Vadim Chugunov.
When I open the folder which contains the CMakeLists.txt file and locate it with the CMake extension, the project is detected and mounted just fine in the CMake tab. The project structure is there, and I can even build it. However, I am not able to access the files through the CMake tab (to edit them and insert breakpoints), as I get this error:
Unable to open 'main.cpp': Unable to read file
'/home/leonardo/Git/MPMc/MPMc/cmake/Git/MPMc/MPMc/MPM/main/main.cpp'
(Error: Unable to resolve non-existing file
'/home/leonardo/Git/MPMc/MPMc/cmake/Git/MPMc/MPMc/MPM/main/main.cpp').
I see it is reasonable that the program cannot read the file, as its address is looped within itself. So what I really wanted was to know how to avoid this behavior so VS Code could see the real address of the files and allow me to access them.
BTW, I am running a Manjaro 18 system and didn't have the same problem with the lab machine, which runs Debian 10.
Could you guys give me any tip as to what could be the solution to this issue? Is this a VS Code issue or a system issue?
Thanks!
I have attached image of my compiler. My cygwin terminal will not create .exe file for my C++ program? I do not see exe file in my project diretory. I have used cygwin to compile code before, so I do not understand why it does not work.
VScode does the same thing as well?
Does anyone know a possible solution?
I have found that the full version of Visual Studios works much better than VS Code for compiling EXE's. You can get it for free here: https://visualstudio.microsoft.com/vs/
I have a .EXE file which I need to debug using VCEXPRESS using the code in an existing Visual Studio solution (.sln). Basically I trying to do something like this:
VCEXPRESS.EXE program.exe -use project.sln
I know I can do this
VCEXPRESS.EXE program.exe code.cpp
But then I may not be able to navigate through the whole code as VCEXPRESS only sees code.cpp. and also the .exe file contains the code in the solution plus some extra code. Is there is a way to achieve what I am trying or anything similar to it?
I would really appreciate your help.
I debug it using different VS versions. One workaround I could think of is using the /DebugExe, but it doesn't work if I use the Express version since it has many limitations in command line.
https://msdn.microsoft.com/en-us/library/ms241274.aspx
But if I use the VS2015 community version which was also free in command line, I could debug the specified executable file. Would you please use the high VS version like the community which is also free and it has much more features than express version.
If I have misunderstood this issue, please feel free to let me know.
I solved it. The solution is to open the VS solution and use visual studio commands to add the .exe file as an existing project. It will be something like this
VCEXPRESS.EXE solution.sln /COMMAND "File.AddExistingProject program.exe"
You can also open a source code file like this
VCEXPRESS.EXE solution.sln code.cpp /COMMAND "File.AddExistingProject program.exe"
This will open the solution and code.cpp in the editor, then add program.exe as an existing project and allows you to debug it.
I hope someone in the future finds this answer useful.
Currently we are migrating our applications developed in Borland C++ 5.02 on Windows XP to Windows 7. While executing the application on Windows 7, I am getting the error message
VBX library init Failure.
While trying to find the cause on the Internet, I was able to identify the error was because of BIVBX31N.EXE and BIVBX31N.dll.
How can I port a Borland C++ 5.02 application to Windows 7, solving the BIVBX31N.EXE and BIVBX31N.dll related issues?
If you're stuck using this product, here is what I recommend.
Simple answer: Don't use the IDE, but continue to use the command line tools:
bcc32.exe (the compiler) still works fine in Windows 8.
ilink32.exe (the linker) still works fine as well.
Both can be found in the bin sub-folder.
You can get some of the command line information by opening the IDE (project) file in Notepad or a hex editor (it isn't a text file, but you can read most stuff in Notepad). Or if you do have access to Windows XP you can open it there just to copy the settings for usage in the command-line tools.
Just use some other IDE or editor like Notepad++ to edit your source files. You can use an older version of Visual C++ to edit the RC files, or Notepad or other tools.
If you want really want to make it slick, set up your IDE to run an "external tool" when you click a toolbar button, to have it run your command-line tools to compile + link (and optionally run the EXE file). You can probably find a debugger tool as well, but I haven't needed that yet, so haven't checked.
My best recommendation is to start the process of porting your code to Visual Studio.
You can use a library like OWLNext if you've used the OWL library in Borland.
The other alternative is is to use Windows Virtual PC (or other such virtual machine) to run Borland in an integrated Windows XP mode. See an example here.
This can be probable answer ???
You have to download configured Borland Compiler from http://www.4shared.com/get/Gs41_5yA/borland_for_graphics.html or http://dwij.co.in/graphics-c-programming-for-windows-7-borland-compiler/.
Put your Borland’s ‘bin’ folder into Environmental Variables.
Now go inside folder ‘bin’ & edit file bcc32.cfg as per your folder structure. This file contains settings of headers & libraries.
-I"D:\Borland\include;"
-L"D:\Borland\lib;D:\Borland\Lib\PSDK"
Now create any C/C++ Program say myprogram.cpp
Use following command to compile this bunch of code:
F:\>bcc32 myprogram.cpp
Congratulations !!!.
Does anyone know how to debug the LSP sample provided with Microsoft platform SDK? I read about this topic and found that the sample dt_dll generate a DLL file that can be used with a checked version of ws2_32.dll.
The problem is that they are not saying how to do it. How to use the dt_dll.dll file? How to include it? How to debug it? The whole process is not clear.
Also, I tried to created a log file in the code of the LSP sample. The file was not created even though the LSP was loaded and the networking operations are functional as normal.
I need a way to check what I am doing (using a log file, or debugging the LSP).
I am using Windows XP with Visual C++ 2008 Express.
Any ideas?
Let's assume that your LSP and its installer have been built successfully. And assume that the installer has successfully installed the LSP. Let's call it lsp.dll.
Then all applications using winsock, eg ws2_32.dll will also load your lsp.dll.
Verify it by open the command line console and type:
tasklist /m lsp.dll
If your browser is running you should see it in the list outputted by the above command. Attach your debugger to your running browser, you should be able to debug your LSP dll.
In Visual Studio, go to Debug->Attach Process->Select your running browser, eg IE.
You can certainly write to a log file from your LSP. However, please note that your lsp has the same privilege as the host application and it might not have permission to write file.