Can't find the magnifying glass

[klumsy]

i have it installed, i can enable it for my project, and verify thats the case by what is allowed/greyed out in the linqbridge menu, compile, breakpoint, but i can never see this magnifying glass. I'm not sure whether its a conflict with other tools i have like reshaper. I'm on vs.net 2013. Is there a way to do invoke via a menu, right click, or hot key?

[codingadventures]

Hi Karl,

no it's definitely not a conflict with Resharper, I use it too and I have never had a problem. Could you please check a couple of things?

First off you need to rebuild your project/solution (and not just build) in order to generate the mapping after you have enabled your project. Go to this folder and check if there is any dll that contains the name of your enabled project(s):

C:\Users\yourusername\Documents\Visual Studio 2013\Visualizers

you should have something like this:

YourDllName.Visualizer.V12.0.dll DotNetDynamicVisualizerType.V12.0.dll --> this is a generic mapper for (almost) all .NET types

Let me know, and then we might need to check LINQBridgeVs logs

[codingadventures]

Karl I spotted the bug, there's a new version online (1.3.2). Please update/reinstall the extension and check if you have the correct dlls in the folder I mentioned above.

Thanks

[lateralthought]

I have encountered the same issue as Klumsy in visual studio 2013. I have rebuilt my solution and checked for the visualizer dll in the vs2013 visualizers folder.

Still no magnifying glass...Any help would be appreciated.

[codingadventures]

Hi,

please check few things: 1) is Visual Studio 2013 running as Administrator? 2) is the LINQBridgeVs version the latest (1.3.5)? you can check it in the about section in the LINQBridge menu (LINQBridge-->About) 3) Have you enabled your project/s by clicking "Enable LINQBridge"?

if you have done correctly all the three steps above we need to check the log files.

Let me know.

[lateralthought]

Good afternoon and thank you for the prompt response.

Visual Studio is running as admin. The installed version of LINQBridgeVS is 1.3.5. I have enable LINQBridge.

Where are the log files located?

Larry

On Tue, Apr 29, 2014 at 5:03 PM, Johnny Stark notifications@github.comwrote:

Hi,

please check few things: 1) is Visual Studio 2013 running as Administrator? 2) is the LINQBridgeVs version the latest (1.3.5)? you can check it in the about section in the LINQBridge menu (LINQBridge-->About) 3) Have you enabled your project/s by clicking "Enable LINQBridge"?

if you have done correctly all the three steps above we need to check the log files.

Let me know.

— Reply to this email directly or view it on GitHubhttps://github.com/nbasakuragi/LINQBridgeVs/issues/14#issuecomment-41746889 .

[codingadventures]

Hi Larry,

you can find log following this path:

%HOMEPATH%\AppData\Local\LINQBridgeVs\LINQBridgeVs.txt

Reason of that problem is the extension couldn't activate a post build event. Firstly check that log and please send me it at this address:

linqbridgevs@gmail.com

Check other two things if you can:

go to: %ProgramFiles(x86)%\MSBuild\12.0\Bin and check if:

1) BridgeBuildTask.targets is in the folder 2) open Microsoft.Common.targets and go at the very bottom. you should find this:

<Import Project="BridgeBuildTask.targets" />

have a nice day

[codingadventures]

Hi Tommy,

I sent you an email there.

[chizran]

Has this been resolved? I have the same problem. There is no BridgeBuildTask.targets on my filesystem, and in the log file I can see the following:

2014-06-13T11:42:15.4021898+02:00 BridgeBuild.targets Removed for x86 Operating System

2014-06-13T11:42:15.4131904+02:00 BridgeBuild.targets Removed for x64 Operating System

2014-06-13T11:42:15.4191908+02:00 BridgeBuild.targets Removed for framework 4.5

This is on Visual Studio 2013.

[codingadventures]

Hi,

BridgeBuild.targets has been removed since version 1.3.7.

Your problem might be missing permissions on the folder Documents/Visual Studio 2013/Visualizers Please try to add the user "Everyone" to the Visualizers folder (from the Security tab on the folder properties)

There is a new version coming up soon with few fixes for these issues.

Let me know how you get on with that.