Explore topic-wise InterviewSolutions in Current Affairs.

Provides a method, GetDlgControl, that will return an interface pointer on a CONTROL, given the ID of its host window. In addition, the Windows API WRAPPERS exposed by CWINDOW GENERALLY make window management easier.

Provides a method, GetDlgControl, that will return an interface pointer on a control, given the ID of its host window. In addition, the Windows API wrappers exposed by CWindow generally make window management easier.

Wraps an "AtlAxWin80" WINDOW, PROVIDING methods for creating the window, creating a CONTROL and/or ATTACHING a control to the window, and retrieving interface pointers on the host object.

Wraps an "AtlAxWin80" window, providing methods for creating the window, creating a control and/or attaching a control to the window, and retrieving interface pointers on the host object.

ACTS as a base CLASS for ACTIVEX CONTROL classes based on a dialog resource. Such controls can contain other ActiveX controls.

Acts as a base class for ActiveX control classes based on a dialog resource. Such controls can contain other ActiveX controls.

Acts as a BASE CLASS for DIALOG classes based on a dialog resource. Such dialogs can contain ACTIVEX CONTROLS.

Acts as a base class for dialog classes based on a dialog resource. Such dialogs can contain ActiveX controls.

WRAPS an "AtlAxWinLic80" window, providing METHODS for creating the window, creating a control and/or attaching a licensed control to the window, and retrieving interface POINTERS on the HOST OBJECT.

Wraps an "AtlAxWinLic80" window, providing methods for creating the window, creating a control and/or attaching a licensed control to the window, and retrieving interface pointers on the host object.

INITIALIZES the controlhosting CODE.

Initializes the controlhosting code.

Uninitializes the controlhosting CODE.

Uninitializes the controlhosting code.

RETURNS the IUNKNOWN interface pointer of the CONTROL hosted in a window.

Returns the IUnknown interface pointer of the control hosted in a window.

CREATES a modeless dialog BOX from a dialog RESOURCE and returns the WINDOW handle.

Creates a modeless dialog box from a dialog resource and returns the window handle.

CREATES a licensed ACTIVEX CONTROL, initializes it, and HOSTS it in the specified WINDOW, similar to AtlAxCreateControlLic.

Creates a licensed ActiveX control, initializes it, and hosts it in the specified window, similar to AtlAxCreateControlLic.

CREATES a MODAL DIALOG BOX from a dialog RESOURCE.

Creates a modal dialog box from a dialog resource.

RETURNS the IUnknown INTERFACE pointer of the host object connected to a window.

Returns the IUnknown interface pointer of the host object connected to a window.

CREATES a LICENSED ActiveX control, initializes it, and hosts it in the SPECIFIED WINDOW, similar to ATLAXCREATECONTROL.

Creates a licensed ActiveX control, initializes it, and hosts it in the specified window, similar to AtlAxCreateControl.

Creates a host OBJECT, connects it to the supplied WINDOW, then loads a CONTROL (also allows event sinks to be SET up).

Creates a host object, connects it to the supplied window, then loads a control (also allows event sinks to be set up).

CREATES a host object, connects it to the SUPPLIED WINDOW, then loads a CONTROL.

Creates a host object, connects it to the supplied window, then loads a control.

Creates a HOST object, CONNECTS it to the SUPPLIED window, then ATTACHES an existing CONTROL.

Creates a host object, connects it to the supplied window, then attaches an existing control.

The FOLLOWING are the top three REASONS an ATL server might fail to register:

1. You built your project with _WIN32_WINNT=0x400 (the default), and you are not running the ATL server under Windows NT 4.0 or you do not have an uptodate version of Oleaut32.dll. To solve this problem, run "DUMPBIN /EXPORTS OLEAUT32.DLL" and search for UnregisterTypelib. If it is not there, then your server cannot run. Remove this #define statement from Stdafx.h if you want to run the ATL server under Windows 95 or older versions of Windows NT. Alternatively, you can use LoadLibrary and GetProcAddress so that you can run optimally under both Windows 95 and Windows NT 4.0. The Oleaut32.dll that ships with the Internet Explorer 3.x is uptodate.
2. You built your project as MinSize and Atl.dll is not properly INSTALLED on the system. The correct version of Atl.dll must be copied and registered by Regsvr32. There are Windows NT and Windows 95 versions of Atl.dll. The Windows 95 version runs under Windows NT. However, since it does not use the UNICODE APIs, it is slightly less efficient. Unless you build your project as MinDependency, you will need to install the correct version of Atl.dll and run Regsvr32 on it before you install your server.
3. You built your project as UNICODE, and you cannot run it under Windows 95.

The following are the steps to troubleshoot:

