KevinK wrote:
> I was wondering if anybody could lead me to some documentation or best
> practices, architecture documentation etc.. regarding deploying a VB.NET
> desktop application onto a centralized server which is then accessed by
> terminal services clients.
>
> The idea is to allow the app to run on the server, thereby utilizing server
> resources, and allowing a completely stripped down terminal client PC to run
> the app through the terminal service session.
>
> The server OS will likely be Win2K3 Server or Enterprise Server. I'm worried
> about things such as resources, process sharing, permissions, linkages to
> things like file system servers, exchange servers, automation of programs
> like word, excel etc... The architecture scope is fairly large, I'm planning
> to deploy an n-tier framework with db and business components on application
> servers, have separate file system servers, and probably a clustered SQL
> server environment.
>
> Thanks
> KevinK
>
>
I have used a custom app through terminal services before. One tip,
though, is after deploying the app on the terminal server is to
pre-compile it. The pre-compile allows the system to share copies of
the compiled code among the users. Otherwise, each session will JIT
compile it an execute it.
--- Jeremy
|
Similar Threads
