The .Net Framework is free from Microsoft.
|
|
"Scheduling Manager on the Web"
web-based scheduling software
System Requirements - overview
The software is Internet / Intranet based.
Developed using ASP.NET - installed only once on
the server and can be up in running in minutes.
Displayed in a browser (Internet Explorer version 5+) at end-user's PC.
Attention to Firefox browser users, please note that Firefox is considered by .Net as a downlevel browser, you may not be able view all elements on the screen properly as our software is developed in ASP.NET
Minimum Requirements:
Thin-client architecture *
 1. Server (at your ISP - Internet Service Provider)
2. Connection to internet (end-user's PC)
Any connection
3. Client (end-user's PC)
Browser: MS Internet Explorer 5+
Our web-based scheduling software lives on your website (server) and can be accessed from anywhere at anytime.
* Thin-client computing refers to multi-tier client
server paradigm where the client (end-user) programs
display in a browser (such as Internet Explorer)
but the execution of that user code takes place on a central web server, not at the desktop PC.
About deployment:
Deployment is the process of taking the application and installing it in on another machine.
Please note, Scheduling Manager is web based software, developed in ASP.NET.
Deploying ASP.NET applications is very straightforward. You need to copy the application files you have extracted from our reservenet.exe to the production Web server that will host your application.
Before looking at the different steps involved in deploying our Scheduling Manager Web application, it is important to understand the Structure of an ASP.NET Web Application.
An ASP.NET application consists of all the Web pages (.aspx and HTML files), handlers, modules, executable code, and other files (such as images and configuration files) that can be invoked from a virtual directory and its subdirectories on a Web server.
An ASP.NET application also includes the compiled assembly (code-behind, .aspx files) and typically other assemblies that are used to provide functionality for the application. These assemblies are located in the bin directory underneath the virtual directory of the application.
The assemblies are so comprehensive and self-describing that ASP.NET applications don't need to be registered with registry.
This means that ASP.NET applications can be installed by simply copying the required files to the target machine as long as the target machine has the .NET Framework installed.
|
top
|
