D
Donald
I posted this message on the microsoft.public.windowsxp.network_web
newsgroup, however I know think that was the wrong venue.
Perhaps someone else is trying to do the same thing as I. Currently, I have
a VMS site for storing user data files in a automated and structured
manner -- no direct access. The user runs my VB application, which grabs the
desired files, validates them and then stores them using FTP as the transfer
protocol. We are moving off the VMS system and onto a Window Server 2003
terabyte server. I could setup an FTP service to do the same process as I'm
doing on VMS, however it seems that a disk service might be a better
solution (ie more control than just GET and PUT). Yet, I don't want the
user to have direct access to the disk service. Again, I'd like to access
the service via a VB application which connects to the disk service
transparently. Any thoughts on this topic?
I hate to answer my own queries, however after further research it appears
that the Windows Management Interface (WMI) under the system.management
namespace might hold the key. Namely, the connectionoptions,
managementscope and managementobject classes facilitate the mapping of
remote drives. Here is a good article on the matter:
http://www.csharphelp.com/archives2/archive334.html
I have been using VB6 for sometime and have moved over to VB.NET and now
even C# express. Therefore, I may implement the solution in one of the two
latter languages. I'm also looking into Remoting, but not sure how it will
relate, if at all.
newsgroup, however I know think that was the wrong venue.
Perhaps someone else is trying to do the same thing as I. Currently, I have
a VMS site for storing user data files in a automated and structured
manner -- no direct access. The user runs my VB application, which grabs the
desired files, validates them and then stores them using FTP as the transfer
protocol. We are moving off the VMS system and onto a Window Server 2003
terabyte server. I could setup an FTP service to do the same process as I'm
doing on VMS, however it seems that a disk service might be a better
solution (ie more control than just GET and PUT). Yet, I don't want the
user to have direct access to the disk service. Again, I'd like to access
the service via a VB application which connects to the disk service
transparently. Any thoughts on this topic?
I hate to answer my own queries, however after further research it appears
that the Windows Management Interface (WMI) under the system.management
namespace might hold the key. Namely, the connectionoptions,
managementscope and managementobject classes facilitate the mapping of
remote drives. Here is a good article on the matter:
http://www.csharphelp.com/archives2/archive334.html
I have been using VB6 for sometime and have moved over to VB.NET and now
even C# express. Therefore, I may implement the solution in one of the two
latter languages. I'm also looking into Remoting, but not sure how it will
relate, if at all.