文件名称:SOURCES
- 所属分类:
- 通讯编程
- 资源属性:
- [Windows] [Visual.Net] [源码]
- 上传时间:
- 2012-11-26
- 文件大小:
- 80kb
- 下载次数:
- 0次
- 提 供 者:
- m***
- 相关连接:
- 无
- 下载说明:
- 别用迅雷下载,失败请重下,重下不扣分!
介绍说明--下载内容均来自于网络,请自行研究使用
IPC Between Managed and Unmanaged Code
-Technology keeps leaping forward at a fast pace applications in projects, large or small, normally cannot keep up with this speed. On one hand, it doesn t make sense to port old code to the new state merely for the status on the other hand, it also isn t efficient not to use the modern technologies for new designs. Hence, what we get is a mixture of old and new stuff, or as Microsoft depicts it: the Managed and Unmanaged world, creating a new problem when both worlds have to communicate.
There exists, of course, the well-known Inter Process Communication-IPC-, the Microsoft Windows operating system mechanism for facilitating communication and data sharing between applications. This, however, is mainly a property of the old world the .NET fr a mework does not support such a thing, up till version 2.0. Even then, it is still a question whether it is usable for communication with the old world, or that it is only meant for inter-.NET-communication.
The solution presented here s
-Technology keeps leaping forward at a fast pace applications in projects, large or small, normally cannot keep up with this speed. On one hand, it doesn t make sense to port old code to the new state merely for the status on the other hand, it also isn t efficient not to use the modern technologies for new designs. Hence, what we get is a mixture of old and new stuff, or as Microsoft depicts it: the Managed and Unmanaged world, creating a new problem when both worlds have to communicate.
There exists, of course, the well-known Inter Process Communication-IPC-, the Microsoft Windows operating system mechanism for facilitating communication and data sharing between applications. This, however, is mainly a property of the old world the .NET fr a mework does not support such a thing, up till version 2.0. Even then, it is still a question whether it is usable for communication with the old world, or that it is only meant for inter-.NET-communication.
The solution presented here s
(系统自动生成,下载前可以参看下载内容)
下载文件列表
IPCinCSharp\App.ico
...........\AssemblyInfo.cs
...........\bin
...........\...\Release
...........\...\.......\IPCinCSharp.exe
...........\Form1ICS.cs
...........\Form1ICS.resx
...........\IPCinCSharp.csproj
...........\IPCinCSharp.csproj.user
...........\IPCinCSharp.sln
...........\WINUSER_H
...........\.........\WinUser.h
IPCinCSharp
SendPostMessageInCSharp\App.ico
.......................\AssemblyInfo.cs
.......................\bin
.......................\...\Release
.......................\...\.......\SendPostMessageInCSharp.exe
.......................\Form1SPMC.cs
.......................\Form1SPMC.resx
.......................\SendPostMessageInCSharp.csproj
.......................\SendPostMessageInCSharp.csproj.user
.......................\SendPostMessageInCSharp.sln
SendPostMessageInCSharp
...........\AssemblyInfo.cs
...........\bin
...........\...\Release
...........\...\.......\IPCinCSharp.exe
...........\Form1ICS.cs
...........\Form1ICS.resx
...........\IPCinCSharp.csproj
...........\IPCinCSharp.csproj.user
...........\IPCinCSharp.sln
...........\WINUSER_H
...........\.........\WinUser.h
IPCinCSharp
SendPostMessageInCSharp\App.ico
.......................\AssemblyInfo.cs
.......................\bin
.......................\...\Release
.......................\...\.......\SendPostMessageInCSharp.exe
.......................\Form1SPMC.cs
.......................\Form1SPMC.resx
.......................\SendPostMessageInCSharp.csproj
.......................\SendPostMessageInCSharp.csproj.user
.......................\SendPostMessageInCSharp.sln
SendPostMessageInCSharp