Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Many C#/VB.NET applications will run 10-30% slower than their unmanaged
counterparts. The main performance hit in managed applications comes from a
need to load the .NET runtime and then compile the application on the fly before
actually running it. Currently it is not uncommon to wait up to 30 seconds for an
ASP.NET page to load on 1.6Ghz 512MB Dell with 500 Mhz Rambus memory.
Additional performance penalty occurs when ActiveX and COM components are
accessed from .NET. Due to the complex marshalling protocol, it may take up to
80 CPU cycles to execute a function from an unmanaged component. As
developers learn .NET optimization tricks and JIT compiler optimization becomes
more efficient, performance of .NET applications will become comparable to C+
+.
2. Should we move our VC++ 6.0 application to VC++ 7.0/7.1/8.0?
The VC++ 2005 is the latest version of Microsoft's VC++ compiler. It has a slue
of Windows compatibility features not available with older compilers. As a rule
of thumb, I recommend migrating to a new compiler within a year of it's
appearance.
3. Where can we find a Web Service that performs a specific task?
struct Complex
{
//public x,y;
public double x,y;
public static Complex operator+(Complex a, Complex b)
{
Complex c;
c.x=a.x+b.x;
c.y=a.y+b.y;
return c;
}
}
class Test{
public static void Main()
{
Complex z1,z2;
z1.x=1;
z1.y=3;
z2.x=0;
z2.y=10;
Console.WriteLine(" x component is: "+(z1+z2).x+" y component is: "+
(z1+z2).y);
}}