关于MOSS或WSS 3.0，哪些API的部分可能已经落实好？ [英] Regarding MOSS or WSS 3.0, What parts of the API might have been implemented better?

问题描述

如：

• 您可能喜欢密封的方法，延长


• 抛出的异常是比较模糊比是有帮助的


• 的关联内容消除这是一大特点 MCMS 2002


• HTML从存储领域并返回时剥离。没有简单的选项，以解决此问题


• 创建的SPWeb需要漫长。


• 从2002年MCMC不存在的迁移路径

• Sealed Methods you might have liked to extend
• Exceptions thrown are more vague than is helpful
• Elimination of Connected Content which was a major feature in MCMS 2002
• HTML is stripped from fields when stored and returned. No easy option to work around this problem
• Creating an SPWeb takes an eternity.
• Nonexistant migration path from MCMC 2002

推荐答案

我希望SharePoint对象模型纯粹是管理code。虽然有.NET包装方便，不必担心处理实现IDisposable的许多物体是一种痛苦。它是如此容易碰到内存问题时脱手不会被调用的WSS应用程序。我认为原因移动到.NET是免费的开发人员不必处理内存管理...

I wish that the Sharepoint object model was purely managed code. Although having .NET wrappers is convenient, having to worry about disposing the many objects that implement IDisposable is a pain. It's so easy to run into memory issues when dispose does not get called in a WSS app. And I thought the reason for moving to .NET was to free developers from having to deal with memory management...

这篇关于关于MOSS或WSS 3.0，哪些API的部分可能已经落实好？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！