Fabio Cavalcante
Fabio Cavalcante
That's correct. With the current implementation, that is the case, which causes problems in any environment providing isolation with ALC (including Azure Functions)
The `DllImport` should work. We could validate this in Azure Functions. For context (@aderderian), we're only tracking this for Functions 3.0 at this point. FYI, @yojagad
That seems like a bitness mismatch. Are you running in a 32 or 64 bit app? Can you make sure it matches the native dependency you're deploying?
I agree that the current behavior is not ideal and unexpected. We need to be careful though, as changing this behavior would be a breaking change (customers may be relying...
@robertmclaws @bassem-mf , this hasn't been assigned, but I wanted to comment to make make you aware that your feedback is not being ignored :) We have a plan to...
Moving this back to the backlog/triage
@liliankasem the package is published and unlisted, otherwise, there would be a failure here. @jmullen974 this is purely NuGet behavior. Are you experiencing this in multiple environments? Can you share...
@CooperLink following up on stale ope PRs here. If this requires additional validation/discussions, can you either flag as a draft or close and reopen when ready for a review? Thanks!
Had a chat with @ealsur and @brettsam about this today. Some of this work is still in progress in other components, but this is hopefully something we can light up...
@dariagrigoriu we need to engage the VS team to assist with this.