.Net 4 ClickOnce 是否使完全信任的 XBAP 变得可行？
这是我的情况。
我刚刚开始一份新工作，最近继承了一个需要重写的应用程序。我知道你在想什么，但相信我，...这确实是极少数情况之一，我所拥有的系统无法重构，几乎所有东西都必须消失。
当前的应用程序是一个 Silverlight 2.0 应用程序，包含大量 WCF、WCF 数据服务、ASP.Net、实体框架和许多其他内容。在每个关键时刻，最初的“外包”开发似乎都将该项目用作学习练习，但根本没有学到任何东西。这几乎是我见过的最糟糕的情况。问题是这个项目本来应该在去年 9 月完成，所以现在晚了 12 个月。
我的任务是重写解决方案并在 3-4 个月内完成功能。我绝对可以做到这一点（实际上只不过是数据上的一点或形式），但我正在考虑现在最好的选择是什么，以节省时间。我正在考虑 XBAP，但上次我看到它的部署是一场噩梦！
因此，...我们可以针对 .Net 4，因此 ClickOnce 部署了完全信任 XBAP。这意味着我可以暂时放弃该中间层，选择简单的 DAL 程序集并忽略 Web 服务、HTTPHandler（用于上传）等的复杂性。这将是一个 Intranet 部署，因此我可以保证 WAN 上有 IE7+ 和 Windows 机器。
但这一切听起来好得令人难以置信。完全信任 XBAP 或 XBAP 开发本身还存在哪些问题？值得追求这个还是我现在应该寻找其他地方？
任何帮助将不胜感激。 提前致谢。
Here's my situation.
I've just started a new job and I've inherited an application recently which is going to need a rewrite. I know what you're thinking but trust me,...this really IS one of those rare cases where the system I've got is beyond refactoring and almost everything has to go.
The current app is a Silverlight 2.0 app with a whole host of WCF, WCF Data Services, ASP.Net, Entity Framework and a bunch of other stuff. At every juncture the original 'outsourced' development seem to have used this project as a learning exercise and have flat out failed to learn anything. It's just about the worst I've ever seen. Problem is this project should have been complete last September so it's 12 months late now.
What I've been tasked with is to rewrite the solution and have it functionally complete in 3-4 months. I can definitely do that (it's actually little more than a bit or forms over data) but I'm looking at what my best options might be now to save time. I'm considering XBAP but last time I looked at it deployment was a nightmare!
So,...we can target .Net 4 and thusly, ClickOnce deployed Full Trust XBAPs. This means I could drop that middle tier, opt for a simple DAL assembly and ignore the complications of Web services, HTTPHandlers (for uploads) and such for now. This will be an Intranet deployment so I can guarantee IE7+ and Windows boxes on the WAN.
This all sounds too good to be true though. What are the remaining issues with Full trust XBAPs or XBAP development itself. Is it worth pursuing this or should I look elsewhere for now?
Any help would be greatly appreciated.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
到目前为止，我在 .Net 4.0 中选择了对 XBAP 应用程序的部分信任 - 即使在 Intranet 上，我们在使签名/证书工作实现完全信任方面也遇到了严重的问题。我们可能比其他人的孩子更笨，但我们决定采用 WCF 服务和部分信任 XBAP，因为它更无摩擦。
不过，Click-Once 一直工作得很好（除了一些 IE 的小问题，其中缓存有点太过分了）。
我们现在最大的问题是打印:-)。固定布局很痛苦。
希望这会有所帮助。
So far, I've opted for partial trust for our XBAP application in .Net 4.0 - We've had severe problems getting the signing/certificate thing working for full-trust even on the intranet. We might be dumber than other people's kids, but we decided to go the way of a WCF-service and a partial trust XBAP as it was just more friction-less.
Click-Once has been working perfectly, tho (except from a few IE hick-ups where caching went a wee bit too far).
Our largest problem is printing now :-). Fixed layout is a pain.
Hope this helps a bit.