[WiX-users] Restoring SQL Database with Sqlstring in WiX v3

2009-01-29 Thread Eric Latendresse
Anyone have any suggestions on how to debug this? I have checked the SQL
server logs and there is nothing there pertaining to this WiX error.
Thank you in advance for your help with this. 

This is the exact error: 
Error -2147217900: failed to execute SQL string, error detail: RESTORE
DATABASE is terminating abnormally., SQL key: RestoreDB SQL string:
RESTORE DATABASE Suite FROM DISK = 'G:\Database\SuiteBlank

This is the WiX code. Creating the database works fine. the error
happens within the SQL String. Running the SQL string in SQL Query
analyzer works as well. 

Component Id=SuiteDatabaseComponent
Guid=d6e96011-3252-4e85-80b5-b1ff64045e88
File Id=DatabaseBackup
Name=SuiteBlank.bak Source=..\..\Database\Backups\SuiteBlank.bak /
CreateFolder/

!-- installs database --
sql:SqlDatabase Id=db1
  Server=[SQLSERVER]
Instance=[SQLINSTANCE] Database=Suite
  CreateOnInstall=yes
ConfirmOverwrite=yes
  DropOnUninstall=no User=SQLUser

!-- define where the database
files are saved --
sql:SqlFileSpec Id=mdf
Name=Suite_Data

Filename=[DATABASEDIR]Suite_Data.mdf
Size=2MB
GrowthSize=2MB/
sql:SqlLogFileSpec Id=ldf
Name=Suite_Log

Filename=[DATABASEDIR]Suite_Log.ldf/

/sql:SqlDatabase

sql:SqlString Id='RestoreDB'
SqlDb='db1' ContinueOnError='no' ExecuteOnInstall='yes'

SQL=RESTORE DATABASE Suite FROM DISK = '[DATABASEDIR]SuiteBlank.bak'
WITH MOVE 'Suite_Data' TO '[DATABASEDIR]Suite_Data.mdf', MOVE
'Suite_Log' TO '[DATABASEDIR]Suite_Log.ldf',REPLACE/


/Component




Eric 



-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com] 
Sent: Wednesday, January 28, 2009 9:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

Is it possible the Sql Database is locked after it creates it? The .mdf
and .ldf file DO get created before the .msi is finished, but maybe
because the .msi isn't complete the files are locked? Just a thought. If
this is the case is there a way around this? TO create the blanks sql
Database, unlock it, then run the restore script?

Eric Latendresse



-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com] 
Sent: Wednesday, January 28, 2009 8:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

Still getting the error and no way to debug? Are there any other
options? This way of restoring a database SHOULD work, right? 

Eric 


-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com] 
Sent: Tuesday, January 27, 2009 8:32 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

Yes, The sql server is local. It creates the blank database correctly
and I can see the .mdf and .ldf files at the time of the error. The
backup file is there as well. The problem must be with the restore
script. I can run the script manually and it works fine. Is there
anything that would cause WiX to read the sqlstring wrong? Maybe the
single quotes aren't coming through as they should? Is there a WiX log
or a way to add one so that I can get a more detailed message?

Eric 



-Original Message-
From: David Reed [mailto:david.r...@microsoft.com] 
Sent: Monday, January 26, 2009 3:34 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

That's often a 404-equivalent. There's usually more info in the server
error log.

Error -2147217900
Cannot open backup device 'incorrect_path_2_file.bak'.
Device error or device off-line. See the SQL Server error log
for more details.

Make sure the SQL Server process has permissions to that path and that
the file actually exists there.

You are trying to restore to a local server instance, right? Not a
remote server?



-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com]
Sent: Monday, January 26, 2009 13:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

I tried to restore the database from a backup file during the initial
install and am getting this error below. Is there WiX log or something
where I can get some more info on how to debug this? Below is my code
and I think this should work. Anyone have any ideas

Re: [WiX-users] Restoring SQL Database with Sqlstring in WiX v3

2009-01-29 Thread Eric Latendresse
Thanks David. I got this to work! Seems that putting USE master; in
front of the script did the trick. Which makes complete sense now. So
sending your code helped! I appreciate your time! 

Eric 



-Original Message-
From: David Reed [mailto:david.r...@microsoft.com] 
Sent: Thursday, January 29, 2009 11:39 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Restoring SQL Database with Sqlstring in WiX v3

I've done restores successfully this way. Profiler will help determine
the call(s) made and more details about why they failed.

Eric, assuming that you're using integrated security, are you sure that
your installer is running elevated at the point where the restore is
attempted?

We've since abandoned BAK files, but here's an example component from
the original RTM AdventureWorks2008 installer from last year:

Component Id=C_AdventureWorks2008Backup
Feature=F_AdventureWorks2008Restore Directory=INSTALLDIR
Guid={15E1D2B7-681F-41D2-8B17-A703317C359B}
Win64=$(var.PlatformIs64bit) KeyPath=yes
  ReserveCost Id=RC_AdventureWorks2008Backup
RunFromSource=83886080 RunLocal=83886080 /
  RegistryKey Root=HKLM Key=SOFTWARE\Microsoft\Microsoft SQL
Server\100\Samples
RegistryValue Name=InstallAdventureWorks2008YN
Value=[INSTALLADVENTUREWORKS2008YN] Type=string /
  /RegistryKey
  !--sql:SqlString
 
