COM and .NET Interoperability

The funny thing about writing a book on COM and .NET interoperability is that one author could craft a five- to ten-page article describing the basic details that you must understand to get up and running with interop-related endeavors. At the same time, another author could write volumes of materia...

Mô tả đầy đủ

Đã lưu trong:
Chi tiết về thư mục
Tác giả chính: Troelsen, Andrew
Định dạng: Sách
Ngôn ngữ:English
Được phát hành: Apress 2012
Những chủ đề:
Truy cập trực tuyến:http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30928
Các nhãn: Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
Thư viện lưu trữ: Thư viện Trường Đại học Đà Lạt
id oai:scholar.dlu.edu.vn:DLU123456789-30928
record_format dspace
spelling oai:scholar.dlu.edu.vn:DLU123456789-309282012-06-07T03:11:48Z COM and .NET Interoperability Troelsen, Andrew Technologies The funny thing about writing a book on COM and .NET interoperability is that one author could craft a five- to ten-page article describing the basic details that you must understand to get up and running with interop-related endeavors. At the same time, another author could write volumes of material on the exact same subject. So, you may be asking, how could this massive discrepancy between authors possibly exist? Well, stop and think for a moment about the number of COM-aware programming languages and COM application frameworks that exist. Raw C++/IDL, ATL, MFC, VB 6.0, and Object Pascal (Delphi) each have their own syntactic tokens that hide the underbelly of COM from view in various ways. Thus, the first dilemma you face as an interop author is choosing which language to use to build the COM sample applications. Next, ponder the number of .NET-aware programming languages that are either currently supported or under development. C#, VB .NET, COBOL .NET, APL .NET, PASCAL .NET, and so on, each have their own unique ways of exposing features of the CTS to the software engineer. Therefore, the next dilemma is choosing which language to use to build the .NET applications. 2012-06-07T03:11:48Z 2012-06-07T03:11:48Z 2002 Book 1590590112 http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30928 en application/chm Apress
institution Thư viện Trường Đại học Đà Lạt
collection Thư viện số
language English
topic Technologies
spellingShingle Technologies
Troelsen, Andrew
COM and .NET Interoperability
description The funny thing about writing a book on COM and .NET interoperability is that one author could craft a five- to ten-page article describing the basic details that you must understand to get up and running with interop-related endeavors. At the same time, another author could write volumes of material on the exact same subject. So, you may be asking, how could this massive discrepancy between authors possibly exist? Well, stop and think for a moment about the number of COM-aware programming languages and COM application frameworks that exist. Raw C++/IDL, ATL, MFC, VB 6.0, and Object Pascal (Delphi) each have their own syntactic tokens that hide the underbelly of COM from view in various ways. Thus, the first dilemma you face as an interop author is choosing which language to use to build the COM sample applications. Next, ponder the number of .NET-aware programming languages that are either currently supported or under development. C#, VB .NET, COBOL .NET, APL .NET, PASCAL .NET, and so on, each have their own unique ways of exposing features of the CTS to the software engineer. Therefore, the next dilemma is choosing which language to use to build the .NET applications.
format Book
author Troelsen, Andrew
author_facet Troelsen, Andrew
author_sort Troelsen, Andrew
title COM and .NET Interoperability
title_short COM and .NET Interoperability
title_full COM and .NET Interoperability
title_fullStr COM and .NET Interoperability
title_full_unstemmed COM and .NET Interoperability
title_sort com and .net interoperability
publisher Apress
publishDate 2012
url http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30928
_version_ 1757669298363432960