＋设为首页 ＋添加到收藏夹
delphi 8 for .net assemblies; packages and libraries 【程序编程相关:最近刚为公司完成的一款监视的小工具软件!】
【推荐阅读:关于MIDAS的安全问题的解决方案】in this article, bob swart will explain what .net assemblies are, how we can use them in delphi 8 for .net applications, and especially how we can make them ourselves (it actually turns out that there is more than one way, and even some special way to use some of them in win32 applications).dlls and .net assemblies 【扩展信息:2004.11.30.Managing 】
the world of windows application development introduced the dll - dynamic link library. a dll can contain a number of functions that can be called from an application that loads the dll (statically or dynamically). the windows api consists mainly of dlls. these dlls were written in c or c++, and came with a header file that described the interface of the dll. for pascal and delphi developers, it was not easy to use the dll if you didnt have a dll import unit. and back in 1989 i released headconv - my first c dll header converter, which is now available as free tool under management of the delphi-jedi darth project. the delphi jedi project itself was founded to produce delphi import units for c dll header files - a tedious job, but well appreciated by all delphi developers who ever needed to use a c dll header file. why am i telling you this? because the world has changed. the .net framework is taking over the windows world, and the dll is being replaced by a new kind of library, called the .net assembly. .net assemblies are more powerful than dlls in a number of ways. first of all, where a dll can only export functions (and not classes), the .net assembly can define classes that can be used and extended by other .net assemblies or applications. another significant benefit is the fact that the .net framework is language neutral. as a consequence, a .net assembly written in language x can be used by any language, including delphi 8 for .net. no more c dll header conversions ever!add references
... 下一页