I'm receiving an error message when trying to reference my dll I've just
built and installed on my development workstation. Where can I find the
proper procedures for developing and then conducting a user test of
installation of the dll on the same machine?
Do I have to unregister the com library first and then install or does the
setup installer take care of that for me?
--

thx
-jsh

Re: Error while installing library by Richard

Richard
Fri Oct 15 10:34:10 CDT 2004

What error are you getting?
Are you trying to use the component from VB/Excel/script? You don't need to register .NET assemblies to be able to use them normally

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

I'm receiving an error message when trying to reference my dll I've just
built and installed on my development workstation. Where can I find the
proper procedures for developing and then conducting a user test of
installation of the dll on the same machine?
Do I have to unregister the com library first and then install or does the
setup installer take care of that for me?
--

thx
-jsh



Re: Error while installing library by Girish

Girish
Fri Oct 15 14:23:33 CDT 2004

What are you building? Is it a COM object? What errors are you seeing?

--
Girish Bharadwaj
http://msmvps.com/gbvb
"J Holsinger" <jsh02_nova@hotmail.com> wrote in message
news:eZTG3fssEHA.2536@TK2MSFTNGP11.phx.gbl...
> I'm receiving an error message when trying to reference my dll I've just
> built and installed on my development workstation. Where can I find the
> proper procedures for developing and then conducting a user test of
> installation of the dll on the same machine?
> Do I have to unregister the com library first and then install or does the
> setup installer take care of that for me?
> --
>
> thx
> -jsh
>
>



Re: Error while installing library by J

J
Mon Oct 18 15:33:35 CDT 2004

I was getting an error Object null reference even though I had a reference
to my dll. When I used '<Assembly: PrimaryInteropAssembly(1, 0)>' in my
assembly info file my problem went away.

--

thx
-jsh