如何使用kinect v2设备为wpf项目创建设置？ [英] How to create setup for wpf project with kinect v2 device?
问题描述
我有两个关于部署和创建kinect v2项目设置的问题。
第一个：
我只是使用Kinect v2 SDK（和设备）构建我的wpf项目。
how为我的应用程序创建一个用户不需要安装kinect SDK的设置。我希望我的程序可以安装在任何可以连接kinect v2（具有正确规格的电脑）的电脑上，但我不希望用户将
必须自己安装SDK。 / p>
有没有人知道如何创建这种安装？可能以某种方式使用kinect v2 sdk的dll和库。
第二个问题： 开发和Metro-app会更容易吗？我正在寻找开发kinect v2应用程序并为其创建设置的最佳方法，而无需用户安装
SDK。
另外我想知道哪个更好，为我的kinect程序创建 wpf程序或Metro-app ？优缺点？
谢谢！
1）要为.Net WPF应用程序创建安装程序，您需要分发此处的Kinect运行时：C：\Program Files \ MicroSoft SDKs\Kinect\v2.0_1409 \ Reded。你可以简单地将它添加到你的安装程序例程中检测是否存在驱动程序文件夹并且
执行它，或者只是让一个步骤让用户执行它。
2）正在更容易取决于您对WinRT api，策略和体系结构的了解。它绝对更容易分发，因为它将在Windows 8/10商店中，允许您打包Kinect运行时并自动安装。
开发Window Store应用程序是一个很远的与.Net应用程序不同，存在不同的安全范例，运行时范例，内存范例，文件访问范例以及Api用于WinRT的总体使用。我不会说它本身更容易，
但只是不同的心态。
我实际上认为.Net开发期是最简单的。与Native Win32或C ++ WinRT相比，这是.Net与WinRT或.Net标准。但是我认为Native和C ++ WinRT在我看来更加熟练和强大。
要分发 - 显然Windows Store应用程序是最简单的，但要在商店中获取应用程序可以是有点棘手，取决于第三方库和其他东西的复杂性。如果您的应用程序是纯WinRT和Kinect - 您将不会有任何问题。否则
.Net发布需要运行时和.Net代码。如果您不介意为此构建安装程序，那么您就可以了。
I have two question regarding deploy and create setups to kinect v2 project.
The first one:
I just build my wpf project using the Kinect v2 SDK (and device).
how do create a setup for my application that users doesn't need to install the kinect SDK. I want that my program could be able to install in any pc that can connect the kinect v2 (pc that have the right specification), but I don't want that the user will have to install the SDK itself.
Is there anyone who know how to create this kind of installation? probably using somehow the dll's and libraries of the kinect v2 sdk.
Second question: It will be easier to develop and Metro-app instead? I'm looking for the best way to develop a kinect v2 app and creating setup for it, without the user having to install the SDK.
Also I'm wondering which is better, create an wpf program or Metro-app for my kinect program? pros and cons?
Thanks!
1)To create an Installer for a .Net WPF application you need to distribute the Kinect runtime found here: C:\Program Files\Microsoft SDKs\Kinect\v2.0_1409\Redist. You can simply add this to your installer routine detect to see if driver folder exists and execute it, or simply have a step that has the user execute it.
2)Being easier is dependent upon your knowledge of WinRT api's, policies, and architecture. It is definitely easier to distribute since it will be inside the Windows 8/10 Store which allows you to package the Kinect Runtime and have it installed automatically.
Developing for Window Store apps is a far cry different than just .Net applications, there is a different security paradigm, runtime paradigm, memory paradigm, file access paradigm, and overall usage of Api's for WinRT. I wouldn't say it's easier per se, but just different mind set.
I actually think .Net development period is the easiest. That's .Net with WinRT or .Net standard, compared to Native win32 or C++ WinRT. However I think Native and C++ WinRT are way more proficient and powerful in my opinion.
To distribute - obviously Windows Store apps are the easiest, but to get you app in the store can be a bit tricky depending on the complexity of 3rd party libraries and other things. If you app is pure WinRT and Kinect - you won't have an issue. Otherwise .Net distribution requires the Runtime, and your .Net code. If you don't mind building the installer for that then you're good.
这篇关于如何使用kinect v2设备为wpf项目创建设置？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
