Re: Internationalization
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Sun, 30 Dec 2007 10:14:48 -0500
That's yet a different issue. I've avoided, except in one case, being an automation
server. But I've written several programs that use automation, and the choice of MFC vs.
ActiveX is not one the programmer necessarily has control over. For example, one program
I delivered used a graphics support package, which only had an ActiveX interface, which we
had to use. OleDB database interface is clearly an OLE interface. I've used a
communications library that only exported ActiveX interfaces. About one in five of my
projects requires that I talk to an ActiveX interface of some third-party vendor
preselected by my clients. So my preference doesn't enter the picture; if I'm using the
embedded-system-download-interface for brand X embedded processor boards, then I have to
use the brand X ActiveX control to interface to it. If I'm using the Brand Y grid
control, it's ActiveX. The brand Z graphics package, ActiveX. And so on. While I don't
create these controls (I prefer to use MFC controls when I have to create them), I don't
have a choice, because the customer has chosen the product and I am to build an
application that interfaces to it. And there have been bugs in the ActiveX support DLLs
which generated support calls; I have a colleague who is an ActiveX guru, so when I see
certain problems, I sometimes send him email, and get responses of the form "That problem
was true of the version n.m release of <name of OLE DLL here>, and was fixed in later
versions". We go back to the customer, and indeed, they have that version installed. We
tell them to install the appropriate updates, and the problem goes away. This was
certainly true in Win2K, but I've not seen or heard of it in XP.
joe
On Sun, 30 Dec 2007 06:33:40 GMT, "David Ching" <dc@xxxxxxxxxxxxxxxxxxxxxx> wrote:
"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in messageJoseph M. Newcomer [MVP]
news:ui9en3dj6h2p7hbtgmo3igr4ftolid4a9n@xxxxxxxxxx
Any app that uses ActiveX controls would use automation, and that's more
and more.
No, I don't think so. By "automation" I mean OLE Automation which means
your app is an Automation server, which has nothing to do with whether or
not it consumes ActiveX controls, say a custom control. Most MFC
programmers prefer using MFC controls instead of ActiveX controls, so while
an MFC app can offer an Automation interface, it by no means indicates
whether it uses ActiveX controls or not. But both being an Automation
server and consuming ActiveX controls requires use of OLE32.DLL...
I'm
somewhat of an anomaly because I don't create ActiveX controls (just a
decision on my part
where I was going to concentrate my efforts). But a lot of what I get
uses automation,
and a lot of third-party code is delivered only as ActiveX code (I don't
know what procexp
does, but it clearly uses OLE32.DLL).
... and just because an app uses OLE32.DLL does not mean you have to redist
OLE32.DLL! So what difference is it whether an app uses OLE32.DLL or not?
You never redist OLE32.DLL anyway (or at least I never have heard of doing
so, other than the VC6 on Win95 Gold case).
I just can't get excited about the issue of the MFC DLL; I've delivered so
many projects
using it that I can't even recall all of them (real projects, not just the
toys on my Web
site), and we've just never had any problems when they're installed with
an installer. I
generally don't get involved in the actual creation of the setup, because
each client has
their "standard look & feel" installer they prefer.
If you've not created the Setup, then of I would think you would NOT hear of
any bugs in the deployment since the writer of the Setup typically gets
those. And there are a lot of them, especially with the new way of
redisting the C runtime and MFC DLL's from VS2005, and ensuring you redist
SP1 or not.
-- David
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- Follow-Ups:
- Re: Internationalization
- From: David Ching
- Re: Internationalization
- References:
- Re: Internationalization
- From: Pete Delgado
- Re: Internationalization
- From: Thomas Mooney
- Re: Internationalization
- From: Joseph M . Newcomer
- Re: Internationalization
- From: David Ching
- Re: Internationalization
- From: Joseph M . Newcomer
- Re: Internationalization
- From: David Ching
- Re: Internationalization
- From: Joseph M . Newcomer
- Re: Internationalization
- From: David Ching
- Re: Internationalization
- From: Joseph M . Newcomer
- Re: Internationalization
- From: David Ching
- Re: Internationalization
- Prev by Date: Re: String length
- Next by Date: Re: String length
- Previous by thread: Re: Internationalization
- Next by thread: Re: Internationalization
- Index(es):
Relevant Pages
|
Loading