Id=SqlString_DropAdventureWorks2008
SqlDb=SqlDb_Master
Sequence=5
ExecuteOnUninstall=yes
ContinueOnError=yes
SQL=
USE master;
IF '[INSTALLADVENTUREWORKS2008YN]' = '1'
BEGIN
IF EXISTS (SELECT * FROM sys.databases WHERE name =
'AdventureWorks2008')
BEGIN
EXECUTE (N'ALTER DATABASE
AdventureWorks2008 SET SINGLE_USER WITH ROLLBACK IMMEDIATE;');
EXECUTE (N'DROP DATABASE
AdventureWorks2008;');
END
END
 /--
  sql:SqlString
Id=SqlString_RestoreAdventureWorks2008
SqlDb=SqlDb_Master
Sequence=10
ExecuteOnInstall=yes
ExecuteOnReinstall=yes
ContinueOnError=no
SQL=
IF '[INSTALLADVENTUREWORKS2008YN]' = '1'
BEGIN
USE master;
DECLARE @sql_path nvarchar(256);
SELECT @sql_path = SUBSTRING(physical_name, 1,
CHARINDEX(N'master.mdf', LOWER(physical_name)) - 1)
FROM master.sys.master_files WHERE database_id = 1 AND
file_id = 1;
IF EXISTS (SELECT * FROM sys.databases WHERE name =
'AdventureWorks2008')
BEGIN
EXECUTE (N'ALTER DATABASE
AdventureWorks2008 SET SINGLE_USER WITH ROLLBACK IMMEDIATE;');
EXECUTE (N'DROP DATABASE
AdventureWorks2008;');
END
EXECUTE (N'RESTORE DATABASE AdventureWorks2008
  FROM DISK =
''[INSTALLDIR]Tools\Samples\AdventureWorks2008.bak''
  WITH  MOVE ''AdventureWorks2008_Data'' TO N'''
+ @sql_path + N'AdventureWorks2008.mdf'',
MOVE ''AdventureWorks2008_Log''
TO N''' + @sql_path + N'AdventureWorks2008.ldf'',
MOVE ''FileStreamDocuments''
TO N''' + @sql_path + N'Documents'';');
EXECUTE (N'ALTER DATABASE AdventureWorks2008 SET
NEW_BROKER;');
END
 /
/Component





-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Thursday, January 29, 2009 09:05
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Restoring SQL Database with Sqlstring in WiX v3

Not much that is helpful.  When I've had really hard SQL issues, I've
always used the SQL profiler to dig through all the calls and find the
one that is failing.

Note: I have seen successful attaches of database files but never tried
to do a restore from backup.  I always have issues restoring from
backup.

-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com]
Sent: Thursday, January 29, 2009 08:15
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Restoring SQL Database with Sqlstring in WiX v3

Anyone have any suggestions on how to debug this? I have checked the SQL
server logs and there is nothing there pertaining to this WiX error.
Thank you in advance for your help with this.

This is the exact error:
Error -2147217900: failed to execute SQL string, error detail: RESTORE
DATABASE is terminating abnormally., SQL key: RestoreDB SQL string:
RESTORE DATABASE Suite FROM

Re: [WiX-users] Creating SQL Database with WiX v3

2009-01-28 Thread Eric Latendresse
Still getting the error and no way to debug? Are there any other
options? This way of restoring a database SHOULD work, right? 

Eric 


-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com] 
Sent: Tuesday, January 27, 2009 8:32 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

Yes, The sql server is local. It creates the blank database correctly
and I can see the .mdf and .ldf files at the time of the error. The
backup file is there as well. The problem must be with the restore
script. I can run the script manually and it works fine. Is there
anything that would cause WiX to read the sqlstring wrong? Maybe the
single quotes aren't coming through as they should? Is there a WiX log
or a way to add one so that I can get a more detailed message?

Eric 



-Original Message-
From: David Reed [mailto:david.r...@microsoft.com] 
Sent: Monday, January 26, 2009 3:34 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

That's often a 404-equivalent. There's usually more info in the server
error log.

Error -2147217900
Cannot open backup device 'incorrect_path_2_file.bak'.
Device error or device off-line. See the SQL Server error log
for more details.

Make sure the SQL Server process has permissions to that path and that
the file actually exists there.

You are trying to restore to a local server instance, right? Not a
remote server?



-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com]
Sent: Monday, January 26, 2009 13:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

I tried to restore the database from a backup file during the initial
install and am getting this error below. Is there WiX log or something
where I can get some more info on how to debug this? Below is my code
and I think this should work. Anyone have any ideas? Thanks in advance
for you help.

Component Id=SuiteDatabaseComponent
Guid=d6e96011-3252-4e85-80b5-b1ff64045e88
File Id=DatabaseBackup
Name=SuiteBlank.bak Source=..\..\Database\Backups\SuiteBlank.bak /
CreateFolder/

!-- installs database --
sql:SqlDatabase Id=db1
  Server=[SQLSERVER]
Instance=[SQLINSTANCE] Database=Suite
  CreateOnInstall=yes
ConfirmOverwrite=yes
  DropOnUninstall=no User=SQLUser

!-- define where the database
files are saved --
sql:SqlFileSpec Id=mdf
Name=Suite_Data

Filename=[DATABASEDIR]Suite_Data.mdf
Size=2MB
GrowthSize=2MB/
sql:SqlLogFileSpec Id=ldf
Name=Suite_Log

Filename=[DATABASEDIR]Suite_Log.ldf/

/sql:SqlDatabase

sql:SqlString Id='RestoreDB'
SqlDb='db1' ContinueOnError='no' ExecuteOnInstall='yes'

SQL=RESTORE DATABASE Suite FROM DISK = '[DATABASEDIR]SuiteBlank.bak'
WITH MOVE 'Suite_Data' TO '[DATABASEDIR]Suite_Data.mdf', MOVE
'Suite_Log' TO '[DATABASEDIR]Suite_Log.ldf',REPLACE/


/Component



Error -2147217900: failed to execute SQL string, error detail: RESTORE
DATABASE is terminating abnormally., SQL key: RestoreDB SQL string:
RESTORE DATABASE Suite FROM DISK = 'G:\Database\SuiteBlank.bak' WITH
MOVE 'Suite_Data' TO G:\ ...\Suite_Log.ldf',REPLACE

Eric Latendresse



-Original Message-
From: David Reed [mailto:david.r...@microsoft.com]
Sent: Friday, January 23, 2009 11:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

It really depends on what those 9k scripts are doing.

If your scripts are a raft of INSERT statements or other transactions,
then you can probably switch to CSVs and bulk load (much faster), which
is what we do with AdventureWorks now for SQL Server 2008 samples. The
WiX3 code for ours is checked into CodePlex here along with the MSBuild
scripts, etc:
http://www.codeplex.com/SqlServerSamples/SourceControl/ListDownloadableC
ommits.aspx

In our experience with AdventureWorks' installers, switching to a
backup/restore is likely to bloat the size of your installer quite a bit
because the BAK files aren't nearly as compressible (if at all) as
script files are...



From: Eric Latendresse [elatendre...@optimum-solutions.com]
Sent: Friday, January 23, 2009 13:10
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Creating

Re: [WiX-users] Creating SQL Database with WiX v3

2009-01-28 Thread Eric Latendresse
Is it possible the Sql Database is locked after it creates it? The .mdf
and .ldf file DO get created before the .msi is finished, but maybe
because the .msi isn't complete the files are locked? Just a thought. If
this is the case is there a way around this? TO create the blanks sql
Database, unlock it, then run the restore script?

Eric Latendresse



-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com] 
Sent: Wednesday, January 28, 2009 8:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

Still getting the error and no way to debug? Are there any other
options? This way of restoring a database SHOULD work, right? 

Eric 


-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com] 
Sent: Tuesday, January 27, 2009 8:32 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

Yes, The sql server is local. It creates the blank database correctly
and I can see the .mdf and .ldf files at the time of the error. The
backup file is there as well. The problem must be with the restore
script. I can run the script manually and it works fine. Is there
anything that would cause WiX to read the sqlstring wrong? Maybe the
single quotes aren't coming through as they should? Is there a WiX log
or a way to add one so that I can get a more detailed message?

Eric 



-Original Message-
From: David Reed [mailto:david.r...@microsoft.com] 
Sent: Monday, January 26, 2009 3:34 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

That's often a 404-equivalent. There's usually more info in the server
error log.

Error -2147217900
Cannot open backup device 'incorrect_path_2_file.bak'.
Device error or device off-line. See the SQL Server error log
for more details.

Make sure the SQL Server process has permissions to that path and that
the file actually exists there.

You are trying to restore to a local server instance, right? Not a
remote server?



-Original Message-
From: Eric Latendresse [mailto:elatendre...@optimum-solutions.com]
Sent: Monday, January 26, 2009 13:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

I tried to restore the database from a backup file during the initial
install and am getting this error below. Is there WiX log or something
where I can get some more info on how to debug this? Below is my code
and I think this should work. Anyone have any ideas? Thanks in advance
for you help.

Component Id=SuiteDatabaseComponent
Guid=d6e96011-3252-4e85-80b5-b1ff64045e88
File Id=DatabaseBackup
Name=SuiteBlank.bak Source=..\..\Database\Backups\SuiteBlank.bak /
CreateFolder/

!-- installs database --
sql:SqlDatabase Id=db1
  Server=[SQLSERVER]
Instance=[SQLINSTANCE] Database=Suite
  CreateOnInstall=yes
ConfirmOverwrite=yes
  DropOnUninstall=no User=SQLUser

!-- define where the database
files are saved --
sql:SqlFileSpec Id=mdf
Name=Suite_Data

Filename=[DATABASEDIR]Suite_Data.mdf
Size=2MB
GrowthSize=2MB/
sql:SqlLogFileSpec Id=ldf
Name=Suite_Log

Filename=[DATABASEDIR]Suite_Log.ldf/

/sql:SqlDatabase

sql:SqlString Id='RestoreDB'
SqlDb='db1' ContinueOnError='no' ExecuteOnInstall='yes'

SQL=RESTORE DATABASE Suite FROM DISK = '[DATABASEDIR]SuiteBlank.bak'
WITH MOVE 'Suite_Data' TO '[DATABASEDIR]Suite_Data.mdf', MOVE
'Suite_Log' TO '[DATABASEDIR]Suite_Log.ldf',REPLACE/


/Component



Error -2147217900: failed to execute SQL string, error detail: RESTORE
DATABASE is terminating abnormally., SQL key: RestoreDB SQL string:
RESTORE DATABASE Suite FROM DISK = 'G:\Database\SuiteBlank.bak' WITH
MOVE 'Suite_Data' TO G:\ ...\Suite_Log.ldf',REPLACE

Eric Latendresse



-Original Message-
From: David Reed [mailto:david.r...@microsoft.com]
Sent: Friday, January 23, 2009 11:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

It really depends on what those 9k scripts are doing.

If your scripts are a raft of INSERT statements or other transactions,
then you can probably switch to CSVs and bulk load (much faster), which
is what we do with AdventureWorks now for SQL Server 2008 samples. The
WiX3 code for ours

Re: [WiX-users] Creating SQL Database with WiX v3

2009-01-26 Thread Eric Latendresse
I tried to restore the database from a backup file during the initial
install and am getting this error below. Is there WiX log or something
where I can get some more info on how to debug this? Below is my code
and I think this should work. Anyone have any ideas? Thanks in advance
for you help. 

Component Id=SuiteDatabaseComponent
Guid=d6e96011-3252-4e85-80b5-b1ff64045e88
File Id=DatabaseBackup
Name=SuiteBlank.bak Source=..\..\Database\Backups\SuiteBlank.bak /
CreateFolder/

!-- installs database --
sql:SqlDatabase Id=db1
  Server=[SQLSERVER]
Instance=[SQLINSTANCE] Database=Suite
  CreateOnInstall=yes
ConfirmOverwrite=yes
  DropOnUninstall=no User=SQLUser

!-- define where the database
files are saved --
sql:SqlFileSpec Id=mdf
Name=Suite_Data

Filename=[DATABASEDIR]Suite_Data.mdf
Size=2MB
GrowthSize=2MB/
sql:SqlLogFileSpec Id=ldf
Name=Suite_Log

Filename=[DATABASEDIR]Suite_Log.ldf/

/sql:SqlDatabase

sql:SqlString Id='RestoreDB'
SqlDb='db1' ContinueOnError='no' ExecuteOnInstall='yes'

SQL=RESTORE DATABASE Suite FROM DISK = '[DATABASEDIR]SuiteBlank.bak'
WITH MOVE 'Suite_Data' TO '[DATABASEDIR]Suite_Data.mdf', MOVE
'Suite_Log' TO '[DATABASEDIR]Suite_Log.ldf',REPLACE/


/Component



Error -2147217900: failed to execute SQL string, error detail: RESTORE
DATABASE is terminating abnormally., SQL key: RestoreDB SQL string:
RESTORE DATABASE Suite FROM DISK = 'G:\Database\SuiteBlank.bak' WITH
MOVE 'Suite_Data' TO G:\ ...\Suite_Log.ldf',REPLACE

Eric Latendresse



-Original Message-
From: David Reed [mailto:david.r...@microsoft.com] 
Sent: Friday, January 23, 2009 11:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQL Database with WiX v3

It really depends on what those 9k scripts are doing.

If your scripts are a raft of INSERT statements or other transactions,
then you can probably switch to CSVs and bulk load (much faster), which
is what we do with AdventureWorks now for SQL Server 2008 samples. The
WiX3 code for ours is checked into CodePlex here along with the MSBuild
scripts, etc:
http://www.codeplex.com/SqlServerSamples/SourceControl/ListDownloadableC
ommits.aspx

In our experience with AdventureWorks' installers, switching to a
backup/restore is likely to bloat the size of your installer quite a bit
because the BAK files aren't nearly as compressible (if at all) as
script files are...



From: Eric Latendresse [elatendre...@optimum-solutions.com]
Sent: Friday, January 23, 2009 13:10
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Creating SQL Database with WiX v3

I am creating a SQL database with my installer. Right now I have
approximately 9000 scripts to be run after the database is created. This
is taking around 20mins for the install to complete. Is there anything I
can do to speed this process up? I thought about running a  single
script to restore the database from a backup file of the database, but
thought I'd ask if there was a better way.



Eric Latendresse






--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Creating SQL Database with WiX v3

2009-01-23 Thread Eric Latendresse
I am creating a SQL database with my installer. Right now I have
approximately 9000 scripts to be run after the database is created. This
is taking around 20mins for the install to complete. Is there anything I
can do to speed this process up? I thought about running a  single
script to restore the database from a backup file of the database, but
thought I'd ask if there was a better way. 

 

Eric Latendresse

 

 

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Error Creating Patch

2008-07-30 Thread Eric Latendresse
I found the problem. The paths in the Patch.wxs to the two .msi's were
incorrect. 

Eric 


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Monday, July 28, 2008 10:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Error Creating Patch

What version of WiX?  What was the command-line?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Monday, July 28, 2008 10:21
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Error Creating Patch

I was successful in creating the two different .msi's. Built the
transform with torch. Compiled the Patch.wxs. But when I run pyro I get
this error.



..\Patches\Patch.wixmsp : error PYRO0104 : Not a valid output file;
detail: Invalid character in the given encoding. Line 1, position 1.



Anyone have any ideas why this is happening or know how I can debug
this?



Thanks,



Eric






-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Patching SQL Database with script

2008-07-30 Thread Eric Latendresse
Could you give a little more information? Would these new scripts need
to be included in a separate component other than my SQL Database
component? In my installer I am creating a new database and running a
script CreateTable.sql on the install. This works. For the patch I
changed the CreateTable.sql to AlterTable.sql in my Setup.wxs. I want to
include new sql scripts in the updated .msi and create a patch that will
execute the changed sql. Does it need to have a different Binary Key?
When executing the patch.msp I get an option to Change/Repair/Remove.
I've tried both Change and repair, but it seems Change is the option I
want to use since it asks for the SQL credentials. The assemblies are
getting updated but the script is not being run. I'm a little unsure how
this is all suppose to work. 

Binary Id=CreateTable
SourceFile=..\..\SQLScript\MigrateScripts\CreateTable.sql /

Component Id=SuiteDatabaseComponent
Guid=d6e96011-3252-4e85-80b5-b1ff64045e88
CreateFolder/

!-- installs database --
sql:SqlDatabase Id=db1
  Server=[SQLSERVER]
Instance=[SQLINSTANCE] Database=SuiteWix
  CreateOnInstall=yes
ConfirmOverwrite=yes
  DropOnUninstall=no User=SQLUser

!-- define where the database
files are saved --
sql:SqlFileSpec Id=mdf
Name=SuiteWix_Data

Filename=[DATABASEDIR]SuiteWiX_Data.mdf
Size=2MB
GrowthSize=2MB/
sql:SqlLogFileSpec Id=ldf
Name=SuiteWix_Log

Filename=[DATABASEDIR]SuiteWiX_Log.ldf/

!-- add reference to database
script bianarieshere --
sql:SqlScript Id=CreateTable
BinaryKey=CreateTable ExecuteOnInstall=yes/
/sql:SqlDatabase
/Component

Eric 



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Monday, July 28, 2008 10:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching SQL Database with script

The SqlScript element (or SqlString if you just want to run a couple
strings).

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Monday, July 28, 2008 14:59
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Patching SQL Database with script

My initial installer creates the SQL database perfectly, but I want to
be able to include new SQL scripts to be run with my patches. Could
someone give me some insight on how to do this?



Eric






-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Error Creating Patch

2008-07-28 Thread Eric Latendresse
I was successful in creating the two different .msi's. Built the
transform with torch. Compiled the Patch.wxs. But when I run pyro I get
this error. 

 

..\Patches\Patch.wixmsp : error PYRO0104 : Not a valid output file;
detail: Invalid character in the given encoding. Line 1, position 1.

 

Anyone have any ideas why this is happening or know how I can debug
this?

 

Thanks, 

 

Eric 

 

 

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Patching SQL Database with script

2008-07-28 Thread Eric Latendresse
My initial installer creates the SQL database perfectly, but I want to
be able to include new SQL scripts to be run with my patches. Could
someone give me some insight on how to do this? 

 

Eric 

 

 

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Manual un-install

2008-07-25 Thread Eric Latendresse
thanks

Eric 


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chad
Petersen
Sent: Thursday, July 24, 2008 5:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Manual un-install

Here's a link

http://support.microsoft.com/kb/290301



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Thursday, July 24, 2008 12:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Manual un-install

How can I manually un-install a setup? I get an error when I try to
remove my setup from Add\Remove programs.

Thanks, 

 

Eric 

 

 


-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Build Fails with NAnt. The formatofthefile 'NAntTasks.dll' is invalid.

2008-07-24 Thread Eric Latendresse
Excellent!

Thanks for your help.

Eric Latendresse

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gavin Bee
Sent: Wednesday, July 23, 2008 9:00 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Build Fails with NAnt. The formatofthefile
'NAntTasks.dll' is invalid.

Eric,

My apologies for leaving that part out.  CustomOutputPath needs to be
used
to set the value of OutputPath.  So your Debug and Release
PropertyGroups
end up looking like the following 

  PropertyGroup Condition= '$(Configuration)' == 'Debug' 
OutputPath$(CustomOutputPath)/OutputPath
IntermediateOutputPathobj\Debug\/IntermediateOutputPath
DefineConstantsDebug/DefineConstants
  /PropertyGroup
  PropertyGroup Condition= '$(Configuration)' == 'Release' 
OutputPath$(CustomOutputPath)/OutputPath
IntermediateOutputPathobj\Release\/IntermediateOutputPath
  /PropertyGroup 

Note that in the above your output path ends up being the same for debug
and
release.

Gavin :)

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Wednesday, July 23, 2008 5:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Build Fails with NAnt. The format ofthefile
'NAntTasks.dll' is invalid.

Thanks Gavin, 

I think I'm very close. It still builds my .msi, but I can't get the
CustomOutput argument to work. I haven't worked with msbuild project
files before so I'm sure my code is wrong. Maybe you can easily see what
I'm doing wrong. 

Nant Code:

exec
program=${framework::get-framework-directory(framework::get-target-fram
ework())}\msbuild.exe  resultproperty=msbuild.result
failonerror=true
arg value=${wix.work.dir}\SuiteSetup.wixproj/
arg value=/nologo/
arg value=/noconsolelogger/
arg value=/target:Build/
arg
value=/property:SolutionDir=${project::get-base-directory()}\\/
 arg value=/property:CustomOutputPath=${wix.release.dir}/
 arg
value=/property:CustomOutputName=${wix.release.dir}\Setup_${project.ver
sion}.msi/
/exec

Project File:

Project DefaultTargets=Build
xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
  PropertyGroup
Configuration Condition= '$(Configuration)' == ''
Debug/Configuration
ProductVersion3.0/ProductVersion
ProjectGuid{2891ae0b-bf21-405f-b3af-87075ee2f574}/ProjectGuid
SchemaVersion2.0/SchemaVersion
OutputNameSuiteSetup/OutputName
OutputTypePackage/OutputType
WixTargetsPath Condition= '$(WixTargetsPath)' == ''
$(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPat
h
WixToolPath$(ProgramFiles)\Windows Installer XML
v3\bin\/WixToolPath
  /PropertyGroup
  PropertyGroup Condition= '$(Configuration)' == 'Debug' 
OutputPathbin\Debug\/OutputPath
IntermediateOutputPathobj\Debug\/IntermediateOutputPath
CustomOutputPath$(CustomOutputPath)/CustomOutputPath
DefineConstantsDebug/DefineConstants
  /PropertyGroup
  PropertyGroup Condition= '$(Configuration)' == 'Release' 
OutputPathbin\Release\/OutputPath
IntermediateOutputPathobj\Release\/IntermediateOutputPath
CustomOutputPath$(CustomOutputPath)/CustomOutputPath
  /PropertyGroup
  ItemGroup
Compile Include=SuiteSetup.wxs /
  /ItemGroup
  ItemGroup
WixExtension Include=C:\Program Files (x86)\Windows Installer XML
v3\bin\WixSqlExtension.dll /
WixExtension Include=C:\Program Files (x86)\Windows Installer XML
v3\bin\WixUIExtension.dll /
WixExtension Include=C:\Program Files (x86)\Windows Installer XML
v3\bin\WixUtilExtension.dll /
  /ItemGroup
  Import Project=$(WixTargetsPath) /
/Project

Eric Latendresse



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gavin Bee
Sent: Wednesday, July 23, 2008 2:54 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Build Fails with NAnt. The format ofthefile
'NAntTasks.dll' is invalid.

Sounds like you need to pass the desired output path to msbuild from
nant.
You can use the /property command line argument to msbuild.exe to pass
property values from NAnt into MSBUILD.

We use the a NAnt exec task that looks something like the following:
  exec
program=${framework::get-framework-directory(framework::get-target-fram
ewor
k())}\msbuild.exe resultproperty=msbuild.result failonerror=false
arg value=${product.sln}/
arg value=/nologo/
arg value=/noconsolelogger/
arg value=/target:Build/
arg
value=/property:SolutionDir=${project::get-base-directory()}\\/
arg value=/logger:Kobush.Build.Logging.XmlLogger,${
XmlLogger4MSBuild.directory}\bin\Release\Kobush.Build.dll;${compile.log.
xml}
/
  /exec 

You could just add another argument to the list of args
arg value=/property:CustomOutputPath=your output path/
arg value=/property:CustomOutputName=your output file

[WiX-users] Manual un-install

2008-07-24 Thread Eric Latendresse
How can I manually un-install a setup? I get an error when I try to
remove my setup from Add\Remove programs.

Thanks, 

 

Eric 

 

 

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Build Fails with NAnt. The format of thefile 'NAntTasks.dll' is invalid.

2008-07-23 Thread Eric Latendresse
Great, that worked. I was able to build my installer using my NAnt build
file. However. I need to specify an output path every time the .msi gets
built. Right now the output path is what is set in the protect
properties. The reason I need to separate the build versions is that
ultimately I need to look at the different versions to create patches.
Can you recommend a way to do this with the msbuild command?

Eric Latendresse



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent: Tuesday, July 22, 2008 5:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Build Fails with NAnt. The format of thefile
'NAntTasks.dll' is invalid.

One option to consider is using the shipping MSBuild .targets file that
has a complete build process for WiX in conjunction with NAnt. Trying to
re-construct a build process using individual tasks is often fraught
with peril, and using the one that ships with WiX is almost always a
better idea.

You would create a .wixproj that uses the MSBuild process for building
WiX (a quick way to do this is to create a WiX project in Visual
Studio), and then in your nant build script just do msbuild
project=myinstaller.wixproj. You'll get our well-tested and supported
build process for free, yet still be able to use nant as your overall
build driver.

Neil

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Tuesday, July 22, 2008 2:36 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Build Fails with NAnt. The format of the file
'NAntTasks.dll' is invalid.

I am using NAnt to build my WiX project. Here is the code:



target name=CreateSetupPackageUsingWiX description=Create the
installer package using WiX Script

mkdir dir=${wix.release.dir}/

loadtasks
assembly=${wix.work.dir}/Microsoft.Tools.WindowsInstallerXml.NAntTasks.
dll/



candle out=${wix.work.dir}\ cultures=en-us
extensions=WixUtilExtension;WixWixSqlExtension;WixUIExtension
exedir=${wix.dir}\ rebuild=true

sources

include name=SuiteSetup.wxs /

/sources

/candle

light out=${wix.release.dir}/SuiteSetup.msi cultures=en-us
extensions=WixUtilExtension;WixWixSqlExtension;WixUIExtension
exedir=${wix.dir}\ rebuild=true

sources

include name=SuiteSetup.wixobj /

/sources

/light

/target









Here is the error I am getting:



BUILD FAILED - 1 non-fatal error(s), 0 warning(s)



D:\Development\SuiteBuild_Development\BuildProcess.build(209,4):

Failure scanning \C:\Program Files (x86)\Windows Installer XML
v3\bin\Microsoft.

Tools.WindowsInstallerXml.NAntTasks.dll\ for extensions.

The format of the file
'Microsoft.Tools.WindowsInstallerXml.NAntTasks.dll' is invalid.



Total time: 0.1 seconds.





Eric






-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK  win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Build Fails with NAnt. The format ofthefile 'NAntTasks.dll' is invalid.

2008-07-23 Thread Eric Latendresse
Thanks Gavin, 

I think I'm very close. It still builds my .msi, but I can't get the
CustomOutput argument to work. I haven't worked with msbuild project
files before so I'm sure my code is wrong. Maybe you can easily see what
I'm doing wrong. 

Nant Code:

exec
program=${framework::get-framework-directory(framework::get-target-fram
ework())}\msbuild.exe  resultproperty=msbuild.result
failonerror=true
arg value=${wix.work.dir}\SuiteSetup.wixproj/
arg value=/nologo/
arg value=/noconsolelogger/
arg value=/target:Build/
arg
value=/property:SolutionDir=${project::get-base-directory()}\\/
 arg value=/property:CustomOutputPath=${wix.release.dir}/
 arg
value=/property:CustomOutputName=${wix.release.dir}\Setup_${project.ver
sion}.msi/
/exec

Project File:

Project DefaultTargets=Build
xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
  PropertyGroup
Configuration Condition= '$(Configuration)' == ''
Debug/Configuration
ProductVersion3.0/ProductVersion
ProjectGuid{2891ae0b-bf21-405f-b3af-87075ee2f574}/ProjectGuid
SchemaVersion2.0/SchemaVersion
OutputNameSuiteSetup/OutputName
OutputTypePackage/OutputType
WixTargetsPath Condition= '$(WixTargetsPath)' == ''
$(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPat
h
WixToolPath$(ProgramFiles)\Windows Installer XML
v3\bin\/WixToolPath
  /PropertyGroup
  PropertyGroup Condition= '$(Configuration)' == 'Debug' 
OutputPathbin\Debug\/OutputPath
IntermediateOutputPathobj\Debug\/IntermediateOutputPath
CustomOutputPath$(CustomOutputPath)/CustomOutputPath
DefineConstantsDebug/DefineConstants
  /PropertyGroup
  PropertyGroup Condition= '$(Configuration)' == 'Release' 
OutputPathbin\Release\/OutputPath
IntermediateOutputPathobj\Release\/IntermediateOutputPath
CustomOutputPath$(CustomOutputPath)/CustomOutputPath
  /PropertyGroup
  ItemGroup
Compile Include=SuiteSetup.wxs /
  /ItemGroup
  ItemGroup
WixExtension Include=C:\Program Files (x86)\Windows Installer XML
v3\bin\WixSqlExtension.dll /
WixExtension Include=C:\Program Files (x86)\Windows Installer XML
v3\bin\WixUIExtension.dll /
WixExtension Include=C:\Program Files (x86)\Windows Installer XML
v3\bin\WixUtilExtension.dll /
  /ItemGroup
  Import Project=$(WixTargetsPath) /
/Project

Eric Latendresse



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gavin Bee
Sent: Wednesday, July 23, 2008 2:54 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Build Fails with NAnt. The format ofthefile
'NAntTasks.dll' is invalid.

Sounds like you need to pass the desired output path to msbuild from
nant.
You can use the /property command line argument to msbuild.exe to pass
property values from NAnt into MSBUILD.

We use the a NAnt exec task that looks something like the following:
  exec
program=${framework::get-framework-directory(framework::get-target-fram
ewor
k())}\msbuild.exe resultproperty=msbuild.result failonerror=false
arg value=${product.sln}/
arg value=/nologo/
arg value=/noconsolelogger/
arg value=/target:Build/
arg
value=/property:SolutionDir=${project::get-base-directory()}\\/
arg value=/logger:Kobush.Build.Logging.XmlLogger,${
XmlLogger4MSBuild.directory}\bin\Release\Kobush.Build.dll;${compile.log.
xml}
/
  /exec 

You could just add another argument to the list of args
arg value=/property:CustomOutputPath=your output path/
arg value=/property:CustomOutputName=your output file name/

You will then have to update your wixproj file to use these property
values
to populate OutputPath and OutputName as appropriate.

Hope that helps,
Gavin :)

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Wednesday, July 23, 2008 2:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Build Fails with NAnt. The format of thefile
'NAntTasks.dll' is invalid.

Great, that worked. I was able to build my installer using my NAnt build
file. However. I need to specify an output path every time the .msi gets
built. Right now the output path is what is set in the protect
properties. The reason I need to separate the build versions is that
ultimately I need to look at the different versions to create patches.
Can you recommend a way to do this with the msbuild command?

Eric Latendresse



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent: Tuesday, July 22, 2008 5:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Build Fails with NAnt. The format of thefile
'NAntTasks.dll' is invalid.

One option to consider is using the shipping MSBuild .targets file that
has a complete build process for WiX in conjunction with NAnt. Trying to
re-construct

[WiX-users] Build Fails with NAnt. The format of the file 'NAntTasks.dll' is invalid.

2008-07-22 Thread Eric Latendresse
I am using NAnt to build my WiX project. Here is the code: 

 

target name=CreateSetupPackageUsingWiX description=Create the
installer package using WiX Script

mkdir dir=${wix.release.dir}/

loadtasks
assembly=${wix.work.dir}/Microsoft.Tools.WindowsInstallerXml.NAntTasks.
dll/

 

candle out=${wix.work.dir}\ cultures=en-us
extensions=WixUtilExtension;WixWixSqlExtension;WixUIExtension
exedir=${wix.dir}\ rebuild=true

sources

include name=SuiteSetup.wxs /

/sources

/candle

light out=${wix.release.dir}/SuiteSetup.msi cultures=en-us
extensions=WixUtilExtension;WixWixSqlExtension;WixUIExtension
exedir=${wix.dir}\ rebuild=true

sources

include name=SuiteSetup.wixobj /

/sources

/light

/target

 

 

 

 

Here is the error I am getting:

 

BUILD FAILED - 1 non-fatal error(s), 0 warning(s)

 

D:\Development\SuiteBuild_Development\BuildProcess.build(209,4):

Failure scanning \C:\Program Files (x86)\Windows Installer XML
v3\bin\Microsoft.

Tools.WindowsInstallerXml.NAntTasks.dll\ for extensions.

The format of the file
'Microsoft.Tools.WindowsInstallerXml.NAntTasks.dll' is invalid.

 

Total time: 0.1 seconds.

 

 

Eric 

 

 

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Build Automation with NAnt

2008-05-14 Thread Eric Latendresse
Does anyone have any documentation on this?

 

Eric 

 

-
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Failed to drop sql database

2008-05-06 Thread Eric Latendresse
Thanks Rob, that worked.

 

Eric 

 

From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 05, 2008 9:53 PM
To: Eric Latendresse; wix-users@lists.sourceforge.net
Subject: RE: Failed to drop sql database

 

What I usually do is build the fixed MSI then do a recache-reinstall
(msiexec /fv fixed.msi) to fix the uninstall issues.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Monday, May 05, 2008 12:11
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Failed to drop sql database

 

I have an installer that installs a Windows App along with a SQL
Database. The SQL Database is defined in my .wxs to be dropped on
uninstall. I am trying to remove my application through the Add\Remove
programs in the Control Panel. But, I made the mistake of manually
deleting the database before removing the application. Now, when I try
to remove the application I get this error. 

 

Error -2147467259: failed to drop SQL database: , error detail: unknown
error. 

 

Anyone have an idea how to remove my app?

 

Eric

 

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Failed to drop sql database

2008-05-05 Thread Eric Latendresse
I have an installer that installs a Windows App along with a SQL
Database. The SQL Database is defined in my .wxs to be dropped on
uninstall. I am trying to remove my application through the Add\Remove
programs in the Control Panel. But, I made the mistake of manually
deleting the database before removing the application. Now, when I try
to remove the application I get this error. 

 

Error -2147467259: failed to drop SQL database: , error detail: unknown
error. 

 

Anyone have an idea how to remove my app?

 

Eric

 

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] How to execture a Custom Action

2008-03-14 Thread Eric Latendresse
I am trying to execute a custom action on a specific dialog after the
ValidateProductID event. I have tried using  InstallUISequence and
also InstallExecuteSequence.  InsatllUISequence executes the
TestDialog right away which is not what I need. The
InstallExecuteSequence does not seem to pass the PIDKEY value to my CA.
Can someone point me in the right direction on how I should do this
correctly? Basicly what I need to do is execute the CA after the user
has entered the key on the LicenseKeyDialog. The CA should return the
ProductID value to DisplayLicenseDialog. Attached is my .wxs. 

 

Thanks

 

Eric Latendresse

 



SuiteSetup.wxs
Description: SuiteSetup.wxs
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to execture a Custom Action

2008-03-14 Thread Eric Latendresse
Are you saying to do this?:

 

!-- Define a custom action to execute the PIDKEYValidation function
from the DLL --

CustomAction Id=PIDKEYValidation
BinaryKey=ValidatePIDKEYCA DllEntry=PIDKEYValidation /



!-- Define a custom action to set the PIDKEY property value
--

CustomAction Id=SetPIDKeyValue Property=PIDKEY
Value=[PIDKEY]/

 

 

Publish Dialog=LicenseKeyDlg Control=Back
Event=NewDialog Value=LicenseAgreementDlg1/Publish

Publish Dialog=LicenseKeyDlg Control=Next
Event=DoAction Value=SetPIDKeyValue Order=11/Publish

Publish Dialog=LicenseKeyDlg Control=Next
Event=NewDialog Value=DisplayLicenseDialog
Order=2ProductID/Publish

 

 

Then use the InstallUISequence like this?:

 

InstallUISequence

  Custom

Action=SetPIDKeyValue

After=ValidateProductID /

  Custom

Action=PIDKEYValidation

After=SetPIDKeyValue /

  Show

Dialog=DisplayLicenseDialog

After=PIDKEYValidation /

/InstallUISequence

 

I must still be missing something because the DisplayLicenseDialog is
still showing as soon as the msi is executed. 

Thanks for your help. 

 

Eric 

 

From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 14, 2008 1:00 PM
To: Eric Latendresse
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to execture a Custom Action

 

Eric Latendresse wrote: 

I am trying to execute a custom action on a specific dialog after the
ValidateProductID event. I have tried using  InstallUISequence and
also InstallExecuteSequence.  InsatllUISequence executes the
TestDialog right away which is not what I need. The
InstallExecuteSequence does not seem to pass the PIDKEY value to my CA.
Can someone point me in the right direction on how I should do this
correctly? Basicly what I need to do is execute the CA after the user
has entered the key on the LicenseKeyDialog. The CA should return the
ProductID value to DisplayLicenseDialog. Attached is my .wxs. 


Use Publish/@Event=DoAction with a Value attribute of the CA name.



-- 
sig://boB
http://joyofsetup.com/
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Feature Groups

2008-03-10 Thread Eric Latendresse
I am trying to create a feature tree in the installation like this for example:

 

-MainProductFeature

-HelpFeature

 

The Help component should be listed under the MainProductFeature and users 
should see it as part of that feature. Not sure if I should be using the 
FeatureGroup or the ComponentGroup, or how I should use either. The result of 
my code shows the tree as:

 

-MainProductFeature

-HelpFeature

 

Can someone provide an example on how I can do this. Thanks.

 

Eric

 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Feature Groups

2008-03-10 Thread Eric Latendresse
Thanks, that worked. 

Eric 


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Hamflett
Sent: Monday, March 10, 2008 10:01 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Feature Groups

You should just need to put one feature inside the other, like this:

Feature Id=myFeature ... 
   Feature Id=mySubFeature ...
   /Feature
/Feature

Rob

Eric Latendresse wrote:
 I am trying to create a feature tree in the installation like this for

 example:
 
  
 
 -MainProductFeature
 
 -HelpFeature
 
  
 
 The Help component should be listed under the MainProductFeature and 
 users should see it as part of that feature. Not sure if I should be 
 using the FeatureGroup or the ComponentGroup, or how I should use 
 either. The result of my code shows the tree as:
 
  
 
 -MainProductFeature
 
 -HelpFeature
 
  
 
 Can someone provide an example on how I can do this. Thanks.
 
  
 
 Eric
 
  
 
 


 


-
 This SF.net email is sponsored by: Microsoft
 Defy all challenges. Microsoft(R) Visual Studio 2008.
 http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
 
 


 
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Validate Product Key Dialog with custom action

2008-03-10 Thread Eric Latendresse
Thanks for your reply Phil. I did find some examples on managed custom
actions and I know what you mean by arm-weaving. I also found an
example using a C++ Win32 application. This seems like it is the way I
need to go but the example was outdated and the code didn't compile. I'm
not very familiar with C++, do you have an example that I could follow?

 

Thanks, 

 

Eric 

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: Monday, March 10, 2008 5:39 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Validate Product Key Dialog with custom action

 

You can't get there from here.  The infrastructure for calling managed
code custom actions isn't natively supported by MSI, and even if you did
all the arm-waving to make it work as a custom action (called from the
UI sequence) it's so decoupled from the install that you cannot use it
to set a property in the install.  This is important because you
probably need to disable the next button until the key is valid, and
this mechanism uses properties.  

 

When I say arm waving I don't mean the InstallUtilLib.dll stuff, bad
as it is,  I assume that you are in the UI sequence and no files have
been installed. How do you get your assembly onto the system, and how do
you call it? This is a mountain of code. 

 

Speaking of mountains, there's a mountain of opinion in the archives and
elsewhere on calling managed code custom actions, most of which falls
into two categories : 1) Don't do it because of the issues involved
and 2) Why the heck doesn't WiX/MSI support it.  So if all you're
going to do is look at the text of the key and say Yes or No, then
vbscript isn't too bad. If you're going out into the world to read files
or the internet, C++ is recommended. 

 

Phil Wilson 

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Monday, March 10, 2008 10:33 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Validate Product Key Dialog with custom action

 

I want to use a C#.net assembly to validate my product key. Could
someone point me in the right direction on where to start?

 

Thanks,

 

Eric 

 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] INstall SQL Database

2008-03-07 Thread Eric Latendresse
I have built an installer that creates a SQL database and am getting the
following error. 

 

Error -2147217900: failed to create SQL database: SuiteWiX error detail:
cannot create file
C:\ProgramFiles\OptimumSuite\Database\SuiteWix_log.LDF because it
already exists. 

 

 

 

I have verified that this file does not exist. Can someone shed some
light on what might be wrong? I have attached my .wxs

 

Thanks in advance,

 

Eric 

 

image001.png

SuiteSetup.wxs
Description: SuiteSetup.wxs
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] INstall SQL Database

2008-03-07 Thread Eric Latendresse
Nvm. I found that I was using the sql:SqlFileSpec for both the data and
log files. Changed to sql:SqlLogFileSpec

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Friday, March 07, 2008 12:22 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] INstall SQL Database

 

I have built an installer that creates a SQL database and am getting the
following error. 

 

Error -2147217900: failed to create SQL database: SuiteWiX error detail:
cannot create file
C:\ProgramFiles\OptimumSuite\Database\SuiteWix_log.LDF because it
already exists. 

 

 

 

I have verified that this file does not exist. Can someone shed some
light on what might be wrong? I have attached my .wxs

 

Thanks in advance,

 

Eric 

 

image001.png-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] INstall SQL Database

2008-02-21 Thread Eric Latendresse
I am trying to create a SQL database as a separate component. I know that it is 
probably something simple maybe you could take a look at the attached and point 
me in the right direction. Basically I want to install the SQL Data and Log 
files in a sub directory to the Main application folder. Attached is my wxs. 
The error that I get is:

 

The Directory/Component pair must be listed in the CreateFolders table

 

 

Eric Latendresse

Optimum Solutions, Inc.

(615) 369-6097 office

(615) 329-4448 fax

[EMAIL PROTECTED]

www.optimum-solutions.com http://www.optimum-solutions.com/ 

Payroll ∙ HR ∙ Time  Attendance
Made Simple.

 



SuiteSetup.wxs
Description: SuiteSetup.wxs
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] INstall SQL Database

2008-02-21 Thread Eric Latendresse
Thanks for your reply, but now I get the error:

 

error CNDL0005 : The CreateFolder element contains an unexpected child element 
'sql:SqlDatabase’

 

 

Eric 

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander 
Shevchuk
Sent: Thursday, February 21, 2008 4:29 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] INstall SQL Database

 

Hi Eric,

 

Add CreateFolder around sql:SqlDatabase.  sql:SqlDatabase is a custom 
action and Windows Installer will not create an empty folder unless it will be 
forced to do so with explicit CreateFolder:

 

Directory Id=”SuiteDatabaseFolder”

Component iD=”SuiteDatabaseComponent” …

CreateFolder

sql:SqlDatabase … /

/CreateFolder

/Component

/Directory

 

 

Alex

 

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Latendresse
Sent: Thursday, February 21, 2008 2:11 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] INstall SQL Database

 

I am trying to create a SQL database as a separate component. I know that it is 
probably something simple maybe you could take a look at the attached and point 
me in the right direction. Basically I want to install the SQL Data and Log 
files in a sub directory to the Main application folder. Attached is my wxs. 
The error that I get is:

 

“The Directory/Component pair must be listed in the CreateFolders table”

 

 

Eric 

 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to configure SQL Express bootstrap

2007-10-02 Thread Eric Latendresse
Excellent, Thanks!

 

Eric

 

From: John Vottero [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 02, 2007 4:57 PM
To: Eric Latendresse; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] How to configure SQL Express bootstrap

 

Find the Package.xml file for SQL Express, edit it and look for the
Command PackageFile=sqlexpr32.exe Arguments=.. element.  Change
the Arguments to what you want.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Latendresse
Sent: Tuesday, October 02, 2007 5:41 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to configure SQL Express bootstrap

 

I created a bootstrapper  with MSbuild to install SQL Express, but I'd
like to change the configuration... Since it is in a bootstrap it
doesn't show the install wizard. Surely configuring the database engine
is possible. Does someone have an example or can please point me in the
right direction? 

 

Thanks.

 

Eric Latendresse

Programmer

Optimum Solutions, Inc.

615-329-2313x 2229

615-329-4448  fax

[EMAIL PROTECTED]

www.optimum-solutions.com http://www.optimum-solutions.com/ 

Your Only Payroll,HR and time  attendance solution

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] SQL Express 2005 bootstrap

2007-09-21 Thread Eric Latendresse
I have added a bootstrap for the SQL Express installer. Everything
builds and the .msi gets created but, when I run the installer it starts
extracting the SQL Express as expected. I then get an error message
saying There is a problem with this Windows Installer package. A
program run as part of the setup did not finish as expected. Contact
your support personnel or package vendor. What can I do to debug this
problem? Below is my bootstrap code inside my .wxs file. Am I missing
something?

 

CustomAction Id=InstallExpress Return=check ExeCommand=/qn
Property=ExprPath Impersonate=yes /

Property
Id=ExprPath![CDATA[C:\SqlServerExpress_Advanced.EXE]]/Property

  InstallUISequence

Custom Action= InstallExpress Before=
ExecuteAction1/Custom

  /InstallUISequence

 

Eric

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Run SQL Express 2005 install as WiX Component

2007-09-20 Thread Eric Latendresse
Does anyone know how I can run a SQL Express installation (or another
setup.exe) as a WiX component? Thanks in advance for you help.

 

Eric 

 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users