VS bug found in making a VS Setup project for a VSIP package

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

George Kodinov - 21 Oct 2004 10:19 GMT

Hi,
I've tried making a deployment project for one of my VSIP packages to not
use the self registration.
I have a number of string keys in the form "#nnn" (that refer to resource
ids).
When installing the installer produced thease get set as DWORD registry
values.
Example :
in my deployment project
HKLM\Software\Microsoft\VisualStudio\7.1\Projects\{79A1BA5A-70F2-4497-9739-672A94B02870}\DisplayName="#108"

When installed that becomes DWORD: 0x6c (108)

IMHO that is a genuine VS bug preventing the usage of non-selfregistering
VsPackages.

Reply to this Message

Bob Arnson [MSFT] - 25 Oct 2004 16:34 GMT

> Hi,
> I've tried making a deployment project for one of my VSIP packages to not
[quoted text clipped - 11 lines]
> IMHO that is a genuine VS bug preventing the usage of non-selfregistering
> VsPackages.

That's actually how Windows Installer works, not a peculiarity of deployment
projects. The Registry table
(<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/regis
try_table.asp>)
has only Name and Value columns, not a column to indicate the value type. A
leading # indicates a REG_DWORD type. You need to escape the # so it's
written as-is as a string. I'm not sure how to do it in a deployment
project, but in raw MSI tables, it would be

[\#]nnn

See Formatted.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/forma
tted.asp

Signature

sig://boB
http://msdn.microsoft.com/vstudio/extend/

Reply to this Message

VS bug found in making a VS Setup project for a VSIP package

Free Magazines