15.02.2015 Views

C# 4 and .NET 4

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

simple Deployment options ❘ 409<br />

The following server platforms are supported:<br />

➤<br />

➤<br />

Windows 2003 Server Family SP2<br />

Windows 2008 Server Family (Server Core Role not supported)<br />

The following architectures are supported:<br />

➤<br />

➤<br />

➤<br />

x86<br />

x64<br />

ia64 (some features not supported)<br />

Other requirements are Windows Internet Explorer version 5.01 or later, MDAC version 2.8 or later (if the<br />

application is designed to access data), <strong>and</strong> Internet Information Services (IIS) for ASP.<strong>NET</strong> applications.<br />

You also must consider hardware requirements when deploying .<strong>NET</strong> applications. The minimum hardware<br />

requirements for both the client <strong>and</strong> the server are a Pentium 400 MHz <strong>and</strong> 96 MB RAM<br />

For best performance, increase the amount of RAM — the more RAM the better your .<strong>NET</strong> application<br />

runs. This is especially true for server applications.<br />

deploying the .neT runtime<br />

When an application is developed using .<strong>NET</strong>, there is a dependency on the .<strong>NET</strong> runtime. This may seem<br />

rather obvious, but sometimes the obvious can be overlooked. The following table shows the version number<br />

<strong>and</strong> the filename that would have to be distributed:<br />

.neT Version<br />

filename<br />

2.0.50727.42 dotnetfx.exe<br />

3.0.4506.30 dotnetfx3.exe (includes x86 <strong>and</strong> x64)<br />

3.5.21022.8 dotnetfx35.exe (includes x86, x64, <strong>and</strong> ia64)<br />

4.0.0.0 dotnetfx40.exe (includes x86, x64, <strong>and</strong> ia64)<br />

simPle dePloymenT oPTions<br />

If deployment is part of an application’s original design considerations, deployment can be as simple as<br />

copying a set of files to the target computer. For a web application, it can be a simple menu choice in Visual<br />

Studio 2010. This section discusses these simple deployment scenarios.<br />

To see how the various deployment options are set up, you must have an application to deploy. The sample<br />

download at www.wrox.com contains four projects:<br />

➤<br />

➤<br />

➤<br />

➤<br />

ClientWinForms<br />

ClientWPF<br />

WebClient<br />

AppSupport<br />

ClientWinForms <strong>and</strong> ClientWPF are smart client applications using WinForms <strong>and</strong> WPF, respectively.<br />

WebClient is a simple web app. AppSupport is a class library that contains one simple class that returns a<br />

string with the current date <strong>and</strong> time.<br />

The sample applications use AppSupport to fill a label with a string containing the current date. To use<br />

the examples, first load <strong>and</strong> build AppSupport. Then, in each of the other applications, set a reference to the<br />

newly built AppSupport.dll.<br />

www.it-ebooks.info

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!