W
Woody Splawn
I have a non-web (winforms) VS dot net application that I have written using
SQL Server 2000 as the back-end. This was done on a local area network with
a dedicated file server. SQL Server 2000 resides on the file server and a
full blown version of VS.net is on a client machine of the server. My
solution resides on the local C drive. At this point in time I suppose I am
doing what you would call a client/server type application in a two tier
architecture. Is this Correct?
So far so good. My applicaiton runs and works fine. However, I would like
the application to be accessable to other machines on the network. The
other machines all run Windows XP and have the dot net framework. My
question has to do with the best way to do this.
I suppose from the original machine I could create an .msi file, copy it to
each of the other machines on the network and run it but this seems tidious.
Another thought that comes to me is that instead of creating the solution on
the local drive of the design machine, maybe I should create it on a shared
drive of the server. Perhaps then I could compile to release mode and the
other client machines could simply access the .exe that release mode
creates. Is this possible and the way you do things in dot net or do I have
it wrong? My guess is that at this point I would effectively have a 3-tier
solution its just that the middle tier and the data tier would be considered
as residing on the same machine - i.e., the file server.
Any clarification would be appreciated.
SQL Server 2000 as the back-end. This was done on a local area network with
a dedicated file server. SQL Server 2000 resides on the file server and a
full blown version of VS.net is on a client machine of the server. My
solution resides on the local C drive. At this point in time I suppose I am
doing what you would call a client/server type application in a two tier
architecture. Is this Correct?
So far so good. My applicaiton runs and works fine. However, I would like
the application to be accessable to other machines on the network. The
other machines all run Windows XP and have the dot net framework. My
question has to do with the best way to do this.
I suppose from the original machine I could create an .msi file, copy it to
each of the other machines on the network and run it but this seems tidious.
Another thought that comes to me is that instead of creating the solution on
the local drive of the design machine, maybe I should create it on a shared
drive of the server. Perhaps then I could compile to release mode and the
other client machines could simply access the .exe that release mode
creates. Is this possible and the way you do things in dot net or do I have
it wrong? My guess is that at this point I would effectively have a 3-tier
solution its just that the middle tier and the data tier would be considered
as residing on the same machine - i.e., the file server.
Any clarification would be appreciated.