通过 .NET 从 SQL Server 下载可执行文件是否可能甚至合乎逻辑？
我正处于开发解密数千台笔记本电脑硬盘驱动器的解决方案的初始阶段。
我认为创建一个父应用程序来处理所有数据库调用、客户端更新、客户端命令和状态更新会很有用。该应用程序可以作为服务运行，也可以作为计算机启动时的 .EXE 运行。
然后让子应用程序通过记录到 XML 文件来执行所有解密和验证职责。
我认为如果需要新功能，可能需要更新这个孩子。这就是我试图思考更新它的最合乎逻辑的方法的地方，我的第一个想法是将其作为 BLOB 存储在 SQL 中，然后在需要时将其从父应用程序中拉下来。
这听起来合理吗？需要注意的一点是我的目标计算机都是.NET 2.0。
I am in the beginning stages of developing a solution to decrypt the hard drives of a few thousand laptops.
I have a thought that it would be useful to create a parent application that would handle all of the database calls, client updates, client commands and status updates. This application would either run as a service or as a .EXE from the computers start up.
Then have a child application perform all of the decryption and verification duties with logging to a XML file.
It is the child that I am thinking may need to be updated in the event new functionality is needed. That is where I am trying to think of the most logical way of updating it, my first thought went to storing it in SQL as a BLOB, and then pulling it down from the parent application if needed.
Does this sound reasonable? One item to note is that my target computers are all at .NET 2.0.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Ms. SQL Server 2008 引入了 FILESTREAM 存储，它使您既可以享受 DBMS 的好处，又可以享受文件系统的速度。值得一看。
http://msdn.microsoft.com/en-us/library/bb933993。 ASPX
Ms. SQL Server 2008 introduces FILESTREAM storage which gives you both the benefit from DBMS and speed of Filesystem. Worth having a look at it.
http://msdn.microsoft.com/en-us/library/bb933993.aspx
可能的？大概。受到推崇的？可能不会。
是否有任何原因导致您无法将可执行文件存储在文件共享上，并且在数据库中有一个条目指向客户端收集文件本身的 UNC 路径。
文件共享最适合提供文件，因此请这样使用。
Possible? Probably. Recommended? Probably not.
Is there any reason why you can't store the executable on a file share and have an entry in the database which points to a UNC path for the client to collect the file itself.
The file share is best for serving files so use it as such.