ASP.NET Efficiency Question

[Z GIRL]

Dear DotNET Developers,

I've developed a plethora of ASP applications which have handled
10's of thousands of transactions per day w/o any problems.
I was wondering, in DOT Net the efficiency papers say to use
the Server based control sparingly in order to create an efficient
application.

The point of going to DOT NET is that the server based controls
reduce the time of development. Now is there any rule to the number
of server controls you should use per form? For instance, if your creating
a contact manager system.

I'm just wondering what people have done to create efficient systems
yet exploit the very funcitonality DOT NET offers w/o reducing performance.

Thanks in advance.

[Cor]

Hi Z Girl,

Did you know that there was a special group ASPNet

Aspnet
<news://msnews.microsoft.com/microsoft.public.dotnet.framework.aspnet>

Web interface:

<http://msdn.microsoft.com/newsgroups...ups/loadframes
..asp?icp=msdn&slcid=us&newsgroup=microsoft.public .dotnet.framework.aspnet>

I hope this helps?

Cor

I've developed a plethora of ASP applications which have handled
10's of thousands of transactions per day w/o any problems.
I was wondering, in DOT Net the efficiency papers say to use
the Server based control sparingly in order to create an efficient
application.

The point of going to DOT NET is that the server based controls
reduce the time of development. Now is there any rule to the number
of server controls you should use per form? For instance, if your creating a contact manager system.

I'm just wondering what people have done to create efficient systems
yet exploit the very funcitonality DOT NET offers w/o reducing performance.
Thanks in advance.