Resource issues with hosting a windows .net app

[Greg]

I have a client that wants an application developed to run
alongside an existing application currently deployed over
Citrix. I was hoping to write this app using the .Net
framework. However I find that when doing some testing
(on Windows 2000) with a very simple app that accesses a
database, fills a dataset, and also for fun opens a frame
with a crystal report viewer, I find that memory
requirements in RAM quickly skyrocket up to around 40MB.
I hate to think what the app will require when fully
developed. Each time I start a new instance of the app it
requires the same amount of RAM. This is going to cause
some issues with resources for my client who has a large
number of users who will each require to start instances
of the app on the Citrix server. Is there a good approach
to minimising the RAM that will be required? Am I on the
wrong track expecting to use .Net for this development?
Will C++ or VB (pre .Net) be a better fit? What are the
memory requirements of a typical simple .Net data access
application as opposed to a typical Win32 app?

[Mark]

Hi Greg
There are a couple of ways to get round this. You could use a thin client
and .NET Remoting to do all the work on the server - especially using a
touchless deploy so the clients dont install anything.

If RAM is a major concern you can make use of memory mapping in the
System.IO.IsoStorage namespace too :)

"Greg" <ki************@microsoft.com> wrote in message
news:09****************************@phx.gbl...

I have a client that wants an application developed to run
alongside an existing application currently deployed over
Citrix. I was hoping to write this app using the .Net
framework. However I find that when doing some testing
(on Windows 2000) with a very simple app that accesses a
database, fills a dataset, and also for fun opens a frame
with a crystal report viewer, I find that memory
requirements in RAM quickly skyrocket up to around 40MB.
I hate to think what the app will require when fully
developed. Each time I start a new instance of the app it
requires the same amount of RAM. This is going to cause
some issues with resources for my client who has a large
number of users who will each require to start instances
of the app on the Citrix server. Is there a good approach
to minimising the RAM that will be required? Am I on the
wrong track expecting to use .Net for this development?
Will C++ or VB (pre .Net) be a better fit? What are the
memory requirements of a typical simple .Net data access
application as opposed to a typical Win32 app?