Hi Tom,
Thanks for the quick reply.
From what I could tell, it seems (again, I am completely guessing here),
that AppDomains would potentially reduce the memory footprint of my
application.
The application itself is a TimeClock application (Punch In/Out etc). It
connects to a SQL db. Nothing super complicated, but it has many screens,
grids etc with information.
Am I wrong to assume that this will potentially free up a considerable
amount of memory on my Terminal Server? Currently, this is installed on a
Test Terminal server, and each TimeClock process is taking between 35 to 45
mb of memory.
"Tom Shelton" <tom_shelton@YOUKNOWTHEDRILLcomcast.netwrote in message
news:%23NGrYKGsIHA.3780@TK2MSFTNGP03.phx.gbl...
Quote:
On 2008-05-07, Kevin L <no_spam@not_real_email.comwrote:
Quote:
>I have an application (Winforms application) that allocates quite a bit
>of
>memory (like 45mb). This application is destined to run in a Terminal
>Server
>environment by multiple users at the same time.
>>
>I would like to reduce the footprint as much as possible.
>>
>I have read a little about AppDomain, but I am have no idea how to
>implement
>it for my application.
>>
>Any AppDomain for Dummies help would be greatly appreciated.
>>
>VS2005 VB.NET
>>
>>
>
What exactly were you thinking of doing? There are issues surrounding
the use of appdomains, that really depend on what kind of architecture
your planning?
>
--
Tom Shelton