Calculating your score ...
Click your answer, then NEXT and END when you are done to find out how you got on!
1 of 20
1. What best defines private components in .NET deployment:
The no-impact application feature isolates installed components from other applications so that there are no DLL conflicts.
If components and applications are self-described and self-contained, then they do not have to be registered and will not have any depend-encies. Thus it is simply a case of copying one folder into another.
This allows for multiple versions of the component or application to be deployed, and the application can choose the one it wants, where the .NET Framework will inform the versioning policy.
As a default the installed components are private, where applications cannot gain access to them. They can be shared, though, if the assembly is assigned a strong name, and the assembly is installed as a global assembly cache.
The private component are installed into an application directory, and are thus only visible to the relevant application, and will not af-fect other applications.