Fooling Around // Software Production Line

Does it make sense that __event __interface may still only use dispinterface defined in this module and not imported?

#import “libid:…” no_namespace raw_interfaces_only raw_dispinterfaces

[
coclass,
event_source(com),
default(IFoo, _FooEvents),
...
]
class ATL_NO_VTABLE CFoo :
public IFoo
{
public:

__event __interface _FooEvents; // Imported using #import
…

OK, in Visual Studio .NET 2002 the attribute provider only appeared first, this could be a problem missed while developing the stuff. 2003 version did not fix the issue. In 2005 it’s still the problem!

error C3706: ‘_FooEvents’: must be a COM interface to fire COM events
error C3335: ‘_FooEvents’: There can be at most one default interface for a coclass ‘CFoo’

Read more »

If you own a Magellan eXplorist and speak Spanish, this post might appear to be helpful Modificar la presentación de mapas IMI para explorist (check the bottom of the page).

I came across released service packs for Visual Studio .NET, 2003 and 2005:

• Microsoft® Visual Studio® .NETâ„¢ 2003 Service Pack 1
• Microsoft® Visual Studio® 2005 Team Suite Service Pack 1

and was surprised, in a good way, that Microsoft finally released an update to fix at least some of the bugs. Some of the bugs were multiple times mentioned on the microsoft.public.vc.atl newsgroup so one would assume they are well know to be fixed in the service pack.

The sad news bugs are still here… For example, regular expressions nasty bug or singleton factory unlock bug are still here.

Visual Studio .NET 2005  service pack failed to install at all, keeps freezing while trying to install…

IDE bugs are also passing through the versions of software:

What’s new in this build?

• Fixed:VersionInfo strings were saved as binary value (ass opposed to text value) and thus were unrecognized by some applications, including VerQueryValue API
• Updated: Setup includes extras (license, blog shortcut etc.)

Read more »

Starting Visual Studio .NET version 2003 (2002?) ATL offered new tracing macros ATLTRACE/ATLTRACE2 which are quite convenient and flexible to generate debug output and, what is important, come with ATL debug API which allows to adjust output settings on runtime using ATL/MFC Trace Tool.

The problem however appeared to be that ATL debug API does not seem to support printing function names, although trace tools shows checbox “Category & Function Names”. I am solving this shortage.

Read more »

What’s new in this build?

• Fixed: Dialog template update would fail on an attempt to set DS_FIXEDSYS or DS_SETFONT flags if none were previously set, as well as unset both flags if any of them were presiously set; This is required because dialog template structre has optional fields defining font which has to be added/removed with the style change
• New: Dialog.ItemStyle property provides access to dialog template control’s styles, for instance, to set/unset WS_VISIBLE style

Read more »

In continuation to recently posted “Smart ATL/WTL combo box and list view classes to cast and optionally manage typed control item data”, list box and tree view classes aware of typed item control data.

Read more »