create com object and register trouble

[GS]

I tried a build com class from vs 2008 on vista ultimate form a power user.
despite
I have access to the files, folders,
and use administrator explicitly created the appropriate CLS ID key and
progid key as well as granting me full access on these keys
I get can not register ....... can not access registry .....

consequently no application nor vbs can create the com object.


What is the proper way of setting up the environment for me as power user to
create /build com object

I'm using net.3.5 sp1. vista ultimate is fully patched

 

[Michel Posseth [MCP]]

AFAIK a developer should be at least a local admin

imho a company who makes there software developers lower level users in
there domain is not taking there devlopers role serious .

Michel

 

[GS]

a developer imho should not be using local admin all the time.

After all he has to do his own other task, email, web research....,
communicate with others. we don't have the luxury of total secure
cooperating internet community - it has been spoiled by a few highly
organized criminals, cyber space terrorist, and some espionage.

developers may be smart and savvy but they are also under intense deadline
pressure and may even have to work long hours at times and that is the time
someone becomes vulnerable to security fault pas

 

[Michel Posseth [MCP]]

GS

<SNIP>
What is the proper way of setting up the environment for me as power user to
create /build com object

</SNIP>

a developer should be a local admin to do his job properly

HTH

Michel

 

[GS]

hey, I was just power user and was able to do my job on XP. I only need the
admin ID to allow me access to certain registry key. Certainly admin
power user is convenient but now the supposedly more secure Vista requiring
Admin to be developer is security regressive!

I can't believe this need of admin powered developer is the intend of Vista

There must a way to setup a developer is do his job of application
development, testing as power or standard user. I will accept the limitation
that I may need elevated privilege when and only when I do final production
deployment to users