1. For a DLL server, run Regsvr32 in the debugger. Open the Project Settings dialog box and click the Debug tab. In the Executable for debug SESSION text box, enter the full path to Regsvr32.exe, such as C:SharedideBinRegsvr32.exe. In the PROGRAM arguments text box, specify the full path to your DLL, such as C:MyprojectsMyFolderDebugMyFile.dll. Set a breakpoint at DllRegisterServer and start stepping.
2. For an EXE server, run it in the debugger and specify /REGSVR as its commandline argument.

The following are the top three reasons an ATL server might fail to register:

The following are the steps to troubleshoot:

Because before calling _Main, PROGRAM MIGHT be calling other function which is needed to initialize the memebers of the program. If that function calling FAILS, then it THROWS so called linker error.

Because before calling _Main, program might be calling other function which is needed to initialize the memebers of the program. If that function calling fails, then it throws so called linker error.

The ATL 2.0 Object Wizard might not be present in the Component Gallery. The ATL 2.0 Object Wizard is not installed by the main ATL 2.0 setup program (Atlinst.exe).

It requires a separate setup program. You need to DOWNLOAD and run the ATL 2.0 Object Wizard Technology Preview (Objinst.exe) from the ATL WEB PAGE. There is a separate ZIP file for Windows NT 3.51.

The ATL 2.0 Object Wizard may crash if an older version of Oleaut32.dll is installed on the system. Make sure the version of Oleaut32.dll is at least 2.20.4049. The latest version is available for download at the Internet Explorer 3.x Web SITE. If this does not fix the problem, then install Service Pack 2 for Windows NT 4.0.

The ATL 2.0 Object Wizard might not be present in the Component Gallery. The ATL 2.0 Object Wizard is not installed by the main ATL 2.0 setup program (Atlinst.exe).

It requires a separate setup program. You need to download and run the ATL 2.0 Object Wizard Technology Preview (Objinst.exe) from the ATL Web page. There is a separate ZIP file for Windows NT 3.51.

The ATL 2.0 Object Wizard may crash if an older version of Oleaut32.dll is installed on the system. Make sure the version of Oleaut32.dll is at least 2.20.4049. The latest version is available for download at the Internet Explorer 3.x Web site. If this does not fix the problem, then install Service Pack 2 for Windows NT 4.0.

ATL's controlhosting CODE doesn't require you to USE any ATL classes; you can simply create an "AtlAxWin80" window and use the controlhosting API if NECESSARY.

ATL's controlhosting code doesn't require you to use any ATL classes; you can simply create an "AtlAxWin80" window and use the controlhosting API if necessary.

ATL's controlhosting API is the set of functions that allows any window to act as an ActiveX control container.

These functions can be statically or dynamically linked into your project SINCE they are AVAILABLE as source CODE and exposed by ATL80.dll.

ATL's controlhosting API is the set of functions that allows any window to act as an ActiveX control container.

These functions can be statically or dynamically linked into your project since they are available as source code and exposed by ATL80.dll.

"AtlAxWin80" is the name of a window class that helps PROVIDE ATL's controlhosting functionality. When you create an instance of this class, the window procedure will automatically use the controlhosting API to create a host object ASSOCIATED with the window and load it with the CONTROL that you specify as the title of the window.

"AtlAxWin80" is the name of a window class that helps provide ATL's controlhosting functionality. When you create an instance of this class, the window procedure will automatically use the controlhosting API to create a host object associated with the window and load it with the control that you specify as the title of the window.

Use the CAXWINDOW class as described below:

Make SURE that AtlAxWinInit has been CALLED.

AtlAxWinInit()

Use the CAxWindow class as described below:

Make sure that AtlAxWinInit has been called.

AtlAxWinInit()

In Windows, Thread is an UNIT of execution.Process is the environment in which thread executes.Scheduler, schedules the Threads not the process.

In UNIX variants,Thread is TREATED as LIGHT WEIGHT process.

Scheduler, schedules the process not threads.

In Windows, Thread is an unit of execution.Process is the environment in which thread executes.Scheduler, schedules the Threads not the process.

In Unix variants,Thread is treated as light weight process.

Scheduler, schedules the process not threads.

Yes There is diff between, both will GIVE you error. ONE will give COMPILER error and ANOTHER will give systax error.

Yes There is diff between, both will give you error. one will give compiler error and another will give systax error.

• A stencil is any text FILE that contains special tags understood by CStencil Class (used to parse a stencil and generate a text stream by replacing elements found within the stencil by output generated by an object implementing the ITagReplacer INTERFACE) or a derived class.
• A SRF is a stencil containing tags understood by CHtmlStencil. 
• The stencil processor is a FEATURE which allows content generation based on the stencil SRF files.
• It allows separating the static PART of the response from dynamic content.

