Re: VS.Net 2005: Uses regsvr32 with undocumented options and fails to register
- From: "David F" <David-White@xxxxxxxxxxxxx>
- Date: Mon, 11 Jul 2005 16:59:27 -0700
I think I can understand and almost identify with several of the responders
here.
However, I think they all missed all key points of the chain of event I went
through.
I will list it in the chronological (which is a logical one in this case
too) order:
1. I get a VS2005. I am suppose to install it in admin mode and use it in
User mode,
like any other SW product. And it is also fine if there is, as is the
case here, a special
"Debugger User" mode. Not only is this how I suppose to work (even by MS'
strong recomendations) but no information that come with the product
suggest that
some parts of it would not work w/o full admin rights.
Right at this point I can say end of story, no ifs no buts.
Personaly I believe that the product can and should be designed w/o
requiring full
admin rights for any of its parts. But if the designers of the product
did not or
could not achieve that for whatever reason, the product's documentaion
should
reflect properly and accurately the COMPLETE requirements.
There is no need to get into any farther detail to conclude that in the
case of a negative
answer to BOTH of these options, there is a serious bug in the product.
2. Independently of anything else, the person who wrote the script that
checks the results of
the regsvr32.exe operation that follows automatically the linking phase,
did an extremely
unprofessional and lousy job, causing so and so many users to waste so
much time.
. He firstly checked only errorlevel 1. This masks all other possible error
reporting levels above 1.
Indeed, in this case, the errorlevel was 5.
Would he check properly and report accordingly, the time damage resulting
from (1)
would be significantly reduced.
This lousy job is of course worse than a bug.
Also, that developer should not have used /c option in W2K. This is a
small bug.
3. Whatever the errors are, they should be saying exactly the root cause of
a problem.
Reporting useless error codes, let alone w/o documenting them, has long
been declared
as sins. No excuses for providing a cryptic number instead of a
complete full report
with a textual description of the EXACT ROOT cause of the problem.
This lousy job is of course worse than a bug
David
--------
Albert Einstein: "Two things are infinite: the universe and human
stupidity; and I'm not sure about the universe."
Me poor David think that Einstein new what he was talking about...
<adebaene@xxxxxxxxxxxxxxxx> wrote in message
news:1121068808.378198.323700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
David F a écrit :
> Finally, I found the problem.
> Unbelievably, I stasrted to suspect that it "smell" like an access right
> problem.
> I always work on my W2K according to MS' recommendation (sometimes they
are
> right...),
> that is, in User (not even Powered User) mode. I also added "VS Developer"
> and "Debugger" access rights. That should have worked by definition.
Should
> it?
COM object registration requires administrative privileges.
> So to add pain to this access right bug,
It is not a bug! Would you like to have everybody able to install any
COM component on your machine?
Arnaud
MVP - VC
.
- Follow-Ups:
- References:
- VS.Net 2005: Uses regsvr32 with undocumented options and fails to register
- From: David F
- Re: VS.Net 2005: Uses regsvr32 with undocumented options and fails to register
- From: Heinz Ozwirk
- Re: VS.Net 2005: Uses regsvr32 with undocumented options and fails to register
- From: David F
- Re: VS.Net 2005: Uses regsvr32 with undocumented options and fails to register
- From: adebaene
- VS.Net 2005: Uses regsvr32 with undocumented options and fails to register
- Prev by Date: Guidelines when using templated classes in DLL's
- Next by Date: RE: a template problem
- Previous by thread: Re: VS.Net 2005: Uses regsvr32 with undocumented options and fails to register
- Next by thread: Re: VS.Net 2005: Uses regsvr32 with undocumented options and fails to register
- Index(es):
Relevant Pages
|
Loading