ArchiCAD API and Visual Studio 2015

[Anonymous]

Hi,

I am new to development with ArchiCAD API. I don't have VS 2010 so I tried to recompile the examples in the API DevKit 20 with VS 2015 but it failed. I think it is because it uses the updated VC++ librairies.

I read on the ArchiCAD API twitter that the API DevKit 21 works with VS2015. Where can I download it ? I can't find it on beta.graphisoft.com

Thanks for your help.

[Anonymous]

Here is what I see

[Karl Ottenstein]

Ralph wrote:
The AC21 dev-kit is available on the beta website – perhaps you didn't spot the location (it's a bit subtle). In the Download area, click on the Download dev-kit link.

I don't have that link on my beta Download page ... did a page search for 'dev' to make sure I wasn't just missing it, and no matches. (I don't need access - but based on what you and Akos said, I should have had access since I'm both beta and dev.)

[Akos Somorjai]

mvallee wrote:
Here is what I see

Our fault, please try again.

Sorry, Akos

[Akos Somorjai]

Karl wrote:

Ralph wrote:
The AC21 dev-kit is available on the beta website – perhaps you didn't spot the location (it's a bit subtle). In the Download area, click on the Download dev-kit link.

I don't have that link on my beta Download page ... did a page search for 'dev' to make sure I wasn't just missing it, and no matches. (I don't need access - but based on what you and Akos said, I should have had access since I'm both beta and dev.)

Hi Karl,

These are two different systems, so we have to set the developer status on the beta page manually. You are all good now.

Best, Akos

[Anonymous]

Thanks to all of you, I managed to download the dev-kit, and everything compiles properly with VS2015.
Just have to learn now !

[Karl Ottenstein]

Thanks, Akos!

[stefan]

This does introduce a new complexity when supporting multiple AC-versions (Win/Mac, 19, 20 & 21). But I believe that moving to a newer Visual Studio is for most people an improvement 😉

We are currently preparing an AC21 add-in for a client. It's mostly working now, although quite some things shifted so our AC20 add-in suffered a bit.

[Akos Somorjai]

stefan wrote:
This does introduce a new complexity when supporting multiple AC-versions (Win/Mac, 19, 20 & 21). But I believe that moving to a newer Visual Studio is for most people an improvement 😉

We are currently preparing an AC21 add-in for a client. It's mostly working now, although quite some things shifted so our AC20 add-in suffered a bit.

Hi Stefan,

You can set VS2015 to use the VS2010 toolset (only if you have the VS2010 tools installed); that may take some of the pain away.

Best, Akos

[stefan]

My colleague (who does the development) had quite a struggle initially with Visual Studio setup. To have the 2010 tools (for AC20 and earlier) it was more fail-safe to install VS2010 before VS2015.

I'm the Mac guy and only support some of the development for my colleagues, so I try to avoid installing too much tools.