• There can be many Web APPLICATION DLLs in a virtual directory which can provide one or more named request handlers.
• They have the FUNCTIONALITY for handling requests and generating responses.
• They expose request handlers that communicate with the ISAPI extension DLL.
• Each Web application DLL can be used from multiple server response files.
• Server response files are basically text files.
• They contain the static parts of a response and special tags.
• These special tags describe where request handler methods can be called to GENERATE the dynamic parts of the response.
• Each server response FILE can use more than one Web application DLL.
• The requests from IIS are received by the ISAPI extension DLL and are passed to the appropriate Web application DLL.
• It provides the request handling infrastructure and common services used by the Web application DLLs.
• One ISAPI extension DLL exists per virtual directory and it handles requests for files with the .dll and .srf extensions.

SRF files contain HTML and script tags denoted by the {{ opening and }} closing braces.

A single SRF file MAY call code from a number of application DLLs and a single application DLL may serve a number of SRF files.

Following is a list of tags USED in the SRF:

• The codepage tag within an SRF is used when the SRF is parsed.
• The comment tag does not rendered on the client Web browser.
• The handler tag specifies the name of the Web application DLL and the name of the REQUEST handler. There can only be one handler tag per SRF.
• The include tag inserts the rendered content of another SRF at the current position of the SRF that uses it.
• The locale tag signifies that any content rendered after that point in the file should support the locale that is specified.
• The replacement tag is a customized tag that is REPLACED with content from the request handler within your Web application DLL.
• The subhandler tag defines an additional request handler. Unlike the handler tag, there can be multiple subhandler tags within an SRF.

SRF files contain HTML and script tags denoted by the {{ opening and }} closing braces.

A single SRF file may call code from a number of application DLLs and a single application DLL may serve a number of SRF files.

Following is a list of tags used in the SRF:

SRF files contain HTML and script TAGS denoted by the {{ opening and }} closing braces.

A single SRF file may call code from a NUMBER of application DLLs and a single application DLL may SERVE a number of SRF files.

The simplest SRF file must contain one or more references to application DLLs and one or more calls to a function within those DLLs. 

Eg:

{{handler ATLServerHelloWorld.dll/Default}}
<html>
<body>
{{Hello CareerRide}}
</body>
</html>

The first line of the file is USED to identify the DLL and the CLASS that the SRF file will make calls to.

{{handler ATLServerHelloWorld.dll/Default}}.

SRF files contain HTML and script tags denoted by the {{ opening and }} closing braces.

A single SRF file may call code from a number of application DLLs and a single application DLL may serve a number of SRF files.

The simplest SRF file must contain one or more references to application DLLs and one or more calls to a function within those DLLs. 

Eg:

{{handler ATLServerHelloWorld.dll/Default}}
<html>
<body>
{{Hello CareerRide}}
</body>
</html>

The first line of the file is used to identify the DLL and the class that the SRF file will make calls to.

{{handler ATLServerHelloWorld.dll/Default}}.

• ATL Server is a SET of native C++ classes that allows developers to create WEB applications, XML Web services, and other server applications.
• MANY classes may also be used in client applications or components.

The Web server RECEIVES requests from the client and passes them on to the ISAPI extension DLL when the request is for a file extension handled by that DLL.

The ISAPI extension DLL receives requests from IIS and passes them on to the appropriate Web application DLL.

Web application DLLs provide application-specific functionality for handling requests and generating responses.

Server response files are TEXT files that contain the static parts of a response and special TAGS describing where request handler methods can be called to generate the dynamic parts of the response.

The Web server receives requests from the client and passes them on to the ISAPI extension DLL when the request is for a file extension handled by that DLL.

The ISAPI extension DLL receives requests from IIS and passes them on to the appropriate Web application DLL.

Web application DLLs provide application-specific functionality for handling requests and generating responses.

Server response files are text files that contain the static parts of a response and special tags describing where request handler methods can be called to generate the dynamic parts of the response.

• ATL Server is developed by Microsoft for developing web BASED applications.
•  ATL Server is a library of C++ classes that allow DEVELOPERS to build internet based applications.
• It includes a template library which is dedicated for use with developing Web-based applications.

It provides the functionality required to build large scale internet sites like:

- SOAP messaging
- caching facilities
- threading facilities
- regular expression processing
- management of session-state
- performance monitoring
- MIME support
- INTEGRATION with IIS and CLASS for interacting with security
- cryptographic infrastructure.

It provides the functionality required to build large scale internet sites like:

- SOAP messaging
- caching facilities
- threading facilities
- regular expression processing
- management of session-state
- performance monitoring
- MIME support
- Integration with IIS and class for interacting with security
- cryptographic infrastructure.