Pro: It enables you to mock up a concept and see if it seems like the development path will be easy before you shell out large amounts of money for the real deal.
Cons: It could trap you in a vicious cycle of wiping your virtual machine and re-installing the OS, the trial version, and your product (you do use source control, correct?) if they are hoping that this will alleviate the need for ever paying for the real product.
Suggestion: If you don't mind unsolicited advice, then I would determine why the lead admin wants to use the trial versions -- and then go from there. Until you know the reasons you cannot respond to them.
If they are doing it for the pro reason, then determine if you feel comfortable working with the possibility of switching technologies 30 days into your build. (Can you do it efficiently?)
If they are doing it to avoid spending money, present some of the alternate open source / free options that you are comfortable developing with. If they will not change their modus operandi at that point, then do what is necessary, knowing what you will be walking away from / getting in to.
(And if you don't mind one more bit of unsolicited advice -- if they are doing it for the con reason and will not change WALK AWAY)
Point them at BizSpark. Microsoft is begging people to use their stuff. A hunny will get you everything on the map for 3 years or until you start making money.
Oh, to answer your question: If I need to get funding for technology not present in the infrastructure or to do a proof of concept I would not think twice about using evals. That is what they are for. I would be evaluating the suitability of the product for use with my designs. Seems easy to me. Maybe I am just, hold on, i have to give my parrot a cracker... ;-)
Apart from the ethical arguments, there are practical ones:
What are you supposed to do if development overruns? Start reinstalling everything, wasting several days doing so?
Additionally, if the client is so strapped for cash that they want to do this, how can you be certain they will pay you (either due to cash flow problems, or simply because of their shady ethics)?
我绝不会在这样的条件下工作。如果您正在开发具体产品，请获取开发工具的适当许可证。我知道 SQL Server 的开发人员版本并不是非常昂贵（与许可用于生产使用的版本相比），因此我认为对于 Sharepoint 来说也是如此。
当然，正如已经提到的，试用期到期后你该怎么办？
I'm pretty sure that that kind of use is a violation of license terms. Trial editions of servers are for evaluating a product. And if you are in fact creating a product, then you have gone way beyond evaluation.
I would never work under such terms. If you are developing a concrete product, get proper licenses for the development tools. I know that the developer edition of SQL server is not hugely expensive (compared to a version licensed for production use), so I would imagine that the same counts for Sharepoint.
And then there is of course, as already mentioned, what do you do when the trail period expires?
I wouldn't mind doing this so long as the job is shorter than 30 days. Make sure your work contract they're paying for the time worked and not specific deliverables, because your deliverables are time-bombed.
Also be prepared to walk away. If this company doesn't have resources to get the right software, you don't want to be there longer than 30 days anyhow.
Microsoft provides several pre-built virtual machines, that contains full stacks.
(Server 2008/Sql 2008/Sharepoin) (Server 2003/Sql/Project Server) etc.
They are time bombed, but often (not always) Microsoft will provide a new image after the time out.
If the project has a quick timeline, it provides the developers access to the configured stack right away, with no ramp up time of building new virtual machines.
Esp when working on beta/early release software this is great.
The SQL Server evaluation's download page mentions that the evaluation license is good for 180 days, and specifically advertises it as a tool you can use for mission-critical applications. This tells me MS is fine with your using it for development work.
To answer a question with more questions:
How long does this project run?
What phase of the effort are you in now?
Is this an internal/proof-of-concept project, or something that your customer(s) will be using for a long time?
If you are going to need to use SQL Server for Operations & Maintenance support months past the initial evaluation period, you ought to get a license for the full version of it. And also consider what your customers are using so that you can reproduce any bugs that come back from them.
I don't think it's ethical to continually renew evaluation licenses to have a longer evaluation period. Companies call them "evaluations" as a try-before-you-buy, not a keep-trying-without-buying.
I'm not sure what others are seeing as unethical here. If the project is short enough to be completed within the 30 day trial, I don't see any issues. I think that's a great use of trials - if they can't handle a clients applications then they aren't a good option and you can use something else.
I think others here have given some good advice regarding the longer than 30 days projects and some good contract ideas.
服务器必须有多内部化？托管解决方案适合他们吗？ （Dreamhost、Amazon Web Services，等等）？一些托管系统提供相当复杂的机器映像（预装了很多东西——肯定是 AWS，大概是大多数其他系统），从而减少了设置时间/工作量。我认为那些带有许可证，尽管我真的不知道。另外，至少在某些情况下，您（他们）只需为您（他们）使用的内容付费。
如果物理机器需要在内部，或者事情非常敏感，那么显然没有什么好处。
How in-house do the servers have to be? Would a hosted solution work for them? (Dreamhost, Amazon Web Services, whatever)? Some hosting systems provide pretty complex machine images (lots of stuff pre-installed--definitely AWS, presumably most others), decreasing setup time/effort. I think those come with licenses, though I don't honestly know. Plus, in at least some cases, you (they) only pay for what you (they) use.
Obviously no good if the physical machine needs to be in-house, or if things are otherwise super-sensitive.
发布评论
评论（9）
优点：它使您能够模拟一个概念，并在您为真正的交易投入大量资金之前看看开发路径是否会很容易。
缺点：如果他们希望的话，它可能会让您陷入擦除虚拟机并重新安装操作系统、试用版和产品的恶性循环（您确实使用源代码管理，对吗？）这将减轻为真正的产品付费的需要。
建议：如果您不介意主动提出的建议，那么我会确定首席管理员为什么想要使用试用版 - 然后从那里开始。在您知道原因之前，您无法回应他们。
如果他们这样做是出于专业原因，那么请确定您是否愿意在构建 30 天后切换技术。 （你能高效地做到这一点吗？）
如果他们这样做是为了避免花钱，请提供一些你愿意开发的替代开源/免费选项。如果他们当时不改变他们的作案方式，那么做必要的事情，知道你将远离/进入什么。
（如果你不介意多一点主动提出的建议——如果他们这样做是出于欺骗的原因并且不会改变走开）
Pro: It enables you to mock up a concept and see if it seems like the development path will be easy before you shell out large amounts of money for the real deal.
Cons: It could trap you in a vicious cycle of wiping your virtual machine and re-installing the OS, the trial version, and your product (you do use source control, correct?) if they are hoping that this will alleviate the need for ever paying for the real product.
Suggestion: If you don't mind unsolicited advice, then I would determine why the lead admin wants to use the trial versions -- and then go from there. Until you know the reasons you cannot respond to them.
If they are doing it for the pro reason, then determine if you feel comfortable working with the possibility of switching technologies 30 days into your build. (Can you do it efficiently?)
If they are doing it to avoid spending money, present some of the alternate open source / free options that you are comfortable developing with. If they will not change their modus operandi at that point, then do what is necessary, knowing what you will be walking away from / getting in to.
(And if you don't mind one more bit of unsolicited advice -- if they are doing it for the con reason and will not change WALK AWAY)
将其指向 BizSpark。微软正在恳求人们使用他们的东西。猎人会在 3 年内为你提供地图上的一切，或者直到你开始赚钱。
哦，回答你的问题：如果我需要为基础设施中不存在的技术获得资金或进行概念验证，我会毫不犹豫地使用评估。这就是他们的目的。我将评估该产品是否适合我的设计。对我来说似乎很容易。也许我只是，等等，我必须给我的鹦鹉一块饼干......;-)
Point them at BizSpark. Microsoft is begging people to use their stuff. A hunny will get you everything on the map for 3 years or until you start making money.
Oh, to answer your question: If I need to get funding for technology not present in the infrastructure or to do a proof of concept I would not think twice about using evals. That is what they are for. I would be evaluating the suitability of the product for use with my designs. Seems easy to me. Maybe I am just, hold on, i have to give my parrot a cracker... ;-)
除了道德争论之外，还有一些实际的争论：
如果发展超支，你该怎么办？开始重新安装所有东西，浪费几天时间？
此外，如果客户现金短缺而想要这样做，您如何确定他们会向您付款（要么是由于现金流问题，要么仅仅是因为他们的不良道德）？
Apart from the ethical arguments, there are practical ones:
What are you supposed to do if development overruns? Start reinstalling everything, wasting several days doing so?
Additionally, if the client is so strapped for cash that they want to do this, how can you be certain they will pay you (either due to cash flow problems, or simply because of their shady ethics)?
我非常确定这种使用违反了许可条款。服务器的试用版用于评估产品。如果你实际上是在创造一个产品，那么你就已经远远超出了评估的范围。
我绝不会在这样的条件下工作。如果您正在开发具体产品，请获取开发工具的适当许可证。我知道 SQL Server 的开发人员版本并不是非常昂贵（与许可用于生产使用的版本相比），因此我认为对于 Sharepoint 来说也是如此。
当然，正如已经提到的，试用期到期后你该怎么办？
I'm pretty sure that that kind of use is a violation of license terms. Trial editions of servers are for evaluating a product. And if you are in fact creating a product, then you have gone way beyond evaluation.
I would never work under such terms. If you are developing a concrete product, get proper licenses for the development tools. I know that the developer edition of SQL server is not hugely expensive (compared to a version licensed for production use), so I would imagine that the same counts for Sharepoint.
And then there is of course, as already mentioned, what do you do when the trail period expires?
只要工作时间短于 30 天，我就不介意这样做。确保你的工作合同是按工作时间而不是特定的交付成果支付费用，因为你的交付成果是定时炸弹。
还要做好走开的准备。如果这家公司没有资源来获取合适的软件，那么您无论如何都不想在那里停留超过 30 天。
I wouldn't mind doing this so long as the job is shorter than 30 days. Make sure your work contract they're paying for the time worked and not specific deliverables, because your deliverables are time-bombed.
Also be prepared to walk away. If this company doesn't have resources to get the right software, you don't want to be there longer than 30 days anyhow.
Microsoft 提供了多个预构建的虚拟机，其中包含完整的堆栈。
（服务器 2008/Sql 2008/Sharepoin）（服务器 2003/Sql/Project Server）等。
它们是定时炸弹，但通常（并非总是）微软会在超时后提供新的映像。
使用这些映像的好处是它们已经配置好并且可以使用。
作为示例，这里是 sharepoint 2010 的测试版 (http://www.microsoft.com/downloads/details.aspx?FamilyID=0c51819b-3d40-435c-a103-a5481fe0a0d2&displaylang=en）。
如果项目有一个快速的时间表，它可以让开发人员立即访问已配置的堆栈，而无需构建新虚拟机的启动时间。
特别是在开发测试版/早期版本软件时，这非常棒。
Microsoft provides several pre-built virtual machines, that contains full stacks.
(Server 2008/Sql 2008/Sharepoin) (Server 2003/Sql/Project Server) etc.
They are time bombed, but often (not always) Microsoft will provide a new image after the time out.
The benefit of using these images is that they are already configured and good to go.
As an example here is a beta of sharepoint 2010 (http://www.microsoft.com/downloads/details.aspx?FamilyID=0c51819b-3d40-435c-a103-a5481fe0a0d2&displaylang=en).
If the project has a quick timeline, it provides the developers access to the configured stack right away, with no ramp up time of building new virtual machines.
Esp when working on beta/early release software this is great.
SQL Server 评估的下载页面提到评估许可证的有效期为 180 天，并专门将其宣传为可用于关键任务应用程序的工具。这告诉我 MS 同意您使用它进行开发工作。
要回答更多问题：
这个项目运行多长时间？
您现在处于哪个阶段？
这是一个内部/概念验证项目，还是您的客户将长期使用的项目？
如果您需要使用 SQL Server 进行操作和管理，初始评估期过后几个月的维护支持，您应该获得完整版本的许可证。还要考虑您的客户正在使用什么，以便您可以重现他们返回的任何错误。
我认为不断更新评估许可证以获得更长的评估期是不道德的。公司将其称为“评估”，是“先试后买”，而不是“不断尝试而不购买”。
The SQL Server evaluation's download page mentions that the evaluation license is good for 180 days, and specifically advertises it as a tool you can use for mission-critical applications. This tells me MS is fine with your using it for development work.
To answer a question with more questions:
How long does this project run?
What phase of the effort are you in now?
Is this an internal/proof-of-concept project, or something that your customer(s) will be using for a long time?
If you are going to need to use SQL Server for Operations & Maintenance support months past the initial evaluation period, you ought to get a license for the full version of it. And also consider what your customers are using so that you can reproduce any bugs that come back from them.
I don't think it's ethical to continually renew evaluation licenses to have a longer evaluation period. Companies call them "evaluations" as a try-before-you-buy, not a keep-trying-without-buying.
我不确定其他人在这里认为什么是不道德的。如果项目足够短，可以在 30 天的试用期内完成，我认为没有任何问题。我认为这是试验的一个很好的用途 - 如果它们无法处理客户端应用程序，那么它们不是一个好的选择，您可以使用其他东西。
我认为这里的其他人对于超过 30 天的项目给出了一些很好的建议以及一些好的合同想法。
I'm not sure what others are seeing as unethical here. If the project is short enough to be completed within the 30 day trial, I don't see any issues. I think that's a great use of trials - if they can't handle a clients applications then they aren't a good option and you can use something else.
I think others here have given some good advice regarding the longer than 30 days projects and some good contract ideas.
服务器必须有多内部化？托管解决方案适合他们吗？ （Dreamhost、Amazon Web Services，等等）？一些托管系统提供相当复杂的机器映像（预装了很多东西——肯定是 AWS，大概是大多数其他系统），从而减少了设置时间/工作量。我认为那些带有许可证，尽管我真的不知道。另外，至少在某些情况下，您（他们）只需为您（他们）使用的内容付费。
如果物理机器需要在内部，或者事情非常敏感，那么显然没有什么好处。
How in-house do the servers have to be? Would a hosted solution work for them? (Dreamhost, Amazon Web Services, whatever)? Some hosting systems provide pretty complex machine images (lots of stuff pre-installed--definitely AWS, presumably most others), decreasing setup time/effort. I think those come with licenses, though I don't honestly know. Plus, in at least some cases, you (they) only pay for what you (they) use.
Obviously no good if the physical machine needs to be in-house, or if things are otherwise super-sensitive.