Explore topic-wise InterviewSolutions in .

To reduce complexity COM+ USED or provides role­based security service that's helps in middle­tier components.

There are two types of rolebased security:

1. Declarative
2. Programmatic

When we applied and configure security without using an explicit PROGRAMMING interface is known as declarative security settings. On the other hand there are some situation when work load is HEAVY and secuirty is must and exchange of data ACROSS the network and security MEASURE should be taken with programming interface and it is known as programmatic security

To reduce complexity COM+ used or provides role­based security service that's helps in middle­tier components.

There are two types of rolebased security:

When we applied and configure security without using an explicit programming interface is known as declarative security settings. On the other hand there are some situation when work load is heavy and secuirty is must and exchange of data across the network and security measure should be taken with programming interface and it is known as programmatic security

Transaction consists of group of task BIND in a single execution unit .When a transaction starts with specific task it is completed when all the statement in units are completed if any one produce error it will Rollback.

So transaction have only two result Success and FAILURE. On the other hand COM+ components need code to transaction.Because it will automatically participate in transaction.Its not require any explicit code to specify the START and end of transaction.

when we CREATE an object of COM+ it is activated with BeginTransaction with COM+ services provides.And this object is deactivated using CommitTransaction or AbortTransaction method.

Transaction consists of group of task bind in a single execution unit .When a transaction starts with specific task it is completed when all the statement in units are completed if any one produce error it will Rollback.

So transaction have only two result Success and failure. On the other hand COM+ components need code to transaction.Because it will automatically participate in transaction.Its not require any explicit code to specify the start and end of transaction.

when we create an object of COM+ it is activated with BeginTransaction with COM+ services provides.And this object is deactivated using CommitTransaction or AbortTransaction method.

To enable the communication between COM and .NET components, the .NET Framework generates a COM Callable Wrapper (CCW).

The CCW enables communication between the calling COM CODE and the MANAGED code. It also handles CONVERSION between the data types, as well as other MESSAGES between the COM types and the .NET types.

To enable the communication between COM and .NET components, the .NET Framework generates a COM Callable Wrapper (CCW).

The CCW enables communication between the calling COM code and the managed code. It also handles conversion between the data types, as well as other messages between the COM types and the .NET types.

A proxy OBJECT generated by the COMMON LANGUAGE runtime so that existing COM applications can use MANAGED classes, including .NET Framework classes, transparently.

A proxy object generated by the common language runtime so that existing COM applications can use managed classes, including .NET Framework classes, transparently.

we acn REGISTER the COM+ SERVICES USING the "regsvcs" command

we acn register the Com+ services using the "regsvcs" command

ContextUtil is the PREFERRED class to USE for obtaining COM+ context INFORMATION.

ContextUtil is the preferred class to use for obtaining COM+ context information.

• AUTOMATIC Transaction
• DISTRIBUTED Transactions
• Object POOLING

com ARCHITECTURE NEEDS registratation & classids where as .NET architecture does not need registration & classids

com architecture needs registratation & classids where as .net architecture does not need registration & classids

Wrapper classes are USED to encapsulate values of PRIMITIVE types in objects, so that they can be PASSED AROUND in the same manner.

Wrapper classes are used to encapsulate values of primitive types in objects, so that they can be passed around in the same manner.

Com Callable Wrapper :

1. Create Assembly and compile with strong NAME. 
2. Register Assembly USING regasm <assembly name> 
3. Register Assembly in GAC using gacutil /i <assembly name> 
4. Use tlbexp <assemblyname.dll> to export Assembly as Type LIBRARY for COM. 

Runtime Callable Wrapper :

1. Create PUBLIC Key Token file using sn.exe –k <keyfilename.snk> 
2. Use tlbimp <TypeLibFileName> /KEYFILE: <keyfilename.snk>
   /out: <AssemblyName.dll>
3. Register Imported Assembly in GAC using gacutil /i
   <AssemblyName.dll>

Com Callable Wrapper :

Runtime Callable Wrapper :

1. Does not supports implement-inheritence
2. VERSION COMPATIBILITY.
3. FULLY dependant on registry hence doesn't work on non-window PLATFORMS.,

yes because when server TRANSFER DATA that will in SERIALIZE and any format they used which SERIALIZED data in COM

yes because when server transfer data that will in serialize and any format they used which serialized data in com

We can pass COMMAND line ARGUEMENTS in VB. We can SPECIFY the arguement in project properties -> make tab. 

Instead we can pass it as command line arguement. The ARGUMENT will be in a object called 'command' and/or 'command$'.

We can pass command line arguements in VB. We can specify the arguement in project properties -> make tab. 

Instead we can pass it as command line arguement. The argument will be in a object called 'command' and/or 'command$'.

8085 is basic MICROPROCESSOR, why we are learning in 21TH centuri for example: u want lean java , before must know some C&C++ CONCEPTS, other wise it will difficult like that we learn some basic after will GO for advanced

8085 is basic microprocessor, why we are learning in 21th centuri for example: u want lean java , before must know some C&C++ concepts, other wise it will difficult like that we learn some basic after will go for advanced

You can no longer install COM+ DLLs into the System32 folder on the server. In Windows 2003 server and beyond (including Windows 7) when exporting COM+ package any DLLs registered in WindowsSystem32 (or folders below that) will not be exported. ACCORDING to Microsoft SUPPORT, this is by design.(This information has not been published publicly by Microsoft, so we had to open a ticket with them to discover the issue.)

The symptoms are that the exported MSI files do not contain the COM+ DLLs if:

• the COM+ DLL is registered in System32 and
• the COM+ package is exported on Windows 2003 or later.

