.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,

Unboxing is the process of converting the value held in the object reference back into a corresponding value type on the stack Syntactically speaking, an unboxing operation looks like a normal casting operation However, the semantics are quite different The CLR begins by verifying that the receiving data type is equivalent to the boxed type; and if so, it copies the value back into a local stack-based variable For example, the following unboxing operations work successfully, given that the underlying type of the boxedInt is indeed an int: private static void SimpleBoxUnboxOperation() { // Make a ValueType (int) variable int myInt = 25; // Box the int into an object reference object boxedInt = myInt; // Unbox the reference back into a corresponding int int unboxedInt = (int)boxedInt; } When the C# compiler encounters boxing/unboxing syntax, it emits CIL code that contains the box/unbox op codes.

While a translation consists of some metadata and a lot of original and translated strings, a portable object template (.pot) file contains all the strings available for translation, without any translated strings. This is useful if you are starting a language translation from scratch or want to determine whether any new strings were added to Drupal since the last version before modifying your site (another way to find this out would be to upgrade a copy of your Drupal site and search for untranslated strings as shown in the Replacing Built-In Strings with Custom Strings section).

If you were to examine your compiled assembly using ildasmexe, you would find the following: method private hidebysig static void SimpleBoxUnboxOperation() cil managed { // Code size 19 (0x13) maxstack 1 locals init ([0] int32 myInt, [1] object boxedInt, [2] int32 unboxedInt) IL_0000: nop IL_0001: ldci4s 25 IL_0003: stloc0 IL_0004: ldloc0 IL_0005: box [mscorlib]SystemInt32.

stloc.1 ldloc.1 unbox.any [mscorlib]System.Int32 stloc.2 ret method Program::SimpleBoxUnboxOperation

You can download the translation files for Drupal core as well as for many contributed modules in dozens of languages from http://localize.drupal.org. On this section of Drupal.org, you will find language-specific translation files (.po files) that can be downloaded and installed, immediately providing multilingual capabilities on your site. You may also wish to install the Localized Drupal (http://drupal.org/project/l10_install) module, which programmatically pulls user interface translations from http://localize.drupal.org, and the Localization Client module (http://drupal.org/ l10n_client), which provides easy ways to localize your site interface through an on-page localization editor interface allowing customization of the interface translation right on the web pages that are being viewed.

Remember that unlike when performing a typical cast, you must unbox into an appropriate data type. If you attempt to unbox a piece of data into the incorrect variable, an InvalidCastException exception will be thrown. To be perfectly safe, you should wrap each unboxing operation in try/catch logic; however, this would be quite labor intensive to do for every unboxing operation. Consider the following code update, which will throw an error because you re attempting to unbox the boxed int into a long: private static void SimpleBoxUnboxOperation() { // Make a ValueType (int) variable. int myInt = 25; // Box the int into an object reference. object boxedInt = myInt; // Unbox in the wrong data type to trigger // runtime exception. try { long unboxedInt = (long)boxedInt; } catch (InvalidCastException ex) { Console.WriteLine(ex.Message); } } At first glance, boxing/unboxing might seem like a rather uneventful language feature that is more academic than practical. After all, You will seldom store a local value type in a local object variable, as seen here. However, it turns out that the boxing/unboxing process is quite helpful because it allows you to assume everything can be treated as a System.Object, while the CLR takes care of the memory-related details on your behalf. Let s look at a practical use of these techniques. Assume you have created a non-generic System.Collections.ArrayList to hold onto a batch of numeric (stack-allocated) data. If you were to examine the members of ArrayList, you would find they are prototyped to operate on System.Object data. Now consider the Add(), Insert(), Remove() methods, as well as the class indexer: public class ArrayList : object, IList, ICollection, IEnumerable, ICloneable { ... public virtual int Add(object value); public virtual void Insert(int index, object value); public virtual void Remove(object obj);

Figure 33-24. A single website with multiple themes Now that your site has a few themes defined, the next logical question is how to apply them to your pages As you might guess, there are many ways to do so.