-
Notifications
You must be signed in to change notification settings - Fork 0
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
Client never initializes on .NET Framework 4.8 MVC Application #31
Comments
Hello @rkajbaf-experientgroup and thank you for your feedback. Are you able to collect any logs? Could you please provide a code snippet of your configuration and call to start the SDK? Thank you! |
Another theory is that a cache or lockfile is holding a version of a library or dependency. Have you tried a clean build and/or do you use a package lockfile? |
I am also having this problem; unrelated to the individual who posted this originally. I even opened a Stack Overflow post a couple months ago: |
Here is the console output related to launch darkly: 'my.exe' (CLR v4.0.30319: my.exe): Loaded 'C:\my-project\bin\x64\buildconfig\LaunchDarkly.CommonSdk.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. |
Based on the output, above dug in some more. Was able to resolve it following the steps here: |
Tried to reproduce this issue by creating a .NET Framework 4.8 class library and then using that in a console application. It appears to have worked fine, so at the moment we cannot reproduce this. |
Is this a support request?
No,
Describe the bug
Fails to ever initialize in a .NET Framework 4.8 Web Application on the latest version (8.0). Downgrading to 7.1 resolves the problem.
To reproduce
Try on a .NET Framework MVC Application. Client will never initialize.
Expected behavior
Should initialize.
Logs
If applicable, add any log output related to your problem.
SDK version
8.0
Language version, developer tools
.NET Framework v4.8
OS/platform
Windows
Additional context
Downgrading to 7.1 resolves the problem.
The text was updated successfully, but these errors were encountered: