Build Box 上的 Silverlight 和表达式组件
我有一个解决方案，需要在没有 VS 或 Expression Blend 等标准编辑工具的计算机上构建 Silverlight 项目。对于 Expressions，我确实需要 Blend SDK 的字体嵌入和媒体处理功能。对于 Silverlight，我需要针对这 3 个运行时进行构建 - SL3、SL4 和 Windows Phone SL3。我将使用 MSBuild，并且更喜欢在我的构建箱上使用 .NET 4.0 运行时。
任何人都可以向我推荐这种构建场景的最低限度的构建箱上的组件是什么？如果我不必安装它，我真的不能（必须向管理层证明为什么在构建箱上安装某些东西）。例如，我可以分解 Blend SDK 并只在构建盒上安装我需要的 dll（我的意思是，这在法律上可行吗？）。对于 SL 运行时，我是否需要这些运行时的开发人员版本，或者常规运行时可以吗？
提前致谢。
I have a solution that needs to build Silverlight projects on a computer that doesn't have standard editing tools like VS or Expression Blend. From Expressions, I do need the font embedding and media processing capabilities of the Blend SDK. For Silverlight, I need to build for these 3 runtimes - SL3, SL4 and Windows Phone SL3. I am going to be using MSBuild and prefer the .NET 4.0 runtime on my build box.
Can anyone recommend to me what the bare minimum for this kind of build scenario would be in terms of componenets on my build box? If I don't have to install it, I really can't (has to be justified to management why something is being installed on the build box). So, for example, can I break apart the Blend SDK and only install the dlls that I need on the build box (I mean, is this legally okay?). For the SL runtimes, do I need the developer version of those or is regular runtime okay?
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
将依赖项 DLL 添加到构建环境
我见过的常见模式是获取任何构建依赖项（例如 SL 运行时或 Blend DLL）并将它们签入您的软件仓库（在 \References*.dll 下） ）。如果 DLL 被标记为“可重新分发”，那么您在法律上就处于良好状态。
如果可能的话，我会尝试保留直接安装 MSI 附带的 SDK（例如 Silverlight SDK、Blend SDK），因为这样可以避免因您认为不需要的依赖项或版本不匹配而产生的错误。对于 Silverlight 和 Blend，有可下载的 SDK MSI：
Silverlight 4 SDK
< a href="http://www.microsoft.com/downloads/en/details.aspx?FamilyID=d197f51a-de07-4edf-9cba-1f1b4a22110d&displaylang=en" rel="nofollow">适用于 Silverlight 的 Blend 4 SDK< /a>
Add your dependency DLLs to your build environment
A common pattern I've seen is to take any build dependencies such as your SL runtimes or Blend DLLs and check them into your depot (under say \References*.dll). If the DLLs are marked as 'redistributable' you're in good shape legally.
If possible I try to keep SDKs (e.g. Silverlight SDK, Blend SDK) that come with MSIs installed directly as it tends to avoid errors from dependencies you didn't think you needed or version mismatches. In the case of Silverlight and Blend, there are downloadable SDK MSIs:
Silverlight 4 SDK
Blend 4 SDK for Silverlight