really needs vs2013?

[elliotwoods]

the guys from MS at eyeo said it works with vs2012

[joshuajnoble]

I just haven't had a chance to test it. Can you confirm that it works with 2012?

[obviousjim]

been working w 2012 for me

On Mon, Jun 23, 2014 at 11:39 AM, joshua noble [email protected]
wrote:

I just haven't had a chance to test it. Can you confirm that it works with
2012?

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

• James

[joshuajnoble]

Is it Express and erm, Standard (i.e. paid)?

[elliotwoods]

I ended up rolling my own because didn't want to move to vs2013, then later heard that this works with vs2012

I'm pretty happy continuing with https://github.com/elliotwoods/ofxKinectForWindows2 for the time being as the COM counterpart to this KCB addon, but feel bad to split the party.

Elliot

[obviousjim]

What are the advantages of the COM implementation if any?

On Mon, Jun 23, 2014 at 4:20 PM, Elliot Woods [email protected]
wrote:

I ended up rolling my own because didn't want to move to vs2013, then
later heard that this works with vs2012

I'm pretty happy continuing with
https://github.com/elliotwoods/ofxKinectForWindows2 for the time being as
the COM counterpart to this KCB addon, but feel bad to split the party.

Elliot

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

• James

[joshuajnoble]

Awesome. A COM implementation is a good idea because it means that we're not waiting on MSOpenTech for speech/audio/face etc. I don't think splitting the party is in any way bad until MSOT gets everything in the KinectSDK implemented in KCB. Btw, I updated the README.

[abuseukk]

For me it doesn't work with VS2012. Everything is configured properly but it still couldn't open KCBv2.lib

[joshuajnoble]

I'll have to leave this to James since I don't have 2012 installed anywhere at present.

[micrem73]

I confirm it works with VS2012 express for desktop.