In the past I have written ATL COM dlls with visual studio 6 using connection points to communicate with VB6 clients. The dll has a worker thread that fires the connection point back to the Windows XP VB6 client app. When I port this to VS2005 and the client is now .NET on the CE 5.0 platform the connection point does not fire in the client app.
I know the connection point works because I have fired it from the dll and the client gets it. But when the worker thread does it the client does not see it. Any idea as to what the difference could be that is making this fail?
The Windows Firewall provides an important layer of protection and a rich interface to configure it. Unfortunately, it lacks item level filtering. This article details my process of implementing firewall-as-code to reduce GPO bloat.
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel.
Part 1 of this series discussed basic error handling code using VBA.