Displaying 4 results from an estimated 4 matches for "dont_resolve_dll_references".
2007 Aug 23
0
Bug in win32-eventlog, grabbing descriptions
Hi all,
I know that once upon a time I said that we shouldn''t use
DONT_RESOLVE_DLL_REFERENCES (line 698), but it appears that this was
wrong headed thinking for win32-eventlog.
A couple of folks have complained that they couldn''t get descriptions
for event records in some cases, and I have a strong feeling that''s the
culprit.
Can anyone see a downside to using DONT_RE...
2005 Feb 14
8
DONT_RESOLVE_DLL_REFERENCES info
For future reference, it looks like we should avoid
DONT_RESOLVE_DLL_REFERENCES in any extensions.
http://weblogs.asp.net/oldnewthing/archive/2005/02/14/372266.aspx
Regards,
Dan
2007 Dec 05
21
Fwd: win32/process problem
Any ideas?
---------- Forwarded message ----------
From: Christian Kerth <christian.ke... at dynamicmedia.at>
Date: Dec 5, 8:28 am
Subject: win32/process problem
To: comp.lang.ruby
I have an application that consists of serveral independent parts.
I want to use the Windows Process API to spawn the different
processes.
e.g.
require ''rubygems''
require
2004 Oct 14
0
More on the description problem in win32-eventlog
I think I''ve narrowed it down to this call in eventlog.h
hModule = LoadLibraryEx(
szExeFilePath,
0,
DONT_RESOLVE_DLL_REFERENCES
);
In all cases where the description is returning nil instead of actual text,
this appears to be the culprit. I''ll do some more research. In the
meantime, ideas welcome. :)
Dan