When creating DropboxClient I'm getting an unable to find System.Net.Http, Version=4.0.0.0 assembly

[BMurri]

Working on upgrading a 8.1 winphone app to API v2 and we get an exception about not finding/loading the System.Net.Http assembly whenever the constructor for the DropboxClient is called. Tried installing the System.Net.Http NuGet package and it says none of my project types apply. Tried installing the Microsoft.Net.Http NuGet package and it tells me that the assembly it found can't be used (it finds a version 1.5.0.0 and it requires a 4.0.0.0). Installing the v2 api nuget package didn't depend on any other packages for our project types.

Anyone have any ideas? I've tried rebinding in app.config with no success. I've tried creating other project types for the system.net.http nuget package and can't get it to create a reference to one of its included assemblies using any incantation that applies to WinPhone (meaning I don't have a clear path to follow trying to subvert the system).

Anyone else using DropBox with winphone 8.1 apps?

[Greg-DB]

Can you share the code that causes the error, and the full error/output you're getting? Thanks in advance!

[BMurri]

https://github.com/BMurri/WinPass

Project to run is "KeePass" within the solution.

Error is thrown in KeePass\Sources\DropBox\DropBoxUtils.cs line 12.

Exact same error is thrown using real devices running Windows Mobile 10 and emulators running Windows Phone 8.1.

System.IO.FileNotFoundException
Could not load file or assembly 'System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Stack Trace: at Dropbox.Api.DropboxRequestHandlerOptions..ctor(DropboxClientConfig config, Stringoauth2AccessToken)
at Dropbox.Api.DropboxClient..ctor(String oauth2AccessToken, DropboxClientConfig config)
at KeePass.Sources.DropBox.List.RefreshList()
at KeePass.Sources.DropBox.List.OnNavigatedTo(Boolean cancelled, NavigationEventArgs e)
at KeePass.Utils.KeePassPage.OnNavigatedTo(NavigationEventArgs e) at Microsoft.Phone.Controls.PhoneApplicationPage.InternalOnNavigatedTo(NavigationEventArgs e) at Microsoft.Phone.Controls.PhoneApplicationPage.Microsoft.Phone.Controls.IPhoneApplicationPage.InternalOnNavigatedToX(NavigationEventArgs e) at System.Windows.Navigation.NavigationService.RaiseNavigated(Object content, Uri uri, NavigationMode mode, Boolean isNavigationInitiator, IPhoneApplicationPage existingContentPage, IPhoneApplicationPage newContentPage) at System.Windows.Navigation.NavigationService.Journal_NavigatedExternally(Object sender, JournalEventArgs args) at System.Windows.Navigation.Journal.OnNavigatedExternally(String name, Uri uri, NavigationMode mode) at System.Windows.Navigation.Journal.DoExternalNavigation(NavigationDirection direction, Boolean isResumeActivation, Boolean isRefresh) at System.Windows.Navigation.Journal.NavigateTo(NavigationDirection direction, Boolean isResumeActivation) at Microsoft.Phone.TaskModel.Interop.Task.FireOnNavigateTo(Int32 direction, BooleanisResumeActivation)Uri: /Sources/DropBox/List.xaml?token=****************

[BMurri]

To build, you will need to copy the KeePass\Utils\ApiKeys.cs, renaming it ApiKeys.release.cs (in same folder), remove the lines starting with '#', and supply the appropriate keys & secrets.

[Greg-DB]

Thanks! We'll look into it.

[BMurri]

Any update? End of September is approaching...

[Greg-DB]

I don't have an update on this right now. I'll check in with the team.

[BMurri]

It's the end of September and this issue has still not been addressed. This is piss-poor support. I'm open to me doing something wrong, but I need your help because it's your code where the error is surfacing and you don't provide sources/symbols nor other helps to diagnose the issue.

Now the product doesn't work with DropBox, as the v1 api has been turned off, and the v2 api doesn't run in an environment tagged in the nuget package this error is produced in. No alternative workaround has been provided, except to drop DropBox.

We have done all we can up to this point to migrate. Please either make v1 available to our product until we've had a reasonable opportunity to react to the response we still have not received from you, or please explain why you only pay lip service to your developer ecosystem.

[Greg-DB]

Apologies for the delay here. This is still open with engineering, but I don't have an update yet.

We'll be happy to offer an extension to API v1 though. Please open an API ticket with the relevant app key(s) for that:

https://www.dropbox.com/developers/contact

[Greg-DB]

@BMurri Can you try v4.4.1 and let me know if that does or doesn't fix the issue for you? Thanks in advance!