GithubHelp home page GithubHelp logo

UWP Compatibility about cue.net HOT 12 CLOSED

darthaffe avatar darthaffe commented on June 12, 2024
UWP Compatibility

from cue.net.

Comments (12)

DarthAffe avatar DarthAffe commented on June 12, 2024 1

Well to be honest I can't see any reason how this could be the fault of the the library. The debug directory is chosen by VS and if it tells wrong paths to nuget there's not too much I can do about that.

Right now I only see two solutions to this problem:

  1. If the app isn't working at all (so if it's not a debugger problem) I'm afraid you'd need to copy the dlls into the correct directory by hand or customize the build-target provided by CUE.NET to do so in your special case.

  2. I'm not 100% sure how the complete directory-structure of your build-result is but if it works if you use the app directly (so if it's a debugger problem) you could just add your special case to the native-paths:

// Execute this two lines before you call CueSDK.Initialize() for the first time.
CueSDK.PossibleX86NativePaths.Add(@"..\x86\CUESDK_2015.dll");
CueSDK.PossibleX64NativePaths.Add(@"..\x64\CUESDK_2015.dll");

from cue.net.

DarthAffe avatar DarthAffe commented on June 12, 2024

Could you give me the exception message provided by the WrapperException?
Since you seem not to run an console-application the Console.WriteLine in the exception-block won't work, but you could just set a breakpoint in there and copy the message out of the debug-window.

from cue.net.

boswelja avatar boswelja commented on June 12, 2024

Oh right, can do later on
EDIT: @DarthAffe I can see console output in Visual Studio's output tab

from cue.net.

boswelja avatar boswelja commented on June 12, 2024
Exception thrown: 'CUE.NET.Exceptions.WrapperException' in CUE.NET.dll ("Can't find the CUE-SDK at one of the expected locations:
 'S:\Visual Studio\Projects\test\test\bin\x86\Debug\AppX\x86\CUESDK_2015.dll
S:\Visual Studio\Projects\test\test\bin\x86\Debug\AppX\x86\CUESDK.dll'")	CUE.NET.Exceptions.WrapperException

It doesn't appear to be copying the dll to the correct location

from cue.net.

DarthAffe avatar DarthAffe commented on June 12, 2024

Are you using the nuget-package? If not the dlls aren't copied on their own. If yes that's somehow weird since there shouldn't be a difference between building a uwp and a normal .net app.

from cue.net.

boswelja avatar boswelja commented on June 12, 2024

Yes, I'm using the nuget package. The DLLs are copied to <project dir>\bin\x86\Debug\x86 but it seems the library is looking in the wrong directory?

from cue.net.

DarthAffe avatar DarthAffe commented on June 12, 2024

That's interesting. The default behavior is to just look for an "x86/" or "x64/" subfolder. I'm not sure why the application thinks that it's running in an AppX subfolder. Is there maybe some debug-path-configuration for uwp projects?

from cue.net.

boswelja avatar boswelja commented on June 12, 2024

I don't think there is, other libraries seem to work fine
Sorry for the late response, I apparently didn't hit send on this when I first wrote it

from cue.net.

boswelja avatar boswelja commented on June 12, 2024

Ok, I'll try this later.

from cue.net.

boswelja avatar boswelja commented on June 12, 2024

Sorry for the late reply again, just got some free time.
Even with your code above, it still seems to be checking in a nonexistent AppX folder

Exception thrown: 'CUE.NET.Exceptions.WrapperException' in CUE.NET.dll ("Can't find the CUE-SDK at one of the expected locations:
 'S:\Visual Studio\Projects\test\test\bin\x86\Debug\AppX\x86\CUESDK_2015.dll
S:\Visual Studio\Projects\test\test\bin\x86\Debug\AppX\x86\CUESDK.dll
S:\Visual Studio\Projects\test\test\bin\x86\Debug\AppX\x86\CUESDK_2015.dll'")

I used both your code above and the following:

CueSDK.PossibleX86NativePaths.Add(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "x86\\CUESDK_2015.dll"));
CueSDK.PossibleX64NativePaths.Add(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "x64\\CUESDK_2015.dll"));

from cue.net.

DarthAffe avatar DarthAffe commented on June 12, 2024

That's super weird ...
Are you 100% sure that the code I wrote above is correctly executed? I just tested it again and it works fine for me (even though I can't test with UWP). Also in the error message only 3 paths are shown. The first two are the defaults, the second one seems to be the one you added with the basedirectory.

Aside of that I don't see any other option than debugging into the LoadCUESDK to see what he is trying to do with that paths.

from cue.net.

boswelja avatar boswelja commented on June 12, 2024

How would I know if the code is being executed correctly? It's put right before CueSDK.Initialize(), so I assume it's working.
I'll do more debugging on what the different path variables return, and see if any of them actually point to AppX

from cue.net.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.