Problem with registering Vb Dll

[Catherine Jones]

I need to register a Vb DLL under restricted acess privilages
please provide me a solution

Regards and thanks

 

[Herfried K. Wagner [MVP]]

I need to register a Vb DLL under restricted acess privilages
please provide me a solution

Please include only groups to your posts which are related to the topic!

 

[Jose Caliente]

is your middle name Zeta, by any chance?

Please include only groups to your posts which are related to the topic!

 

[Armin Zingler]

is your middle name Zeta, by any chance?

Herfried K. Zeta Wagner??

;-)

 

[Jose Caliente]

I was asking Catherine Jones

Herfried K. Zeta Wagner??

;-)

 

[Herfried K. Wagner [MVP]]

is your middle name Zeta, by any chance?

No, not mine...

 

[Herfried K. Wagner [MVP]]

Herfried K. Zeta Wagner??

;-)

ROTFL

 

[Sueffel]

Don't mind these guys LMAO
There is some solutions, I'll leave it up to you to decide which is better
or not...

1) pay $$$ to Desiware and export the functions out of the VB6/.NET DLL's
and use API declerations to call the DLL's, no Registration needed.
2) Rewrite the DLL's in C++, exporting the functions and calling them using
API declerations.
3) {Not recommended, but hey, sometimes...} If you are under a domained
environemnt, allow the users access to the registry, or certian keys, then
the issue goes away.
4) Rewrite the DLL's in VB.NET, no registration needed.

Otherwise, you can ask these guys, I've been banging my head against the
walls over this one for some time, and #3 is my solution, but in-process on
#4.

HTH
Sueffel

 

[Joe \Nuke Me Xemu\ Foster]

I need to register a Vb DLL under restricted acess privilages
please provide me a solution

This sounds like an organizational problem. In effect, you've been
required to run a marathon, but you must wear dancing clogs instead
of running shoes. You won't even be able to properly update the VB
run-times, and God help you if you need to install MDAC, MSDE, or
Jet!

 

[Joseph Geretz]

But ultimately, Joe Foster is correct. This is an organizational /
administrative problem. As such, this will require an organizational /
administrative solution. Setting up such a scenario and then asking your
development department to solve it is foolhardy IMO. Some of what you
propose is cumbersome at best and changes the whole strategy of VB6/ActiveX
development. How are you going to deploy user controls? Third party DLLs? At
worst, some of what you propose is not even possible, if write access is
restricted to the user login.

If domain administration is going to take control of user workstations in
this manner, then they need to take control of software deployments as well.
This means developers need to release MSI installs and domain admins need to
set up group policies to push these products out to the users' workstation.

- Joe Geretz -

 

[Kelly G.]

Hi

Thanks for the help.
Well actually the information was not enough ,I think the problem was due to
me not providing the complete details

I building a MSI using Vs.net ,One of the Dll's is Vb Component ( A shim
component basically) ,
Our application has to install both with Administrative privialges and
restricted user privilages .

The actual problem is that of registering this dll ,Since it tries to
register under Hkey_local_machine ,But under restricted user privilages we
do not have access to Hkey_local_machine so we have to register under
Hkey_Current_user.
I am trying to export the registry of the DLL and add it to my setup so
that it can be exported to the target machine but i am still not been able
to get it to work

Please do provide me with more information on this. This is urgent :-(

Thanks once again

Regards
Kelly

 

[Peter Young]

Hi

Thanks for the help.
Well actually the information was not enough ,I think the problem was due to
me not providing the complete details

I building a MSI using Vs.net ,One of the Dll's is Vb Component ( A shim
component basically) ,
Our application has to install both with Administrative privialges and
restricted user privilages .

The actual problem is that of registering this dll ,Since it tries to
register under Hkey_local_machine ,But under restricted user privilages we
do not have access to Hkey_local_machine so we have to register under
Hkey_Current_user.

A VB DLL is a COM component. COM components require entries in HKEY_LOCAL_MACHINE so that code that needs to instantiate
the component can find the component. Using HKEY_CURRENT_USER is not an option unless you are targeting only Win2K and
up.

If this is the only file in the entire installation that requires registration I'll be surprised. But if it is, then you
have the option of rewriting the DLL's calling code in order to avoid the registration requirement altogether. This is
not a trivial task, but it is possible.

It's also possible to write your own DllRegisterServer and DllUnregisterServer routines using a third-party tool, but
that also is not trivial.

The correct answer has already been stated. The install program requires temporary rights to portions of the Registry
that are normally off-limits. This is an administrative issue, not a programmatic one.

-Peter

 

[David G]

When does VS.Net 2004 Whidbey come out ?
I would like to buy it !

Will it also allow a developer to upgrade from vb6 pro ?
And what proff do i need since all I have is the cd, the case and the
original box . Is that enough to qualify for an upgrade ? I must have lost
the receipt years ago.

Thanks

 

[Herfried K. Wagner [MVP]]

When does VS.Net 2004 Whidbey come out ?
I would like to buy it !

AFAIS Winter 2004 or Spring 2005.

Will it also allow a developer to upgrade from vb6 pro ?
And what proff do i need since all I have is the cd, the case and the
original box . Is that enough to qualify for an upgrade ? I must have lost
the receipt years ago.

Sorry, I don't know that.

Please don't make excessive use of X-posts.

 

[Jeff Johnson [MVP: VB]]

When does VS.Net 2004 Whidbey come out ?

When it DOES come out and you have questions, please note below:

Please ask .NET questions in newsgroups with "dotnet" in their names. The
*.vb.* groups are for VB6 and earlier. If you don't see the *.dotnet.*
groups on your news server, connect directly to the Microsoft server:
msnews.microsoft.com.

 

[David G]

This a dotnet group microsoft.public.dotnet.languages.vb

 

[james]

David, look at the TO: line, it is cross-posted to a ton of newsgroups.
james

 

[Bob O`Bob]

This a dotnet group microsoft.public.dotnet.languages.vb

No, this is SEVEN newsgroups all at once, in about FIVE of which it was off-topic.
It might behoove you to learn to understand your tools (e.g., outlook express)
before you spout off AS IF you understood what people were talking about.

 

[David G]

Well the message is not posted in those groups only in this one.

 

[Al Reid]

It was until your post trimmed it down to
microsoft.public.dotnet.general,microsoft.public.dotnet.languages.vb.