I don't think it can be done. Anything in System.Diagnostics requires admin priviliges...

FWIW, bringing down Working set might look better in your TaskManager view, but it does very little to actually reduce memory usage. What you want to really look at is Private Bytes which is generally unaffected by what you do with the working set (or minimizing the app).

You probably have seen this:
http://west-wind.com/weblog/posts/240.aspx


+++ Rick ---

>All,
>
>I have a client that is running a WinForms application through Terminal Services. The user accounts have minimum permissions. I have noticed over time, that the application's working set memory size increases and never gets released. I have found a solution that works if the user is in the Admin group, but I need a way to get the following line of code to work for bare minimum permissions:
>
>System.Diagnostics.Process.GetCurrentProcess().MaxWorkingSet = value;
>
>That line works ok for Admins, but for regular users, it won't. The client is unwilling to give every user Admin privileges on the servers and I want other options than "impersonating" the admin.
>
>The servers are Windows 2000 Server machines that have been "locked down". If anyone knows a security policy setting that will give the application the rights to trim its working set size without giving the user Admin permissions to the machine, please let me know.
>
>TIA,
>
>Travis