This document provides information on the history and key components of the .NET Framework as well as new features introduced in version 4.5. It began with version 1.0 in 2002 and the latest version is 4.5.2. The .NET Framework includes the Common Language Runtime (CLR) which manages code execution, the Common Type System (CTS) which defines supported data types, and garbage collection for automatic memory management. Version 4.5 introduced improvements such as larger array support, background garbage collection, and regular expression matching timeouts. The document also summarizes WCF concepts like contracts and bindings and describes transport, message, and transport with message credential security options.

1. Net Framework History
 2002 – Version 1.0
 2003 – Version 1.1( VS 2003)
 2014 – Version 4.5.2( VS2013)

2. .Net Framework Key Components
 CLR- Common Language Run Time
 CTS – Common Type System
 Garbage Collector- Automatic Memory Management

3. Core new features and improvements
 Ability to reduce system restarts by detecting and closing
.NET Framework 4 applications during deployment
 Support for arrays that are larger than 2 gigabytes (GB) on
64-bit platforms. This feature can be enabled in the
application configuration file. See
the<gcAllowVeryLargeObjects> element, which also lists
other restrictions on object size and array size.
 Better performance through background garbage
collection for servers. When you use server garbage
collection in the .NET Framework 4.5, background garbage
collection is automatically enabled.

4. Core new features and improvements
 Background just-in-time (JIT) compilation, which is
optionally available on multi-core processors to improve
application performance. See ProfileOptimization.
 Ability to limit how long the regular expression engine will
attempt to resolve a regular expression before it times
out. See the Regex.MatchTimeout property.
 Ability to define the default culture for an application
domain. See the CultureInfo class.
 Console support for Unicode (UTF-16) encoding. See
the Console class.

5. Core new features and improvements
 Support for versioning of cultural string ordering and
comparison data. See the SortVersion class.
 Better performance when retrieving resources.
See Packaging and Deploying Resources in Desktop Apps.
 Zip compression improvements to reduce the size of a
compressed file. See
the System.IO.Compression namespace.
 Ability to customize a reflection context to override
default reflection behavior through
the CustomReflectionContext class.

6. Core new features and improvements
 Support for the 2008 version of the Internationalized Domain
Names in Applications (IDNA) standard when
the System.Globalization.IdnMapping class is used on Windows 8.
 Delegation of string comparison to the operating system, which
implements Unicode 6.0, when the .NET Framework is used on
Windows 8. When running on other platforms, the .NET Framework
includes its own string comparison data, which implements Unicode
5.x. See the String class and the Remarks section of
the SortVersion class.
 Ability to compute the hash codes for strings on a per application
domain basis. See <UseRandomizedStringHashAlgorithm> Element.
 Type reflection support split between Type and TypeInfo classes.
See Reflection in the .NET Framework for Windows Store Apps.

7. WCF 4.5- Key Technical Jargons
 Contract – DataContract, Service Contract
 Behaviour- Operation , Service Behaviour
 Binding and Binding Configuration (BasicHttpBinding,
WsHttpBinding, NetTcpBinding)
 Channels

8. WCF Security - Transport
 Transport -Transport security depends on the mechanism that the binding
you have selected uses. For example, if you are using WSHttpBinding then
the security mechanism is Secure Sockets Layer (SSL) (also the mechanism
for the HTTPS protocol). Generally speaking, the main advantage of
transport security is that it delivers good throughput no matter which
transport you are using. However, it does have two limitations: The first is
that the transport mechanism dictates the credential type used to
authenticate a user. This is a drawback only if a service needs to
interoperate with other services that demand different types of credentials.
The second is that, because the security is not applied at the message level,
security is implemented in a hop-by-hop manner rather than end-to-end.
This latter limitation is an issue only if the message path between client and
service includes intermediaries.

9. WCF Security - Message
 Message : Message security means that every
message includes the necessary headers and data to
keep the message secure. Because the composition
of the headers varies, you can include any number of
credentials. This becomes a factor if you are
interoperating with other services that demand a
specific credential type that a transport mechanism
can't supply, or if the message must be used with
more than one service, where each service demands a
different credential type.

10. WCF Security –
TransportWithMessageCredential
 TransportWithMessageCredential : This choice uses
the transport layer to secure the message transfer,
while every message includes the rich credentials
other services need. This combines the performance
advantage of transport security with the rich
credentials advantage of message security. This is
available with the following
bindings:BasicHttpBinding, WSFederationHttpBinding
, NetPeerTcpBinding, and WSHttpBinding.

11.  XAML
 XAML NameScopes
 <Page
WPF
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" >
<Page.Resources>
<ControlTemplate x:Key="MyButtonTemplate" TargetType="{x:Type Button}">
<Border BorderBrush="Red" Name="TheBorder" BorderThickness="2">
<ContentPresenter/> </Border> </ControlTemplate>
</Page.Resources>
<StackPanel> <Button Template="{StaticResource MyButtonTemplate}">My
first button</Button> <Button Template="{StaticResource
MyButtonTemplate}">My second button</Button> </StackPanel>
</Page>

12. WPF
 Type Converters
In the .NET Framework, the TypeConverter class serves
a particular purpose as part of the implementation for a
managed custom class that can be used as a property
value in XAML attribute usage. If you write a custom
class, and you want instances of your class to be usable
as XAML settable attribute values, you might need to
apply a TypeConverterAttribute to your class, write a
custom TypeConverterclass, or both.

13. Workshop – Code Illustrations
C:WindowsSystem32cmd.exe
Microsoft Windows [Version 7.1.7000]
Copyright (c) 2008 Microsoft Corporation. All rights reserved.
C:UsersUserName>

14. Thank You