Skip to main content
Solved

cognite-sdk-dotnet in production

M
Committed

Is there any known limitation in cognite-sdk-dotnet to be consumed in enterprise solution?

Best answer by Jason Dressel

@Mohit Shakaly 

I think we can close this. For now, the team does not require dotnet dll signing as they have identified a workaround.  If they require this in the future, we can add it to the shared SLB:Cognite Azure DevOps requirements backlog.

View original

J
Seasoned Practitioner
Forum|alt.badge.img

Mohit,
Can you kindly elaborate?  The dotnet SDK is a community SDK. It, and the dotnet extractor utils, are leveraged in cognite dotnet based extractors OSI PI and OPC UA (as examples)

Jason

 

Dilini Fernando
Seasoned Practitioner
Forum|alt.badge.img+2

Hi @Mohit Shakaly ,

Could you please elaborate your question as requested by Jason? 

Best regards,
Dilini

M
Committed

Hi @Jason Dressel & @Dilini Fernando ,

 

As cognite-sdk-dotnet package assemblies (like CogniteSdk.dll,Cognite.Extensions.dll,CogniteSdk.Types.dll) are not signed.

Could it be addressed by cognite?

 

Regards,

Mohit

R
1 person likes this
  • R
    Ramchandra Nile
J
Seasoned Practitioner
Forum|alt.badge.img

@Mohit Shakaly I believe the dlls are now signed.  Correct?

M
Committed

No @Jason Dressel, as the external signing changes the signature it’s own components can’t locate the assembly.

J
Seasoned Practitioner
Forum|alt.badge.img

@Mohit Shakaly 

I think we can close this. For now, the team does not require dotnet dll signing as they have identified a workaround.  If they require this in the future, we can add it to the shared SLB:Cognite Azure DevOps requirements backlog.

Reply


Terms & ConditionsCookie Settings

Cookie Policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings