Pardon my ignorance, but by nfuse classic are you talking nfuse prior to
nfuse elite, or an even older version. We are currently running nfuse on a
Windows 2000 web server with .NET Framework 1.0 installed (soon to have 1.1
as well). We recently upgrade nfuse to the latest version/patch available,
which may be a point of interest to you if you have not. Prior to that nfuse
sat on its own, non .NET server, so I cannot comment on the speed of older
builds of nfuse.
If nfuse classic is something other than what I talk of, I am not sure what
I can say. I would check out Citrix support, as they likely have something
about this logged, if it is a common problem.
NOTE: The Framework, itself, should not have any impact on the server. The
apps running under the Framework are a different story. And, if the
administrator is letting developers debug on your Citrix, shoot him; it is
easier to replace a bad admin than it is to live in an insane asylum. Plus,
the prisons have better meals. (Yes, the killing the admin comment is tongue
in cheek, but debugging on a production server is a serious offense).
BTW, you should check what .NET apps are running on that server, as they may
be contributing the problem and indicate tthe need for a beefier server.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge
****************************************************************************
****
Think Outside the Box!
****************************************************************************
****
