Connect to Network Folder on Application Start from Workgroup Configuration

I have a customer who has a wireless network set up in workgroup configuration such each laptop on the network does not automatically connect to folders outside that computer when the laptop is powered up.  She is using an appiclation (developed by me) that connects to a database located on a PC or server located other than the one that contains the application that needs to connect to the database, like so:

Laptop application >>>>>>>> PC (containing database)<<<<<<<<<<<<<Laptop (application)

The PC is not automatically accessible to the laptops on startup, so right now she either needs to use a tool in the application itself to reconnect to the PC or use Windows Explorer to find the folder and then open the application.  It would be preferred if somehow the application could just automatically open the relevant networked folder without requiring a user to "manually" connect to it.  How can I do that?

Incidentally, I know that the method System.Diagnostics.Process.Start("net", @"use \\folder\name password /user:user") will work, but it flashes the DOS screen on the page when executed, which might be alarming to users, so I was hoping there's another way.  

Thanks.  Please let me know if you need additional information.  

l2BravoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bob LearnedCommented:
Network driver mapping, using the Windows Script Host Object Model:
// Add a COM reference to Windows Script Host Object Model.
 
using IWshRuntimeLibrary;
using System;
using System.Runtime.InteropServices;
using System.IO;
 
public class NetworkDriveMapper : IDisposable
{
 
    // Create a new shell object.
    private WshNetwork _networkShell = new WshNetwork();
 
    public void MapDrive(string driveLetter, string networkPath, bool isPersistent, string userName, string password)
    {
        // Disconnect the drive first, forcing a permanent change.
        DisconnectDrive(driveLetter, true, true);
 
        // Map the drive to the path.
        object persistent = isPersistent;
        object user = userName;
        object pwd = password;
 
        _networkShell.MapNetworkDrive(driveLetter, networkPath, ref persistent, ref user, ref pwd);
    }
 
    public void DisconnectDrive(string driveLetter, bool willForce, bool isPersistent)
    {
 
        if (Directory.Exists(driveLetter))
        {
            object force = willForce;
            object updateProfile = isPersistent;
 
            _networkShell.RemoveNetworkDrive(driveLetter, ref force, ref updateProfile);
        }
 
    }
 
    void IDisposable.Dispose()
    {
        if ((_networkShell != null))
        {
            Marshal.ReleaseComObject(_networkShell);
            _networkShell = null;
        }
    }
}

Open in new window

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C#

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.