Re: Register DLL Question
- From: "boaz" <nospam@xxxxxxxxx>
- Date: Wed, 19 Oct 2005 13:25:26 -0700
I will say about 50% like my products and 10% doesn't like it, and about 40%
doesn't care.
And I don't worry about intallation problem. Many of my customers have a
big IT department. Many of them know what to do. Many of them don't. The
real problem is that "updating" (of any kind) for them is a big deal.
I actually was thinking to switch to Delphi. But the same problem came
back. I couldn't sell the stuffs if I told them it was written in Delphi.
I had to tell them that it was Microsoft and MacroMedia, and craps like
that.. So, the guys who were resposible for purchasing knew my craps were
good craps. ;-)
So anyway... according to "Someone", using ".local" may (and just may) not
do the trick. I look at my projects, I don't have any custome dll at all.
And the third party OCXs don't have any dependency (according to them).
So... back to the topic... do I good to go not to register the DLL/OCX? or
back to the original topic. Do I have to register OCX/DLL in order for my
program to work?
>
> (does this mean that YOUR s/w is crap because it's not from a well-known
> brand name ? (going by your logic) i'm sure you would take offense to
> that.)
.
- Follow-Ups:
- Re: Register DLL Question
- From: Someone
- OT: Re: Register DLL Question
- From: DanS
- Re: Register DLL Question
- References:
- Register DLL Question
- From: boaz
- Re: Register DLL Question
- From: Ralph
- Re: Register DLL Question
- From: Jim Carlock
- Re: Register DLL Question
- From: boaz
- Re: Register DLL Question
- From: DanS
- Register DLL Question
- Prev by Date: Re: Register DLL Question
- Next by Date: OT: Re: Register DLL Question
- Previous by thread: Re: Register DLL Question
- Next by thread: OT: Re: Register DLL Question
- Index(es):
Relevant Pages
|