需要上传文档到MOSS文档库的系统
您好，如果您是 MOSS 专家，我需要您的帮助。
我有一个系统需要将文档上传到 MOSS 文档库。
我认为第一阶段系统最简单的方法就是将网络路径映射到 MOSS 文档库。
整件事看起来太简单了。 之后它是使用 System.IO 的直接副本。
我想知道，这种方法是否足够可靠，可以在生产系统中使用？
猜测固然很好，但如果您有以这种方式与 MOSS 合作的实际经验，那么您的答案将意义重大。
谢谢。
Hi I need your help if you are an expert in MOSS.
I have a system that needs to upload documents into a MOSS document library.
I decided that the easiest approach for a phase 1 system would simply be to map a network path to a MOSS Document library.
The whole thing seems too easy. After that its a straight copy using System.IO.
What I would like to know, is this method reliable enough to be used in a production system?
Speculation would be great, but if you have real experience with working with MOSS in this way, your answer would mean a lot.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
只要您对副本进行正确的错误检查，就可以了 - 如果您牢记 SharePoint 文档库和文件命名约定的标准注意事项。
SharePoint 不允许在文件名中使用 NTFS 和 FAT 允许的某些字符 - 当您尝试将它们复制到 DL 时，无论您如何执行此操作，这些字符都会导致错误，因此您需要事先清理文件名。
使用 SharePoint webdav 界面的网络路径的唯一缺点是，如果您对它压力太大（大量文件的大型副本），您很容易就会压垮它，并导致网络共享对某个用户不可用。一段的时间。 如果您时不时地谈论几个文件，例如每小时几个，应该没问题。
So long as you do the proper error checking around the copy, its fine - if you bear in mind the standard caveats with SharePoint document libraries and file naming conventions.
SharePoint does not allow some characters in file names which NTFS and FAT do - these will cause an error when you try to copy them to the DL, regardless of how you do that, so you will need to sanitise your filenames beforehand.
The only downside to using a network path to the webdav interface of SharePoint is that if you stress it too much (a large copy of a lot of files), you can easily overwhelm it and it will cause the network share to become unavailable for a period of time. If you are talking about a few files every now and then, several an hour for example, it should be fine.
您最好从网络路径读取文件，然后使用对象模型 API 或 Web 服务上传它。
您可以使用计时器作业，这些作业可以安排在方便的时间运行。 计时器作业可以从 XML 文件读取其配置设置。
与使用 System.IO 的直接副本相比，该系统更容易维护和排除故障。
You are better off reading the files off the network path and then using the Object Model API or the web services to upload it.
You can use timer jobs which can be scheduled to run at a convenient time. The timer job can read it's configuration settings from an XML file.
This system would be easier to maintain, and troubleshoot, when compared to a straight copy using System.IO.