> We are using VSIP 2003 Beta 1. I was informed by our developers is that it
> was not possible. However, I have read about the VSIPRegPkg.exe file and
[quoted text clipped - 7 lines]
> keys during self registration. I am sure that this is against Microsoft's
> philosophy about setups.

Signature
Bob Arnson :: Visual Studio Extensibility User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
Hi Bob,
Good to find you around. :-)
It is very unfortunate that VSIP 2003 does not support getting this out of
the registration process. I would love to consume the RGS file and create a
REG file that I can import or WIXify it to a fragment. But the RGS file is
strewn with tons of substitution strings. I am really stuck with this one.
:-(((
Regards,
Vagmi
> > We are using VSIP 2003 Beta 1. I was informed by our developers is that it
> > was not possible. However, I have read about the VSIPRegPkg.exe file and
[quoted text clipped - 15 lines]
> write .reg files (among others) that would be easy to WiX-ify. (I believe
> someone on one of the WiX lists wrote that tool already.)
"Ed Dore [MSFT]" - 24 Feb 2005 23:43 GMT
I'd like to see this as well.
I suspect the reason why we still have self registering components is due
mostly for convenience sake. It's nice to be able to rebuild and test the
package without having to explicity install it. And the ability to register
the package against a particular test environment (aka /rootSuffix) is
pretty convenient. But when it comes to building a setup/installation
utility for the package, this does become a headache.
For managed packages though, this step is pretty trivial. Check out the
/regfile and /vrgfile options supported by the vsipregpkg.exe utility.
For what it's worth, I've sent along a feature request to the ATL team, as
I don't see how we could do this outside of ATL, as the .RGS files contain
replaceable parameters that you don't actually know how to resolve until
the component's actually installed and DllRegisterServer and/or
DllUnregisterServer is called. Maybe just keeping the replacement params in
there would suffice for our purposes though. An RGS2REG.exe utility
perhaps?
Sincerely,
Ed Dore [MSFT]
This post is 'AS IS' with no warranties, and confers no rights.
Bob Arnson [MSFT] - 26 Feb 2005 07:40 GMT
> It is very unfortunate that VSIP 2003 does not support getting this out of
> the registration process. I would love to consume the RGS file and create
> a
> REG file that I can import or WIXify it to a fragment. But the RGS file is
> strewn with tons of substitution strings. I am really stuck with this one.
> :-(((
The %strings% in the .rgs file are all either static or defined in your
vspkg.cpp file (when created by the VSPackage wizard). It's doable, just not
fun. The .rgs format is even spec'd out:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_at
l_understanding_parse_trees.asp.
You'd have to pass in the replaceable parameters as command-line
arguments...Hmmm...

Signature
Bob Arnson :: Visual Studio Extensibility User Education
This posting is provided "AS IS" with no warranties, and confers no rights.