|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Run from Server or WorkstationWhat are some pros and cons associated with running a vb.net app from a
server and from a workstation ? When run from the server, I assume that each instance that is executed is "its own instance" i.e., variables are not shared ? Also, when run from the server, how could you ensure that the same workstation does not have more than 1 instance of the program running ? Thanks Do you mean if it's just on a network share? That is what I assume you mean
here. Pros: Don't have to deploy new version of application to every user Cons: User can't run the app when server is offline or user is disconnected from the server There may be security restrictions imposed on the application by the .net runtime because it is being run from a network share And yes, each instance of the application would be separate, in its own appdomain, it's own variables, etc. You would have to ensure that a user doesn't run the same program twice from the share the same way you would that they dont' run it twice on their local PC. Show quoteHide quote "Rob" <rwch***@comcast.net> wrote in message news:9KadnVy7hovBzkfeRVn-tQ@comcast.com... > What are some pros and cons associated with running a vb.net app from a > server and from a workstation ? > > When run from the server, I assume that each instance that is executed is > "its own instance" i.e., variables are not shared ? Also, when run from > the server, how could you ensure that the same workstation does not have > more than 1 instance of the program running ? > > Thanks > You might also consider a Distributed aproach
thus : 1 server component running on one computer 2 client programs all connecting to this one server component You lighten the load on the clients ( they may even be written as thin clients ) you can share information between the clients and server verry easy etc etc regards Michel Posseth [MCP] Show quoteHide quote "Marina Levit [MVP]" <someone@nospam.com> wrote in message news:%23Za0jn4IGHA.1848@TK2MSFTNGP12.phx.gbl... > Do you mean if it's just on a network share? That is what I assume you > mean here. > > Pros: > > Don't have to deploy new version of application to every user > > Cons: > > User can't run the app when server is offline or user is disconnected from > the server > There may be security restrictions imposed on the application by the .net > runtime because it is being run from a network share > > And yes, each instance of the application would be separate, in its own > appdomain, it's own variables, etc. You would have to ensure that a user > doesn't run the same program twice from the share the same way you would > that they dont' run it twice on their local PC. > > "Rob" <rwch***@comcast.net> wrote in message > news:9KadnVy7hovBzkfeRVn-tQ@comcast.com... >> What are some pros and cons associated with running a vb.net app from a >> server and from a workstation ? >> >> When run from the server, I assume that each instance that is executed is >> "its own instance" i.e., variables are not shared ? Also, when run from >> the server, how could you ensure that the same workstation does not have >> more than 1 instance of the program running ? >> >> Thanks >> > >
Converted a solution to VS2005 and it is complaining: Variable 'PF2' is used before it has been assi
READING EMAILS Problem with installer made in VS 2003.NET Detect Concurrent Running Instances write Override methods in Code Editor VS2005 How do I maintain paragraph numbers into a new word document Can we run Vb.Net Application on Apple Macintosh ? StreamReader does not read all characters... Force ASP.NET shadow directory to update? |
|||||||||||||||||||||||