-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Open
Labels
.NETIssue or Pull requests regarding .NET codeIssue or Pull requests regarding .NET codeBuildFeatures planned for next Build conferenceFeatures planned for next Build conferencemsft.ext.vectordataRelated to Microsoft.Extensions.VectorDataRelated to Microsoft.Extensions.VectorData
Description
MEVD provider implementations make frequent use of JsonSerializer.SerializeToNode() in various ways which are NativeAOT-incompatible. Examples include in mappers (e.g. in WeaviateDynamicMapper), when processing
To work on this, simply drop the following in a provider's csproj:
<IsAotCompatible Condition="$([MSBuild]::IsTargetFrameworkCompatible('$(TargetFramework)', 'net8.0'))">true</IsAotCompatible>This will start generating NativeAOT- and trimming-related warnings. Once this is done, it should be possible to remove [RequiresUnreferenceCode] and [RequiresDynamicCode] from the provider's dynamic collection constructor and to build without any warnings.
Metadata
Metadata
Assignees
Labels
.NETIssue or Pull requests regarding .NET codeIssue or Pull requests regarding .NET codeBuildFeatures planned for next Build conferenceFeatures planned for next Build conferencemsft.ext.vectordataRelated to Microsoft.Extensions.VectorDataRelated to Microsoft.Extensions.VectorData
Type
Projects
Status
Backlog