search

codingadventures / LINQBridgeVs

Dumps the content of variables during debugging in Visual Studio to LINQPad
MIT License
127 stars 21 forks source link

Test with an ASP.net Core project #42

Closed vbjay closed 5 years ago

vbjay commented 6 years ago

image

image

codingadventures commented 6 years ago

This seems a trickier one. I wonder if the generated linqpad script references the assembly BRC.API.Distributor.dll could you please check?

vbjay commented 6 years ago

It does not and it generates an EXE not a dll. When I add the exe I get a bad image exception. I know it is going to be trickier. Wanted to give you a heads up.

On Fri, May 18, 2018 at 11:21 AM codingadventures notifications@github.com wrote:

This seems a trickier one. I wonder if the generated linqpad script references the assembly BRC.API.Distributor.dll could you please check?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/codingadventures/LINQBridgeVs/issues/42#issuecomment-390241864, or mute the thread https://github.com/notifications/unsubscribe-auth/ADdhsSTf8CJnXHVzWsyVOQ-P99TGUnJgks5tzub8gaJpZM4UE3Wd .

codingadventures commented 6 years ago

Thanks Jay for the heads up. When I tried this extension with a .NET Core project it didn't work, so I'm surprised that it didn't raise an exception within visual studio when you exported your variable. I guess I have to spin up an asp.net core project and see for myself. Just out of curiosity, are you using the latest version of VS2017 (15.7) ?

vbjay commented 6 years ago

Yes.

On Fri, May 18, 2018 at 11:27 AM codingadventures notifications@github.com wrote:

Thanks Jay for the heads up. When I tried this extension with a .NET Core project it didn't work, so I'm surprised that it didn't raise an exception within visual studio when you exported your variable. I guess I have to spin up an asp.net core project and see for myself. Just out of curiosity, are you using the latest version of VS2017 (15.7) ?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/codingadventures/LINQBridgeVs/issues/42#issuecomment-390243557, or mute the thread https://github.com/notifications/unsubscribe-auth/ADdhsZYm10nPa-F98y5dfVNCivtpaZeQks5tzuhsgaJpZM4UE3Wd .

codingadventures commented 5 years ago

support for .net core, .net standard is not available. custom debugger visualizers only work on the full .NET framework. There a user voice suggestion to add them in visual studio. In the upcoming release of LINQBridgeVs 1.4.7 there will be an error if a solution containing un-supported projects is LINQBridged