office-gobmx/cli_ure/source/uno_bridge
Kurt Zenker 8e6e78d439 INTEGRATION: CWS jl104 (1.4.6); FILE MERGED
2008/06/18 14:25:02 jl 1.4.6.1: #i88078#  cli_ure moved to URE, therefore it can only build ure types, tests moved to testtools
2008-06-25 11:14:48 +00:00
..
bridge_exports.map
cli_base.h
cli_bridge.cxx
cli_bridge.h INTEGRATION: CWS jl104 (1.3.4); FILE MERGED 2008-06-25 11:14:07 +00:00
cli_data.cxx INTEGRATION: CWS jl104 (1.3.4); FILE MERGED 2008-06-25 11:14:07 +00:00
cli_environment.cxx
cli_environment.h
cli_proxy.cxx INTEGRATION: CWS jl104 (1.3.4); FILE MERGED 2008-06-25 11:14:07 +00:00
cli_proxy.h
cli_uno.cxx INTEGRATION: CWS jl104 (1.3.4); FILE MERGED 2008-06-25 11:14:28 +00:00
makefile.mk INTEGRATION: CWS jl104 (1.4.6); FILE MERGED 2008-06-25 11:14:48 +00:00
README.txt

Because of the LoaderLock bug in .NET Framework 1.0 and 1.1 the cli_uno.dll is linked 
with the /NOENTRY switch, which prevent that the C-runtime is initialized when loading 
the dll.

Also I removed all static c++ objects which need construction by the CRT, 
exception handling seems to need an initialised CRT. Therefore
I added CRT initialization code in  uno_initEnvironment (cli_bridge.cxx)
However there is no deinitialization done because bridge libraries remain 
in memory until the process dies. There is actually no good place where 
this had to be called. If we would do that we would have to implement that
the bridge can be disposed.


Sell also:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vcconmixeddllloadingproblem.asp
http://support.microsoft.com/?id=814472
http://www.ddj.com/dept/windows/184416689
http://blogs.msdn.com/cbrumme/archive/2003/08/20/51504.aspx
http://msdn2.microsoft.com/en-US/library/ms172219.aspx