Whats new in 'NET Remoting for 'NET Framework 2'0

1
Whats new in .NET Remoting for .NET Framework 2.0

• Companion deck for MSDN TV spot

2
IpcChannel

• New channel for on-box communications using named
  pipes
• System.Runtime.Remoting.Channels.Ipc
• Requires a portName (string) for creating the
  underlying named pipe
• Denies off-box communications by denying
  network_sid
• Introduces a new URI scheme for accessing the
  channel
• ipc//myPortName/myObject.rem
• Can be ACLd to limit access
• authorizedGroup config attribute to specify user
  or group allowed access
• ltchannel refipc portNametestPipe
  authorizedGroupAdministrators /gt
• IpcServerChannel ctor accepts CommonSecurityDescri
  ptor for richer ACLs

3
Secure TcpChannel

• Encryption, signing and impersonation added to
  existing TcpChannel
• Use SSPI-based NegotiateStream from
  System.Net.Security
• Existing apps can be upgraded to be more secure
  using simple config changes
• Exposed through simple config option
• ltchannel reftcp securetrue /gt
• Turns on encryption and signing of data
• Both client and server need to switch to
  securetrue
• Also enables identification of caller through
  Thread.CurrentPrincipal.Identity.Name
• Impersonation is easily added
• Server ltchannel reftcp securetrue
  impersonatetrue /gt
• Client ltchannel reftcp securetrue
  tokenImpersonationLevelimpersonation /gt
• Executing identity can be checked with
  WindowsIdentity.GetCurrent().Name

4
Other new features

• Socket cache control for TcpChannel
• Enables controlling cache timeouts for sockets
• ltchannel reftcp socketCacheTimeout0
  socketCachePolicyabsoluteTimeout /gt
• Disabling caching provides for NLB support for
  TcpChannel
• Generics support
• Support for registering closed generic types
• IPv6 support
• Support for binding to IPv6 addresses

5
Version Tolerant Serialization

• Rigidity of the runtime formatters in V1 and V1.1
  made versioning of types difficult
• Added or removed fields resulted in
  de/serialization exceptions
• ISerializable could handle this today but was
  complex
• Only most derived implementation was called,
  which required chaining
• Type authors controlled the adding and removing
  data from the stream

6
Version Tolerant Serialization

• Version Tolerant Serialization makes the
  formatters more flexible
• Changes the formatters to ignore additional data
• Caveat Does not round-trip extra data
• OptionalField attribute marks fields missing
  from older versions
• Serialization processing attributes allow each
  type to participate in de/serialization (see demo
  for examples)

7
More info on .NET Remoting

• Info on the future direction of distributed
  application
• Indigo http//msdn.microsoft.com/Longhorn/underst
  anding/pillars/Indigo/default.aspx
• FAQ http//msdn.microsoft.com/longhorn/support/lh
  devfaq/default.aspxIndigo
• Technology guidance (including .NET Remoting)
  look for a whitepaper on this soon!
• Richard Turners blog http//blogs.msdn.com/richa
  rdt
• Migrating towards the future
• http//msdn.microsoft.com/longhorn/understanding/p
  illars/indigo/migratevideo/