Level up your Box knowledge with brand new learning paths on Box University. Visit training.box.com to get started

Box Status

Box SDK for UWP

Answered
Follow
New post
ptallett

Hi!

 

I have a two UWP apps that use the Box SDK V2.14.0, one using UWP 14393 and one using UWP 16299 (which I can;t change).

 

With the upcoming TLS deprecation, I need to update to Box 3.5.2 or better. However, doing so causes a .NET runtime mismatch. I get similar problems trying to use the .NET Standard version.

 

What's the recommended way of supporting Windows 10 UWP?

 

Cheers,

Paul

0

Comments

5 comments

Date Votes
  • mwiller

     Hi, I'm Matt — I'm one of the engineers who works on the Box .NET SDK.  First, since the TLS deprecation is coming up *very* soon, it would be helpful to get some information from you about exactly what environment you're running in so I can give you the most correct and relevant information.  Which version of .NET Framework are you compiling against currently?  Have you been able to test your application against https://api-test.box.com — which has already removed support for TLSv1.0 and can tell you if your application is compatible or not?  

    0
    Comment actions Permalink
  • ptallett

    Hi!

     

    As I said I have one using UWP 14393 and one using UWP 16299 (which I can't change). These are UWP apps so don't have a desktop .NET Framework version.

     

    I was unable to test against the test server as the suggested code doesn't compile

     

    BoxConfig config = new BoxConfig(/* config parameters */);

    config.BoxApiUri = new System.Uri("https://api-test.box.com/2.0/");

     

    BoxApiUrl is readonly and cannot be assigned to.

     

    I assume as my app uses an old SDK, it will break soon.

     

    Cheers,

    Paul

     

    0
    Comment actions Permalink
  • mwiller

     The .NET Standard version of the SDK should support UWP 16299, but the older UWP version is not supported in the current version of the SDK (which targets netstandard1.6).  If these UWP versions do not support TLSv1.1 or above then your applications will unfortunately no longer be able to contact the Box API after June 15th.

    0
    Comment actions Permalink
  • ptallett

    Hi!

     

    So an app that targets UWP less than 16299 cannot use Box? That's sad, I will have to remove that functionality, my users will not be happy.

     

    When I try to use .NET Standard in my 16299 app I get

     

    System.IO.FileLoadException
    HResult=0x80131040
    Message=Could not load file or assembly 'System.Runtime, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

    0
    Comment actions Permalink
  • mwiller

    It's not really the version of UWP that we're concerned with, just TLS support.  An app that does not support at least TLSv1.1 cannot use Box after June 15th for compliance reasons, but we have made some code changes to recent versions of the .NET SDK to try and ensure that it uses TLSv1.2 whenever possible since some versions of .NET have support for TLSv1.2 but do not enable it by default.

     

    I'm not an expert on UWP, so I'm unsure which versions of TLS it supports or enables by default, but if it's running on Windows 10 it may be okay without any changes!  It mostly just depends on how it handles HTTPS connections and which protocol versions it uses by default.

    0
    Comment actions Permalink

Please sign in to leave a comment.