Professional Documents
Culture Documents
namespace S#stem.!ata."racleClient. (evelopers using the .NET Framework version 1.1 can download the .NET Framework (ata rovider $or 2racle $rom http344msdn.microso$t.com4downloads. %n addition+ A(2.NET now includes the $ollowing $eatures3
The !ata$eader ob5ect now exposes a %as$ows property to determine i$ rows were returned without having to call $EA! method.
The Connection ob5ect now has an Enlist!istributedTransaction method to enable manual enlistment in distributed transactions.
Side&b#&Side E'ecution The .NET Framework version 1.1 supports side-by-side execution. Side-by-side execution is the ability to store and execute multiple versions o$ an application or component on the same computer. This means that you can have multiple versions o$ the runtime+ and multiple versions o$ applications and components that use a version o$ the runtime+ on the same computer at the same time. %n addition+ subse6uent installations o$ other versions o$ the .NET Framework or o$ a component will not a$$ect the applications already installed. For more in$ormation+ see Side-by-Side Execution.
Page 1
11/19/2013
Visual Studio.NET Best Articles Side-by-side execution does not imply that a managed application is compatible with other versions o$ the runtime or o$ a component. 7ather+ it means that a managed application can choose the runtime and the components it executes with+ and that multiple versions o$ the runtime+ applications+ and components can coexist on the same computer. %t is up to you to decide which versions o$ the runtime and which components a particular application will use. Chan es in .NET Framework Securit# %n version 1.1 and 1.1+ applications that receive less than $ull trust $rom the runtime code access security system cannot call shared managed libraries unless the library writer speci$ically allows them to through the use o$ the Allow artiallyTrusted"allersAttribute attribute. %$ you plan on using libraries $rom partially trusted code+ you need to be aware that some libraries will not be available to your code. %n version 1.1+ System.,eb.dll+ System.,eb.!obile.dll+ and System.,eb.7egularExpressions.dll are included in the list o$ assemblies that have the AllowPartiall#TrustedCallersAttribute and can be called $rom partially trusted code. For more in$ormation+ see 8sing 9ibraries $rom "ode. (e$ault security policy has been changed so that applications executing $rom the %nternet :one and assigned to the (nternet )one code group now receive permissions associated with the (nternet permission set. As a result+ applications $rom the %nternet now receive su$$icient permission to execute. %n the .NET Framework 1.1 Service ack 1 and Service ack 0+ such applications received the permissions associated with the Nothin see (e$ault Security olicy. ASP.NET Securit# in %osted En*ironments AS .NET now supports partial trust in ,eb-based applications+ o$$ering greater security $or multiple applications that are hosted on a single ,eb server. Although the operating system account under which an application runs imposes security restrictions on the application+ the code access security system o$ the common language runtime can help en$orce additional restrictions on selected application resources based on policy that you speci$y. ;ou can use this $eature in a shared server environment to isolate separate applications and with standalone servers where you want applications to run with the minimum necessary privileges. AS .NET provides a <trust= con$iguration directive that helps you con$igure code access security levels $or your applications. %$ your partially trusted AS .NET applications call shared managed libraries+ those libraries must contain an Allow artiallyTrusted"allersAttribute attribute that allows calls $rom partially trusted code. For more in$ormation+ see 8sing 9ibraries $rom "ode. (P*+ Su,,ort in the .NET Framework The .NET Framework version 1.1 supports the emerging update to the %nternet re$erred to as % rotocol+ commonly artially Trusted permission set and could not execute. For more in$ormation+ artially Trusted
version >+ or simply % v>. This protocol is designed to signi$icantly increase the
address space used to identi$y communication endpoints in the %nternet to accommodate its ongoing growth. % v> is supported in the System.Net namespace+ AS .NET+ and ?!9 ,eb services. For more in$ormation+ see %nternet rotocol 'ersion >.
Page 2
11/19/2013