Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Test with an ASP.net Core project #42

Closed
vbjay opened this issue May 18, 2018 · 5 comments
Closed

Test with an ASP.net Core project #42

vbjay opened this issue May 18, 2018 · 5 comments

Comments

@vbjay
Copy link

vbjay commented May 18, 2018

image

image
@codingadventures
Copy link
Owner

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

@vbjay
Copy link
Author

vbjay commented May 18, 2018 via email

@codingadventures
Copy link
Owner

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
Copy link
Author

vbjay commented May 18, 2018 via email

@codingadventures
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@codingadventures @vbjay