Well, the plan was to get dasBlog running on Medium Trust and 2.0 and releasing quickly.
好吧,计划是要使dasBlog在Medium Trust和2.0上运行并快速发布。
![](https://i-blog.csdnimg.cn/blog_migrate/ca330103f1184e2c41e8e7b524afe930.png)
Of course, the best laid plans of mice and men, right?
当然,老鼠和男人最好的计划,对吧?
NOTE: Remember, you never need to wait for us, you can always get the code with Subversion (I like TortoiseSVN on Windows, and there's a 64-bit version) using this URL: https://dasblogce.svn.sourceforge.net/svnroot/dasblogce/trunk. This blog, my blog, will almost always be running the "HEAD," meaning, the latest stuff as I am right now. The many dasBlog contributors often run the head. Folks like John Forsythe either run custom modified versions or use Custom Macros to make their sites very unique. If you're a developer, don't be too afraid of living on the edge, er, the "HEAD" of the source tree. Just keep backups! Also, don't forget that we welcome patches. Here's a HOW-TO contribute a patch to an Open Source Project like dasBlog.
注意:请记住,您不需要等待我们,您始终可以使用以下URL使用Subversion获取代码(我喜欢Windows上的TortoiseSVN,并且有64位版本): https : //dasblogce.svn.sourceforge.net / svnroot / dasblogce / trunk 。 这个博客(我的博客)几乎总是运行“ HEAD”(意思是我现在的最新信息)。 许多dasBlog贡献者经常发挥领导作用。 像John Forsythe这样的人要么运行定制的修改版本,要么使用“定制宏”使他们的站点非常独特。 如果您是一名开发人员,请不要太害怕住在源代码树的“ HEAD”边缘。 只要保留备份! 另外,不要忘记我们欢迎补丁。 这是如何向dasBlog之类的开源项目贡献补丁的。
We've set the date for the dasBlog 2.0 Medium Trust Release for this coming Tuesday. Personally, I'm compiling it with Visual Studio 2008 with no problems, and I've recently got it dasBlog compiling and running on IIS7 on Vista 64 with very little trouble. It's Not Scary™.
我们已定下周二即将发布dasBlog 2.0中等信任版本的日期。 就我个人而言,我使用Visual Studio 2008进行编译时没有问题,最近,我使用dasBlog进行了编译并在Vista 64上的IIS7上运行,几乎没有什么麻烦。 这不是吓人™。
Tony Bunce has a fine write-up on the issues we ran into with dasBlog on Medium Trust. Here's some highlights:
对于我们与Medium Trust上的dasBlog遇到的问题, Tony Bunce进行了很好的撰写。 这里有一些亮点:
"The goal of medium trust is for hosting providers to provide functional ASP.NET 2.0 hosting while also protecting against rogue or malicious applications. Unfortunately that protection comes at the cost of application flexibility. ...There are a few features that are limited in a medium trust environment: SMTP on alternative ports and Mail to Weblog via POP3...dasBlog will let you know that you don't have these privileges by displaying warnings on the configuration page.
“中等信任的目标是使托管服务提供商能够提供功能性的ASP.NET 2.0托管,同时还可以防止流氓或恶意应用程序。不幸的是,保护功能是以牺牲应用程序灵活性为代价的。...一个中等信任的环境:备用端口上的SMTP和通过POP3 ...发送到Weblog的邮件通过dasBlog通过在配置页上显示警告,使您知道您没有这些特权。
There is some good news though, these limitations won't affect most users. Many hosting providers that run limited trust environments don't run in the default medium trust, but rather a "modified full trust". In that case you may already have all the permissions you need for all of the features to work."
虽然有一些好消息,但这些限制不会影响大多数用户。 运行有限信任环境的许多托管服务提供商不是以默认的中等信任运行的,而是“修改后的完全信任”的。 在这种情况下,您可能已经拥有了所有功能正常运行所需的所有权限。 ”
Go check out his post for more details. The most interesting issue we bumped into was that you aren't supposed to be able to call out via HTTP on the server side to any other connections unless they match your originURL in your web.config. In other words, my blog at www.hanselman.com can't call to any other site that isn't hanselman.com. However, you can set you originUrl to a regular expression like ".*" and then you can connect anywhere. Phil Haack noticed this and got the fix from Cathal Connollys.
去检查他的帖子了解更多详情。 我们碰到的最有趣的问题是,除非服务器上的HTTP.URL与您的web.config中的originURL匹配,否则您就不能通过服务器端的HTTP调用该服务器。 换句话说,我在www.hanselman.com上的博客无法调用不是hanselman.com的任何其他网站。 但是,可以将originUrl设置为“。*”之类的正则表达式,然后可以在任何地方连接。 菲尔·哈克(Phil Haack)注意到了这一点,并从卡塔尔·康诺利斯(Catha Connollys)得到了解决。
翻译自: https://www.hanselman.com/blog/coming-tuesday-dasblog-20-and-medium-trust