how to create tlb w/o administrator right on vista

  • Thread starter Thread starter GS
  • Start date Start date
G

GS

How can I create an tlb file from an .net dll on vista w/o admin privilege?.
I am using vs 2008 fw 3.5.


I can easily create the required reg file with regasm
 
I did try
regasm my.dll /t:my.tlb
and I was "rewarded" with
Microsoft (R) .NET Framework Assembly Registration Utility 2.0.50727.3053
Copyright (C) Microsoft Corporation 1998-2004. All rights reserved.

RegAsm : error RA0000 : An error occurred while writing the registration
information to the registry. You must have administrative credentials to
perform this task. Contact your system administrator for assistance

I hope there is some sort uac setting I can use to set the pseudo registry
just for the ID so I can proceed as non admin w/o affecting any other users.
on the pc. I don't want to install on the GAC


I just want the tlb file don't care if I have to do reg import later
 
GS said:
I did try
regasm my.dll /t:my.tlb
and I was "rewarded" with
Microsoft (R) .NET Framework Assembly Registration Utility 2.0.50727.3053
Copyright (C) Microsoft Corporation 1998-2004. All rights reserved.

RegAsm : error RA0000 : An error occurred while writing the registration
information to the registry. You must have administrative credentials to
perform this task. Contact your system administrator for assistance

I hope there is some sort uac setting I can use to set the pseudo
registry
just for the ID so I can proceed as non admin w/o affecting any other
users.
on the pc. I don't want to install on the GAC


I just want the tlb file don't care if I have to do reg import later
Click to expand...


I didn't realize regasm /tlb actually registered the objects. The artical
also discuss the difference between regasm /tlb and tlbexp. You could try
tlbexp, which does not register anything. Of course, if you have admin
rights anywhere, you could generate the tlb there, and copy it whereever you
need it.

Generally developers do need admin rights. I saw your post on the other
group. I agree that there are reasons for limiting priveledges, and the
company that I work at is struggling with this issue. Unfortunately they
don't have it right yet, and to accomplish anything useful we need to use
our "admin enabled" accounts.
 
registration free side by side use of com is great for .net applications.

However, there is still legacy applications requiring this COM class to
enhance its ability to handle information for users. Unfortunately these
complex legacy application are not likely to be rewritten due to high cost
of rewrite and risk their stability and user satisfaction.
 
thank you, I will give tlbexp a shot.


I sure hope ms will get it right sometime soon: in the end deployment we or
application admin do need the admin right. however we should be to do most
of development and testing w/o admin right so we can easily tear down and
redo the development w/o restoring image for the enter OS. just use a
different local ID for different application project if need to. setting
up user profile from user profile restore is a lot quicker than os image;
also quick to back up a profile frequently


it will certainly make life easier if ms vs allow us in compile/build option
to deploy as local user vs presumed GAC for COM class.
 
tlbexp worked with a bit warning
TlbExp : warning TX0000 : When cross-compiling, all type library references
should be included on the command line to ensure the correct bit-specific
type libraries are loaded.

I will see what else I have to put in on the command line for the required
the references. is core something one of them?

I did get some good result from testing the com class with vbs though one
function did not return any string - or the string vbs could use. I did not
specifically marshal the string type in the com component but it worked
before on win xp. the function prototype is
public function myfcn() As string

return "some long lines of string"
end function

the console print function did not worked either

GS said:
thank you, I will give tlbexp a shot.


I sure hope ms will get it right sometime soon: in the end deployment we or
application admin do need the admin right. however we should be to do most
of development and testing w/o admin right so we can easily tear down and
redo the development w/o restoring image for the enter OS. just use a
different local ID for different application project if need to. setting
up user profile from user profile restore is a lot quicker than os image;
also quick to back up a profile frequently


it will certainly make life easier if ms vs allow us in compile/build option
to deploy as local user vs presumed GAC for COM class.
Click to expand...
 
Back
Top