Not working with Windows 7 64bit, VS2010 Professional

[Witold Czajewski]

I had installed and been using your extension on 32-bit XP machine and it worked
nicely. Then, recently, I installed it on 64-bit Windows 7 computer only to find
out that it is not working. After registering Native Viewer, the debug
information is corrupt. When I hover the mouse pointer over an image variable
(Mat of course) I see something like that:
+ image = {???}

instead of the normal situation (when NV is off):
+ image = {flags=1124024336 dims=2 rows=512 ...}

When I click on the + to unroll the little pop-up window with image properties,
they are all there in both cases, still, with NV on, there is no image preview
(yes, I remember about the Ctrl key) and these three annoying question marks are
shown.

In both cases, the code compiles and executes correctly.

On both machines I use Visual Studio 2010 Professional.

That would be great if you could have a look at this problem. If you need any
assistance in recreating it, sending some dumps or screen shots, I am more than
willing to help.

Thanx

Witek

[Mikhail Matrosov]

Hello,

With these question marks VS trying to tell us it has a problem with loading debugger extension dll.

Please, check the autoexp.dat file located at C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Packages\Debugger\, find the line starting with "cv::Mat=$ADDIN" - it is the line NativeViewer is adding in the file when it is being integrated. Paste this line here.

There is a path to the NativeViewer10.dll in this line. Please, check the dll is actually located in the path. Check whether you have access to this dll from the user you are using to run VS (you actually should, since you've probably installed the VSIX using the same VS).

Thanks for the report, waiting for you reply.

[Witold Czajewski]

Hi

The line you mention looks like this
cv::Mat=$ADDIN(C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Mikhail Matrosov\NativeViewer\1.0.0\NativeViewer10.dll,CvMatViewer)

and the path is correct, the dll file is in the above mentioned folder and it looks like I have full rights to the file. However, when I rename it or delete it, the effect is exactly the same, which might mean that the file is not actually used anyway.

By the way, when I run VS2010 normally (not in admin mode) it crashes during integration.

[Mikhail Matrosov]

The bug is caused by parentheses in the path: "(x86)". I was able to reproduce it. The extension should normally be installed in the user-specific directory, but it seems like I accidentally enabled installation in a machine-specific path. I will fix this and publish updated version as soon as possible.

As a hot-fix, you can copy all dll files from extension's folder to a different folder, like "c:\temp\NativeViewer" and update path to NativeViewer10.dll in the autoexp.dat file.

Thanks a lot for your help!

[Witold Czajewski]

I am happy that you found the solution and that I could help :)