For the client which has no VSIP installed, you have to request a PLK.
(www.vsipdev.com).

The setup for VSIP package is pretty streghtforward. The
Package::UpdateRegistry update teh registry, so you only need to set the
'register' to 'vsdrpCOMSelfReg' in the setup project fro the package dll.

MS recommand to write the registry entry in the setup package not in the
Package::UpdateRegistry. Once you success in the self-register way, you
can easily change to the MS prefer way.

Mike

Hi Patrick,

Just to be clear, the client machine also needs to have a VS .Net 2003
installation on it. Just having the .NET 2003 SDK isn't going to work. You
need the Visual Studio IDE for the package to load against. I'm guessing
this is not the case though :-)

Michael's suggestion is a good one. First, ensure the package is registered
properly, by using the VSIPRegPkg utility. One you've verified that this
works (by running DevEnv /noVSIP). Run VSIPRegPkg again with the /regfile
or /vrgfile option and this will show you the registry keys your installer
will need to set up.

Note, be sure to add the RegisterLoadKey attribute to your package, so that
it points to the string table resource that contains your PLK. Also, you
want to be careful with the inproc32 key. The path to mscoree.dll is
different on Win2K .vs XP for example. Your installer will need to
determine where the windows directory is, so that you can correctly set the
path to mscoree.dll.

Sincerely,
Ed Dore [MSFT]

This post is 'AS IS' with no warranties, and confers no rights.