|
|
|
|
|
| | Total Hits: 82 | Today: 0 | Author: logicchild. | Rating:  |
| | 
The intention of this paper is to explain some features of the CLR as a basis to understand the basics of interoperation. This paper will reference some key system symbol components in order to explain how the System.Runtime.InteropServices namespace contains methods that use to enable a C# program to call a native system function contained a raw C DLL. This feature is called P/Invoke, for platform invoke.... |
| | Total Hits: 57 | Today: 0 | Author: Bob Burns | Rating: |
| |
This article discusses some of the issues that you may encounter when developing an application that uses both managed and unmanaged code. It discusses how to include existing COM objects in managed code and how to access Windows APIs from managed code.... |
| | Total Hits: 256 | Today: 0 | Author: Wangming Ye | Rating: |
| |
Web services technology offers the promise and hope of integrating disparate applications in a seamless fashion. But enterprise applications are built around different technologies and platforms, and integration across businesses is never a trivial task. The relatively recent emergence of Business Process Execution Language (BPEL) for Web services provides a higher-level description language to specify the behavior of Web services. It provides a standard and portable language for orchestrating W... |
| | Total Hits: 196 | Today: 0 | Author: Tony Patton | Rating: |
| |
Most development projects leave little room for change; thus, finding development shortcuts can rescue valuable time. One way to efficiently use development time is to take advantage of existing products as opposed to developing everything from scratch. Microsoft Office is one product that you should leverage. In recent columns, we've covered .NET integration with Outlook, Word, and Excel. Today we revisit Excel by utilizing its charting features to present data in a .NET Windows Forms applicati... |
| | Total Hits: 122 | Today: 0 | | Rating:  |
| |
Common Language Infrastructure (CLI) is essentially synonymous with .NET Framework.... |
| | Total Hits: 314 | Today: 0 | | Rating: |
| |
This article walks through the details of how to call Microsoft .NET servers from COM clients, helps you understand the concept of COM callable wrappers, create a .NET server that can be called from VB 6.0, use the sn, regasm, and gacutil utilities, write VB 6.0 code that uses a .NET class... |
| | Total Hits: 52 | Today: 0 | Author: Brian Long | Rating:  |
| |
.NET is a new programming platform representing the future of Windows programming. Developers are moving across to it and learning the new .NET oriented languages and frameworks, but new systems do not appear overnight. It is a lengthy process moving entire applications across to a new platform and Microsoft is very much aware of this.
To this end, .NET supports a number of interoperability mechanisms that allow applications to be moved across from the Win32 platform to .NET piece by piec... |
| | Total Hits: 245 | Today: 0 | Author: Wangming Ye | Rating: |
| |
Part 1 of this series discussed the importance of designing a Web Services Description Language (WSDL) and XML Schema data types (XSD) before code writing, the rationale in completely moving toward the Document/literal style, and the necessity in testing the WS-I Basic Profile conformance when developing Web services. This part illustrates the use and impact data types have on interoperability. The input parameters and return values of data types of a Web service operation have a great impact on... |
| | Total Hits: 115 | Today: 0 | Author: pinturic | Rating:  |
| |
Together with Visual Studio .NET programming environment there is a useful utility that automatically generates a wrapper for COM and ActiveX components: the procedure by which these kinds of components are made available to .NET applications is called COM Interoperability. The way of accessing old_style C++ DLL library within managed application is called platform invoke. Unlike what happens for COM components there is no automated way to access the functions present in native DLL and so each t... |
| | Total Hits: 52 | Today: 0 | Author: Brian Long | Rating: |
| |
.NET is a new programming platform representing the future of Windows programming. Developers are moving across to it and learning the new .NET oriented languages and frameworks, but new systems do not appear overnight. It is a lengthy process moving entire applications across to a new platform and Microsoft is very much aware of this.
To this end, .NET supports a number of interoperability mechanisms that allow applications to be moved across from the Win32 platform to .NET piece by piec... |
| | Total Hits: 64 | Today: 0 | Author: Ted Neward | Rating: |
| |
Java and .NET are both great platforms on their own, but together, they are a practical necessity in the modern enterprise. With enterprise development market share of 35-40% each, it's fairly obvious that neither of these two platforms is "going away" any time soon. It's clear to even the most zealous Java or .NET devotee that working with both platforms is going to become the norm. This article looks at various interoperability issues between the Java and .NET platforms.... |
| | Total Hits: 66 | Today: 0 | Author: Aaron Skonnard | Rating: |
| |
If interoperability is the main promise of Web services, why is it that so many developers and organizations have a difficult time achieving it in practice? With all due respect to our hard-working standards bodies, the primary culprits are the imperfect specifications guiding today's implementations. Ambiguities and too many choices often lead to differing interpretations, resulting in incompatible implementations.
Hence, responsibility lies with the developer for early identification of pro... |
| | Total Hits: 68 | Today: 0 | Author: Damien Watkins | Rating: |
| |
This article outlines the interoperability capabilities of the Microsoft .NET Framework. With the increasing use of distributed systems, interoperability is a major issue to system developers. The problems of interoperability have been around for many years, and a number of standards and architectures have been developed to address some of these issues, with varying degrees of success.... |
| | Total Hits: 65 | Today: 0 | Author: Microsoft Corporation | Rating: |
| |
Many applications using managed code require that a particular version of the .NET Framework be present on the machine. Some applications redistribute a particular release of the.NET Framework. In some cases, applications that were developed on a specific version of the .NET Framework may encounter issues when trying to execute on a newer version of the Framework. As explained in Microsoft .NET Framework 1.1 and 2.0 (Beta) Compatibility, managed applications run by default on the version of the ... |
| | Total Hits: 63 | Today: 0 | Author: Microsoft Corporation | Rating: |
| |
The Microsoft .NET Framework 2.0 builds on the success of the Microsoft .NET Framework 1.0 and 1.1 to provide the best runtime environment for Web and Microsoft Windows client applications. Microsoft's compatibility goal for .NET Framework 1.1 applications is that they should work smoothly on the .NET Framework 2.0 except for a set of documented changes in a compiled HTML Help file named BreakingChanges.chm. During the Beta 2 release, we have not yet achieved the goal of documenting all changes ... |
| | Total Hits: 88 | Today: 0 | Author: Jason Clark | Rating: |
| |
In the July 2003 installment of the .NET column I covered the basics of Win32® interoperation with the Microsoft® .NET Framework (P/Invoke). Based on reader feedback, this topic is worthy of further coverage, so I have decided to revisit P/Invoke in this column. It will build upon the information in the July 2003 issue, so if you are not familiar with basic .NET interop, I suggest reviewing that column before digging into this one. This month I am going to delve into the interop details of marsh... |
| | Total Hits: 130 | Today: 0 | Author: Jason Clark | Rating: |
| |
I have noticed a trend in my programming of late, and that trend has inspired the topic of this month's column. Recently, I have done a fair amount of Win32® Interop in my Microsoft® .NET Framework-based apps. I am not saying that my apps are full of custom interop code, but from time to time I bump into a minor, but nagging, inadequacy in the .NET Framework Class Library that can quickly be alleviated by a call into the Windows® API. As I think about it, any feature limitation in the .NET Frame... |
| | Total Hits: 94 | Today: 0 | Author: Bob Burns | Rating: |
| |
Visual Studio® .NET represents a major change in the way that developers create and run applications by introducing the idea of managed code that targets the common language runtime. Managed code provides many advantages including automatic memory management, attributed programming, and a common type system. Unfortunately, the very features that make managed code so powerful also make it fundamentally different from unmanaged code such as Windows APIs and COM objects. Although Visual Studio .NET... |
| | Total Hits: 264 | Today: 0 | Author: Tony Patton | Rating: |
| |
In a recent column, we explored the process of integrating Microsoft Word with the .NET Framework. There are numerous integration possibilities as the full power of the Microsoft Office Suite is available. In this article, we examine another scenario involving Microsoft Excel. We must point out that the Microsoft Office product suite utilizes the Visual Basic for Applications (VBA), so a little knowledge of the Component Object Model (COM) object is helpful. However, the .NET COM interop feature... |
| | Total Hits: 236 | Today: 0 | Author: Tony Patton | Rating: |
| |
In recent articles I've covered working with various pieces of the Microsoft Office Suite including Word and Excel. Today, I'll continue the concept by manipulating Microsoft Outlook via Microsoft .NET code. As with other Microsoft Office products, Visual Basic for Applications (VBA) is utilized. Consequently, a little COM (Component Object Model) knowledge comes in handy. However, the .NET COM interop feature simplifies the process for .NET developers. Thus, you can easily utilize COM objects w... |
|
|
|
|
|
|
|
|
|
|
|
|
|