search

box / box-windows-sdk-v2

Windows SDK for v2 of the Box API. The SDK is built upon .NET Framework 4.5
https://developer.box.com
Apache License 2.0
186 stars 163 forks source link

Windows 7 64-bit Visual Studio build issues #8

Closed Geekly closed 10 years ago

Geekly commented 11 years ago

I'm trying to reference the Box.V2 library in a 64-bit library. The application I'm building is an add-on to a 64-bit application (Solidworks). This is requiring me to build a 64-bit library, but I'm having issues with deployment. The app works fine on my development machine, but I get file not found exceptions when I run on my 64-bit virtual machine.

Specifically, I'm having problems with Nito.AsyncEx. I suspect it's because I can't find a 64-bit version of that library, but I'm not sure. If anyone has suggestions or can recommend build settings, that would be fantastic.

Thanks.

brianytang commented 11 years ago

I unfortunately have not come across this issue myself.

Have you found a work around or are you still blocked by this?

Geekly commented 11 years ago

I'm still having issues. If nothing else, I'd love to get some pointers on including the box libraries within another 64-bit class library project.

On Thursday, November 14, 2013, brianytang wrote:

I unfortunately have not come across this issue myself.

Have you found a work around or are you still blocked by this?

— Reply to this email directly or view it on GitHubhttps://github.com/box/box-windows-sdk-v2/issues/8#issuecomment-28526416 .

Geekly commented 10 years ago

I should mention that I'm working exclusively on Windows 7. Is there anything particular for that OS? Are there plans to make examples for Windows 7? I don't have access to the WebAuthenticator library that's used in the Windows 8 samples.

alitaleg commented 10 years ago

The SDK itself is platform independent. We have a sample WPF app in the SDK that shows basic authentication and displays the contents of the root folder. We will continue to expand our samples but do not have definitive timelines right now.

brianytang commented 10 years ago

I am closing this issue for now.

On the latest update of the SDK on nuget, we have updated all our dependencies (including nito.asyncex) and additionally strong-named the assembly.

Please try updating to the latest assemblies, and if the issue persists, feel free to open a new issue.