-
Notifications
You must be signed in to change notification settings - Fork 64
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.
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
Support for asp.net core targeting full framework #36
Comments
Hi @blebaron , The reason for your exceptions is, you are using I suggest to use ASP.NET X-Ray handler for Is there any specific reason for a use case where you change the framework from Thanks, |
Sorry for the delayed response. I got this working by manually pulling out the .net core assemblies from the nuget packages and referencing them directly and then forgot that I had logged an issue. I'm using the asp.net core MVC constructs (startup, kestrel, etc...) inside of a full framework project. That's why I can't use the |
Hi @blebaron , Best, |
I'm not sure why this was closed nor how @blebaron worked around the issue. Targeting kestrel and asp.net core is recommended for .net framework developers. How can xray instrument asp.net core on this platform? |
I'm working on an asp.net project that is targeting the full .net framework. I get the following error when attempting to use the asp.net core XRay library:
I haven't dug in to try and find where the issue is but I have created a simple example that illustrates the issue here: https://github.com/blebaron/AWSXRayExample
I created the example by using the VS 2017 asp.net core api new project template and then modifying it to target the
net461
The text was updated successfully, but these errors were encountered: