Dokan (1 Viewer)

[akayani]

https://groups.google.com/forum/#!topic/dokan/DsknCUTGiPI

Looks like an issue with the Win 10 installer. There are only a couple of files involved and no doubt a reg entry.

http://wiki.team-mediaportal.com/in...nt/Building_&_Compiling/2_Build_Prerequisites
Maybe so of the detail in here could be expanded for Visual Studio. Likely if you are used to working with dependencies in VS you would know to dig into the Windows directory to access directX.

Same goes for Dokan.

I don't see any errors in debug that mention Dokan. Only the one for the namespace of directX.[DOUBLEPOST=1439427385][/DOUBLEPOST]http://stackoverflow.com/questions/...-xml-namespaceyyy-reference-could-not-be-foun

That looks like the solution but it crashes VS. >of course<

 

[azzuro]

you can found the Dokan driver modified for MP2 here :
https://github.com/chefkoch/DokanCustomization

 

[akayani]

Maybe if I complied it? I'm on Win 10.

 

[azzuro]

Maybe look. The repo. And search about os limitation.

 

[azzuro]

But use only 0.53. 0.6 and 0.7 crash MP

 

[mrj]

Hi
About Dokan version. See wiki
http://wiki.team-mediaportal.com/2_MEDIAPORTAL_2/6_Support/FAQ/DokanNewerVersion

mrj

 

[MJGraf]

Hi akayani,
sorry, I don't quite understand what you are trying to do.
Dokan 0.53 should be installed automatically with the installer of MP2.
If you want to install it manually because you don't want to use the installer, please use this file: http://install.team-mediaportal.com/dokaninstall_053.exe
It is also Version 0.53 and we removed the OS Version check so that you should be able to use it on Windows 10. Start it from commandline with a " /S" switch (capital 'S' is important). Version check is only circumvented in "Silent" mode of the installer.
As per the link of mrj, do not use later Versions of Dokan. They will lead to BSODs.
If this is not what you want to do, please explain in a bit more Detail what you are about to do.
Thanks, Michael

 

[akayani]

As far as I can tell MP2 is working fine. I'm trying to sort out the dependencies in Visual Studio (VS) so I can compile the program. That's made difficult but a general lack of knowledge on VS & C#. I come from using Aptana (Eclipse) PHP and javaScript. It is going to take a few months to get a handle on this. I accept that as being the case. The basic structures I understand from Java. Obviously, from where I come from the question is, 'why the hell would anyone ever write an interface in this dog box of XAML. With oh I see binding'. It's about understanding limitations rather than coding. I don't have a coders brain. My training is in usability. So the goal is to understand the relationship between what I see as valid comments and what that means in coding effort. I think that is required to make meaningful comment that isn't sledging.

Bottom line is that I'm impressed by the work people have done but I'm not at all impressed by the client interface. To be fair I need to understand the why of that better but my critique of it is valid. I understand how this occurs in application development and I'm not immune to it in my own work. When things grow based on need interface design get caught in the process. You end up with ways to do stuff but at the expense of usability for newcomers. It's about being a hard marker but doing it from a position of understanding what your claimed needs mean in code time. Mindful critique.

 

[azzuro]

Sorry. My english is not famous.
But what is your goal exactly ?

 

[osre]

@akayani Normally VS gets all needed dependencies via nuget when you build it the 1st time.
All you should need to do is clone the MP2 repo from git, open the MP2 client or server solution (.sln files in source folder) and build.