The MSI will be created and will install, however the applications will not be able to instantiate the OBJECTS because the DLL was never installed. Opening the MSI with a install editor like Wise INSTALLATION Editor will reveal that the DLL is not included in the MSI.

You can no longer install COM+ DLLs into the System32 folder on the server. In Windows 2003 server and beyond (including Windows 7) when exporting COM+ package any DLLs registered in WindowsSystem32 (or folders below that) will not be exported. According to Microsoft Support, this is by design.(This information has not been published publicly by Microsoft, so we had to open a ticket with them to discover the issue.)

The symptoms are that the exported MSI files do not contain the COM+ DLLs if:

The MSI will be created and will install, however the applications will not be able to instantiate the objects because the DLL was never installed. Opening the MSI with a install editor like Wise Installation Editor will reveal that the DLL is not included in the MSI.

Transaction Atomicity has four attributes:-ACID (atomicity, consistency, isolation, and durability) is an ACRONYM device for learning and emembering the four primary attributes ensured to any transaction by a transaction manager (which is also called a transaction monitor). These attributes are GIVEN below: 

• Atomicity. In a transaction involving two or more discrete pieces of information, either all of the pieces are committed or none are. 
• Consistency. A transaction either CREATES a new and valid state of data, or, if any failure occurs, returns all data to its state before the transaction was started. 
• Isolation. A transaction in process and not yet committed must REMAIN ISOLATED from any other transaction. 
• Durability. Committed data is saved by the system such that, even in the event of a failure and system restart, the data is available in its correct state.

Transaction Atomicity has four attributes:-ACID (atomicity, consistency, isolation, and durability) is an acronym device for learning and emembering the four primary attributes ensured to any transaction by a transaction manager (which is also called a transaction monitor). These attributes are given below: 

We MUST ENSURE that the SYSTEM is ALWAYS left at the correct state in case of the FAILURE or success of a transaction.

We must ensure that the system is always left at the correct state in case of the failure or success of a transaction.

ENSURE data integrity by protecting concurrent transactions from SEEING or being adversely AFFECTED by each other's PARTIAL and uncommitted results.

Ensure data integrity by protecting concurrent transactions from seeing or being adversely affected by each other's partial and uncommitted results.

Make SURE that the SYSTEM can RETURN to its ORIGINAL state in case of a failure.

Make sure that the system can return to its original state in case of a failure.

• With OBJECT pooling, COM+ creates OBJECTS and keeps them in a pool, where they are ready to be used when the NEXT client MAKES a request. 
• This improves the performance of a server application that HOSTS the objects that are frequently used but are expensive to create.

The objective of JIT activation is to minimize the amount of time for which an object lives and consumes RESOURCES on the server.

With JIT activation, the client can hold a reference to an object on the server for a long time, but the server CREATES the object only when the client calls a method on the object. 

After the method call is COMPLETED, the object is freed and its memory is reclaimed. JIT activation enables applications to scale up as the number of users INCREASES.

The objective of JIT activation is to minimize the amount of time for which an object lives and consumes resources on the server.

With JIT activation, the client can hold a reference to an object on the server for a long time, but the server creates the object only when the client calls a method on the object. 

After the method call is completed, the object is freed and its memory is reclaimed. JIT activation enables applications to scale up as the number of users increases.

In the ROLE-based security model, access to parts of an application are granted or denied based on the role to which the CALLERS belong. 

A role DEFINES which members of a Windows domain are allowed to work with what components, methods, or INTERFACES

In the role-based security model, access to parts of an application are granted or denied based on the role to which the callers belong. 

A role defines which members of a Windows domain are allowed to work with what components, methods, or interfaces

The queued components service enables you to create components that can EXECUTE asynchronously or in disconnected MODE. 

Queued components ensure availability of a SYSTEM even when one or more sub-systems are temporarily unavailable. 

Consider a scenario where SALESPEOPLE take their laptop computers to the field and enter orders on the go. 

Because they are in disconnected mode, these orders can be queued up in a MESSAGE queue. When salespeople connect back to the network, the orders can be retrieved from the message queue and processed by the order processing components on the server.

The queued components service enables you to create components that can execute asynchronously or in disconnected mode. 

Queued components ensure availability of a system even when one or more sub-systems are temporarily unavailable. 

Consider a scenario where salespeople take their laptop computers to the field and enter orders on the go. 

Because they are in disconnected mode, these orders can be queued up in a message queue. When salespeople connect back to the network, the orders can be retrieved from the message queue and processed by the order processing components on the server.

Loosely coupled EVENTS ENABLE an object (PUBLISHER) to publish an EVENT. Other objects (subscribers) can subscribe to an event. 

COM+ does not require PUBLISHERS or subscribers to know about each other. Therefore, loosely coupled events greatly simplify the programming model for distributed applications.

Loosely coupled events enable an object (publisher) to publish an event. Other objects (subscribers) can subscribe to an event. 

COM+ does not require publishers or subscribers to know about each other. Therefore, loosely coupled events greatly simplify the programming model for distributed applications.

The APPLICATION generates CORRECT and CONSISTENT information all the time.

The application generates correct and consistent information all the time.

The application meets its requirement for EFFICIENCY EVEN if the NUMBER of USERS increases.

The application meets its requirement for efficiency even if the number of users increases.

USERS can DEPEND on USING the APPLICATION when NEEDED.

Users can depend on using the application when needed.

The APPLICATION is NEVER disrupted or compromised by the efforts of MALICIOUS or IGNORANT users.

The application is never disrupted or compromised by the efforts of malicious or ignorant users.

System.EnterpriseServices

System.EnterpriseServices

DEPLOYMENT and maintenance of the application is as EFFICIENT and painless as POSSIBLE.

Deployment and maintenance of the application is as efficient and painless as possible.