A few questions
First of all, I'd like to say that this is going to be a GREAT product! [But you know this, don't you?..]
A couple of days ago, I read all web pages and articles on softwarepotential.com, but there isn't much to read there yet...
I have a few questions/requests, if you don't mind me asking:
1. In order to make SLPS a one-stop solution for all kinds of software development shops, it would be really, REALLY nice if you could include some kind of credit card processing module (maybe, as an optinal module at an extra cost in addition to a "regular" SLPS edition).
By the way, could you elaborate a bit more on what kinds of editions (or, products!..) will be included in SLPS, please? The website is kinda vague on this point.
2. It is a common practice to provide a 30-days money-back guarantee. If a client purchases a licence managed by SLPS, and then decides to get money back, will s/he be able to continue using the software after that? If the answer is [hopefully!..] "No", will a solution to this problem be a part of SDK?
3. Will SLPS license management be available and be the same for software purchased directly from the manufacturer (ISV), Amazon.com, and Windows Marketplace?
4. Will there be an option to create/manage promotion codes?
5. And last but not least, are you planning to add SLPS to software bundle for the "Empower for ISVs" program?http://microsoft.mrmpslc.com/ISVCommunity/OverviewdetailEmpower.aspx
Combined with credit card processing module, this would attract startups and ISVs and established companies to you like butterflies are attracted to light.
[1859 byte] By [
fafnir] at [2008-3-7]
Oops, I forgot to ask one more question...
6. If a client purchases, for example, a Developer edition of this [whatever] custom software, and then decides to upgrade to Standard or Pro or Enterprise edition, how will SLPS handle this upgrade: as a new purchase (for example, adding a promotion certificate "behind the scenes" which value is equal to the price of the original/previous edition), or some other way?
Thank you.
It's been 10 days since I posted my questions.
Unlike other MSDN forums which have dozens, if not hundreds, or posts every day, and someone's questions can be quickly "buried" among many others (and, even get moved to the next page #2 within a couple of hours, etc.),
on this forum there are just a few posts so far.
That said, there has not been a reply for 10 days.
I checked securelm.net and softwarepotential.com just a minute ago, and there's nothing new there since about two weeks ago.
So, now my only qustion is: WHY?
If my questions are naive and dumb, please let me know. My e-mail address is: fafnir [at] optonline.net
If the answers to all questions (including, but not limited to, mine) are not available yet, please let us know you'll get back to us.
If the project is dead, or at least stalled... please let us know.
For me personally, there is no (I repeat: NO) other software which release I would be looking forward to nearly as much as SLPS.
Any response would be greatly appreciated.
So sorry fafnir,
Your questions are neither dumb or otherwise. We got mightily wrapped up in release. It's not a good excuse, only a reason.
Many of your questions and observations are spot on.
I'll start with your list.
1. In order to make SLPS a one-stop solution for all kinds of software development shops, it would be really, REALLY nice if you could include some kind of credit card processing module (maybe, as an optinal module at an extra cost in addition to a "regular" SLPS edition).
By the way, could you elaborate a bit more on what kinds of editions (or, products!..) will be included in SLPS, please? The website is kinda vague on this point.
No CC processing at this time. This is always a huge request.
We are still a little vague on this as well. However, the biggest difference will be the number of licenses you buy.
2. It is a common practice to provide a 30-days money-back guarantee. If a client purchases a licence managed by SLPS, and then decides to get money back, will s/he be able to continue using the software after that? If the answer is [hopefully!..] "No", will a solution to this problem be a part of SDK?
You have a few options with this-- However the answer is 'yes' -- you will be able to revoke after 'n' days. With SLPS it might be 'kinder' to attenuate features instead.
3. Will SLPS license management be available and be the same for software purchased directly from the manufacturer (ISV), Amazon.com, and Windows Marketplace?
I'm not sure what you mean by this one. Can you describle the scenario you're thinking of?
4. Will there be an option to create/manage promotion codes?
Promotion codes are more associated with the actual purchase. They are rarely used in the context of licensing.
5. And last but not least, are you planning to add SLPS to software bundle for the "Empower for ISVs" program? http://microsoft.mrmpslc.com/ISVCommunity/OverviewdetailEmpower.aspx
Combined with credit card processing module, this would attract startups and ISVs and established companies to you like butterflies are attracted to light.
We are most certainly looking into this.
Terrence Nevins
SLP Services - Program Manager
Microsoft Program Manager: Software Licensing and Protection Platform Thank you very much for your reply, Terrence.
From what you wrote, I got an impression that this product is going to be even better than I expected.
Perhaps, the request about credit card processing is one of the least important (and, most likely, the hardest to implement) because it has to be coupled to a shopping cart and a merchant account.
Different shopping carts, merchant accounts from different banks... This might get messy.
Besides, for example, PayPal provides both a CC module and a shopping cart, AND there is an option to not have a merchant account at all.
I am almost sure that most people (including me) are far more interested in MSIL code protection and license management:
1. .NET code protection (IP protection): I evaluated 2 very famous obfuscators against 2 (again, very well-known) disassemblers. The result is extremely discouraging: assemblies protected by one of those two obfuscators are protected against one of those disassemblers, but helpless against another disassembler; and vice versa. So, if Microsoft is adopting some really cool technology for REALLY protecting MSIL code, that's going to be a killer product, and I can't wait to get my hands on it.
2. License management: Suffice it to say, I'd rather use this kind of product from Microsoft than from any other company. TOC of MS products tends to be lower than that of MS rivals, and, from my experience, tech support responsiveness and quality is a big issue (MS's been on top of my list, - never had a problem with MS support).
My question about license management for software purchased directly from an ISV, Amazon, and Windows Marketplace, is not valid. I realized it does not matter where the software was purchased from , as long as it uses SLPS: the software can be downloaded from anywhere (or, even be installed from a CD/DVD); what matters is how it is activated, and the activation is in no way related to where the software came from.
About promotion codes: I see what you mean. Thank you.
Just two more questions, if you don't mind:
1. I read somewhere that SLPS' release is estimated to be in October 2007.
Is that true?
2. [After the initial release] if and when Service Pack 1 and/or hotfixes become available, will it be possible to update ONLY the server-side part of SLPS (residing on the ISV's server) without having to distribute any updates to the end users of the SLPS-protected software?
Thank you very much.
Hi again fafnir,
The answer to release is YES. October 2007 is the date and we look like we are on track.
The answer to the #2 question is:
It takes a crystal ball to know this. If there was something that absolutely had to be fixed in the client software that is on an end-user's system we would ship a hotfix/QFE. But it's not a simple matter of simply pushing a patch to an end-user's system. In some cases it would require you to push the patch. The reason for this is complex on the surface, but makes sense - we use our own technology (Code Protection) to protect the system from end to end. Including that which ends up installed on the end-user's system. Part of code protection is tamper detection -- we don't have a back-door on defeating our tamper protection. In fact our technology wouldn't even begin to permit us to open a backdoor! So in some cases (most) where we might need to patch something - we rely on you to pick up a new permutation and use it to re-generate your distributables.
So with this LONG answer - comes the following. We believe that we won't have to issue such a patch (ever?) or often. We've worked through key scenarios that might trigger such a patch and have mitigated this requirement. But as in all things security related - there's never 100% confidence.
For all issues outside of the 'core' technology - the answer is "YES" we will deliver service paks that target isolated components of the solution when indicated. For example: providing new perfcounters in the server product.
Thanks for the great questions,
Terrence Nevins
