Free asp.net component software for windows

SMConvexButton component is an extension of the TBitBtn component that allows to display a caption and glyph. It looks like an IBM-button.

Are you a developer of web applications in ASP.NET? Do users of your applications upload data onto the server? Do they complain that every server upload is time-consuming and that they have no way of telling whether their upload is complete?
If you find yourself in one of the above then the ASP.NET Upload component should be your answer. This component fills in the gap left by browser developers and ASP.NET programmers, monitors data transfer onto the server in a clear way, and provides the following information: overall size of the transfered file or files names of the transfered files, information about the amount of data that has been sent to the server, elapsed transfer time, estimated time remaining until end of file transfer, current transfer rate, possible graphical representation of the file transfer.
Main features:
Project integration
- The component can be integrated into a project simply using the HTTP module (by adding a single line to the Web.config file).
- The standard means of access to saved files is using Request.Files or UploadFile.File.
- It is possible to use a special button to submit data to the server.
Transfer monitoring window
- The standard means of monitoring upload is in a separate window, which is pre-prepared as part of the component.
- Furthermore you have the option to program a window of your own and thus control the information displayed in it, and modify the design to suit the needs of your application.
- You can devise your own means of displaying transfer progress and can display further information such as the progress of processing the files sent on the server.
Technical specifications - server
- Operating systems Windows 2003 .NET Server, Windows 2000 Server, Windows XP, Windows 2000 Workstation
- Microsoft Internet information server (IIS) versions 5.0, 5.1 and 6.0
- MS Framework 1.0 or 1.1
Supported and tested browsers
- MS IE 5.0 and higher
- Mozilla 1.7 and higher
- Mozilla FireFox 0.9.3 and higher
- Opera 6.0 and higher
- Netscape 6.0 and higher
Version restrictions:
- it monitors the transfer of the first half of the data only

Pivo.Ping allows you to effortless enable your applications to send Internet Control Message Protocol (Ping/ICMP) packets in .NET. Programmatically ping a remote server, host, route, or any network device to see if it is up. Pivo.Ping fully supports RFC 792 standard.
Pivo.Ping is a server component. It requires the Microsoft .NET runtime in order to function properly. Pivo.Ping is used to programmatically ping hosts on a network.
A Ping is a technique for sending an ICMP (Internet Control Message Protocol) packet(s) to a remote host. If the remote host is up, and supports ICMP, a control message, or packet, will be sent back to the sender. This technique provides a mechanism for feedback about communication problems in a networked environment. Pivo.Ping abstracts this mechanism in an easy to use manner for the programmer. For more information about ICMP, check out the RFC 792 at http://www.faqs.org/rfcs/rfc792.html.
Pivo.Ping can only be used programmatically from a .NET environment, including, but not limited to, ASP.NET, winforms, console applications, and web services. Here are two brief examples for using Pivo.Ping from C# and Visual Basic. The following example pings www.pivo.com. [C#] Private void Page_Load (object sender, System.EventArgs e) { if ( Page.IsPostBack ) { Pivo.Ping.Icmp icmp = new Pivo.Ping.Icmp("www.pivo.com"); for (int i = 0; i < 4; i++) { Console.WriteLine(icmp.Ping().TotalMilliseconds); } } }.
Pivo.Ping is a low overhead, highly optimized assembly that needs the Microsoft .NET (or equivalent) framework to run. Any system that can support the Microsoft.NET framework will be able to use Pivo.Ping. Pivo.Ping can be used from any environment supported by .NET, which can include winforms, ASP.NET, console applications, components, or web services.