Deployment question

[Woody Splawn]

I have a non-web VB.net applicaiton that I have written. I have written it
on a client machine of a local area network. The solution is on the local
hard drive of this client machine with the back-end database (SQL Server) on
the file server of the network. How do I now make this applicaiton
available to other machines on the local area network? There are about 10
other machines all running XP with the dotnet framework installed.

[ltt]

Hi

I do not know if this is the best way to do this, but with you made a MSI installer there are some ways that everytime you update your software on a main machine is automatically installs in all the others computers. Please note that with this you will have to adapt you code to acess the SQL Database in just one machine, ifg not, each machine will have one Database

I do know if it works also, but try to share your application, it is completely wrong, maybe it could give errors when the users are acessin the database at the same time, it could cause a system slow down problem, however, I do know not if it could work, the first way is more appropriated

I hope that helps

ltt

[Cor Ligthert]

Hi Woody,

In addition to ITT, the method to create an install directory on a server,
is for me a very good way to go, keep in mind that you do not delete that
directory or the msi.

It is is needed again when you deinstall.

Just a little thing.

Cor

[Woody Splawn]

I'm sorry but I find it difficult to understand the response because of
language issues.

What I would like to avoid is running an .MSI from each machine.

Thanks for the try.

Woody
"ltt" <an*******@discussions.microsoft.com> wrote in message
news:9A**********************************@microsof t.com...

Hi,

I do not know if this is the best way to do this, but with you made a MSI installer there are some ways that everytime you update your software on a
main machine is automatically installs in all the others computers. Please
note that with this you will have to adapt you code to acess the SQL
Database in just one machine, ifg not, each machine will have one Database.
I do know if it works also, but try to share your application, it is completely wrong, maybe it could give errors when the users are acessin the
database at the same time, it could cause a system slow down problem,
however, I do know not if it could work, the first way is more appropriated.

I hope that helps.

ltt

[Brad Allison]

Woody,

We keep our installation files on a specified directory on a small computer
that also acts as a file server for our workgroup. Those who have access to
this directory can then install the program as needed.

Brad

"Woody Splawn" <no****@splawns.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

I have a non-web VB.net applicaiton that I have written. I have written it on a client machine of a local area network. The solution is on the local
hard drive of this client machine with the back-end database (SQL Server) on the file server of the network. How do I now make this applicaiton
available to other machines on the local area network? There are about 10
other machines all running XP with the dotnet framework installed.