Visual Studio 2015 static libraries

Shortly after VS 2015 is released as a public stable version.

Any news when the libraries for VS 2015 will be available?

When TurboActivate 4.0 is released. It's being worked on. No hard date yet.

I just got my projects compiling with VS2015. There's just one little linker issue - static turboactivate libraries. Are there really so many differences between 2013 and 2015 that you can't just build the libs after fixing up the projects and some housecleaning? Took me like 2 hours to get my code converted and it's not trivial in any respect.

We already have TurboActivate 4.0 building with VS 2015. We just need to release TurboActivate 4.0. We're not going to back-port changes and fixes to TurboActivate 3.x when we're so close to releasing TA 4.0. It would be a waste of developer time.

If in the meantime if you want to release a version of your app, then you can always use the dynamic library (which will work with any compiler).

Ok, so if it's more like days than weeks then I can wait. The problem is when a programmer tells me "Real Soon Now" or an equivalent, I know all too well what it means from both sides. 🙂 I really do need the static libraries as I haven't written the code to check that the DLL is the real one. I don't spend a lot of time on this - that' s what we're paying for - but I like things to be a bit harder to crack than replace a file. If that's not the case then maybe you can point to the amount of effort it takes. I don't need exotic protection, but a "here load this file" is a much lower level of skill than hacking the EXE with a debugger.

It's about 3 to 4 weeks away.

Have there been any updates on this? Any chance of VS2015 static libraries against the current release?

TA 4.0 is coming out in January. We didn't finish before the holidays (Christmas in particular) which threw a wrench in things.

Wyatt wrote:> TA 4.0 is coming out in January.

Almost march now.

Yep, it was delayed. We're getting there. We want it out as badly as you do.

Wyatt, I don't mean to be offensive, but this matter is becoming a concern to me. I'm rapidly approaching the point where I either commit to TurboActivate as a licensing solution, or pay the extra cash and go with iLok2.

If I read this thread correctly, it seems to me that you said that Visual Studio 2015 static library support was coming last year; that schedule slid into January of this year; and now it seems to have slid into "we want it just as much as you do." Since my product was slated to come out this spring, I had previously taken you at your word on scheduling. So now I have a problem I didn't expect to have.

It seems further to me, based on the following answer you wrote, that the DLL version of TurboActivate can be trivially cracked by replacing the DLL: https://wyday.com/forum/t/2490/dummy-turboactivate-dll/ . In my opinion, that's a sufficiently trivial crack as to make TurboActivate pointless if DLL-based protection is used. I am fully aware that "any copy protection can be broken" but replacing a single file in any distribution by a stub, should not be enough to destroy a bit of copy protection. I am also aware that a DLL can be hashed and checked before loading, but I dare say that it is the responsibility of any reasonable copy protection to system to trivially verify its own signatures before running.

Like you, I'm running a small business as well, so I'm understanding of the difficulties that arise when scheduling and planning software. But I think the apparent fact that there is no believable ETA on when VS2015 static library support is coming out, plus the apparent fact that DLL-based protection is basically no protection at all, is a deal killer on LimeLM for me.

If I am missing any critical information here, I would much appreciate being educated.

Shoot me an email (wyatt@wyday.com) and I'll give you the pre-release version of 4.0. The delays were unrelated to VS2015 static libraries. They were just bundled into the release -- they've been done for many months (around when VS2015 came out).

We're planning to get TA 4.0, TF 4.0, TFS 4.0 all out at the same time. Maybe that was a strategic mistake because of the delays. At any rate we're about 8 or 9 business days away from the final release.

We're really excited about the release (all of the new features and bugfixes) and we've been working extra long days to get this out ASAP.

I apologize that I was short with you.

No apology necessary. However, as I mentioned the time limitation has become rather critical for me. I've sent you a direct email requesting beta access. Thank you most kindly.

Sure, I'll send it to you Monday.

Any update on this ?Thanks

TurboActivate 4.0 will include Visual Studio static libraries for VS2010, 2012, 2013, and 2015. TurboActivate 4.0 will be released soon.

Wyatt wrote:> TurboActivate 4.0 will include Visual Studio static libraries for VS2010,> 2012, 2013, and 2015. TurboActivate 4.0 will be released soon.

I'm in the same boat....I need this soon or I will have to move on to other services. I've been with you guys for a long time, but since Windows 10 and Visual Studio became free, all of my developers are not using 2015 exclusively.

Shoot me an email and I'll send you the pre release version on Monday.

We didn't expect 4.0 to take this long. However we're not releasing the final version until it's up to our standards.