Skip to content

.Net: Bug: InMemory Connector is not StrongName signed and won't work for .Net Framework target SDKs #12363

@e1em3ntoDX

Description

@e1em3ntoDX

Hi,

This issue is pretty similar to the one I found here: #8928.

We at DevExpress are now implementing the semantic search feature for our Grid Controls using the Microsoft.Extensions.VectorData.Abstractions nuget package/assembly functionality. We reached the stage of implementing a demonstration example and chose the InMemory connector for these purposes. As our product demos are now mostly compiled against the .NET FW 4.6.2, we have to use the assembly, but the application does not start due to the exception.

Image

I didn’t include the repro steps because the issue seems straightforward, but please let me know if you still need them and the example demonstrating it.

Please let us know if you have plans to sign the assembly, and if so, is there any ETA available? We have the major product release coming in a few weeks, so the ETA might affect our future plans in this regard.

Thank you

Metadata

Metadata

Assignees

Labels

.NETIssue or Pull requests regarding .NET codebugSomething isn't workingmsft.ext.vectordataRelated to Microsoft.Extensions.VectorData

Type

Projects

Status

Sprint: In Review

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions