regasm issue, VB.net com dll

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

jroozee@gmail.com - 31 Aug 2005 22:24 GMT

I have created a DLL using VB.net for com interopt for use within my
VB6 application. It works fine on my machine - I run the regasm, it
registered and drag the dll in to the assembley folder.

However, when I distribute the DLL to a end-user machine witht the .NET
1.1 framework I have some issues.

Obviously, the COM isnt registered so I get a ActiveX can't crate
obkjct error in my VB6 app. So, I go and try to run regasm to register
it.. but when I run regasm, it's not a reconized interneal or external
command in windows XP. RegAsm is in the .NET framework folder, so I
assume the windows PATH enviroment variable is not pointing to this
path.

So, how do I distributee and regasm a dll file? How do I determine the
path the regasm?

Thanks
Jason Roozee

Reply to this Message

Damien - 01 Sep 2005 08:37 GMT

> I have created a DLL using VB.net for com interopt for use within my
> VB6 application. It works fine on my machine - I run the regasm, it
[quoted text clipped - 15 lines]
> Thanks
> Jason Roozee

What are you using to distribute your DLL? If you're not using any
installer, the easiest way is to add an installer project to your
Solution. It should then 1) Pick up dependancies, and 2) There are
options to automatically register your component upon installation (and
to place in GAC, etc)

If you're using another installer package (e.g. InstallShield), I
believe that these, similarly, offer registration capabilities.

At our place, we use a slightly older version of InstallShield to
install our VB6 programs. Hopefully, once everything is being done in
.NET, we'll move to just using installer projects. There are things
they cannot do, but it's not been a serious limitation so far (One
limitation that a lot of people seem to complain about is that you
cannot place custom actions within a GAC installed DLL, since GAC
installation occurs later - but if you plan for that beforehand and
place custom actions in another DLL, it shouldn't cause too much
heartache. Wow, what a lot of sentence within parenthesis).

Damien

Reply to this Message

jroozee@gmail.com - 01 Sep 2005 17:23 GMT

That's great and all but:
I have update script applet that executes before the main application
runs. It downloads and installs new updates automatically, w/o user
intervention. This works great for VB6 COM DLL's as they jkust need to
be installed then registered using regsvr32 -- how can I automate the
same process for my VB.NET COM DLL and keep it seamless w/o user
interaction. The Setup Installer in .NET is a crappy microsoft
installer that requires user interaction.

Jason

Reply to this Message

jroozee@gmail.com - 01 Sep 2005 19:10 GMT

Well, what I've done is distibute regasm and gacutl in my update applet
script. Then, using a bat file, i script the regasm and gacutl to
execute for the dell. It seems to work, but I'm not sure if I should be
distributing the regasm/gacutl like this.

Jason

Reply to this Message

Damien - 02 Sep 2005 07:42 GMT

> That's great and all but:
> I have update script applet that executes before the main application
[quoted text clipped - 6 lines]
>
> Jason

1) It doesn't require user interaction if you run msiexec with the
/quiet flag, but okay, this may be overkill for your application.

2) gacutil and regasm can always be located under the .NET framework
directory. i.e. under %windir%\Microsoft.NET\Framework\<.NET version>,
where <.NET version> is one of "v1.0.3705", "v1.1.4322", or (at
present) "v2.0.50215", for frameworks 1.0, 1.1 and 2.0 respectively.

That way you don't have to distribute them yourself (which the EULA
prohibits you from doing, I believe)

Out of curiosity, how do you update the script applet if it's that that
needs updating?

HTH,

Damien

Reply to this Message

regasm issue, VB.net com dll

Free Magazines