做.net安装包时用vbs来执行自定义操作

在制作安装包时用vbs来执行自定义操作需要做的有（本人的项目）：

1、在自定义操作---->提交----->右键添加自定义操作，将写好的vbs加载进来。

2、右键设置vbs的一个属性CustomActionData为[TARGETDIR]（这里是为了取得安装后的路径）

3、vbs中的代码如下所示：

 

     Dim wshShell,strPath,fso
     On error resume next
     Set wshShell = CreateObject("Wscript.Shell")
     Set fso = CreateObject("Scripting.FileSystemObject")
     strPath =Session.Property("CustomActionData") &"某程序名.exe"
     if fso.FileExists(strPath) then
     wshShell.Exec(strPath)
     end if

这样在安装完成后就可以执行这里面的vbs代码了，这里的功能是开启安装后的一个程序。

 

 

 

参考：

    Visual Studio Setup - projects and custom actions

    http://www.simple-talk.com/dotnet/visual-studio/visual-studio-setup---projects-and-custom-actions/

 

    This article describes the kinds of custom actions that can be used in your Visual Studio setup project.

Introduction

    It’s often necessary to add your own code to a Visual Studio setup project, which is accomplished using custom actions. Custom actions are in contrast to the standard actions that Windows Installer performs during an installation. Examples of standard actions include copying files and registering COM servers.

(You can download the code examples to go with this article using the link to the right of the title.)

Properties and CustomActionData

    To understand the use of custom actions, it’s important to know how to use Windows Installer properties, and in particular the CustomActionData property. To pass data into your custom-action code in Visual Studio setup projects, for example, you set the CustomActionData property to the data you want to pass into the custom action, and in your code you retrieve the CustomActionData property that contains the data. This is a common theme in the examples that follow.

Remember that the properties can be standard Windows Installer properties (TARGETDIR, VersionNT and so on), or properties that you created yourself, perhaps by using Search Target Machine as we saw in the previous article.

We’ll illustrate this CustomActionData idea with a simple VBScript custom action. This custom-action script will display the value of the CustomActionData property:

    msgbox Session.Property("CustomActionData")

    In the Visual Studio IDE for the properties of that custom action, you specify the value of your CustomActionData. In this example you’ll do this:

[OriginalDatabase]<>[TARGETDIR]<>[ComputerName] 

    You’re passing the value of this string to the CustomActionData property, and then in the custom-action code you get the value from the CustomActionData property. That is, you’re passing this data indirectly via the CustomActionData property.

The data consists of three Windows Installer properties. TARGETDIR is the primary installation folder, OriginalDatabase is the full path to the current MSI file being installed, and ComputerName is the name of the computer. Since angle brackets are not allowed in file names, they can serve as separators for parsing the combined properties and separating them out. So angle brackets are used for passing multiple property values into a custom action. Square brackets indicate that the actual value will be resolved at run time.

One caveat: Anti-virus software sometimes intercepts VBScript code and could prevent your custom action from working properly.

With the basics in place with regard to properties and CustomActionData, we’ll look at other types of custom actions.

 

 

----------

    You can’t get a property in VBScript with Session.Property("TARGETDIR") because of the behavior of Visual Studio’s deferred custom actions and CustomActionData. If Visual Studio custom actions were called during stage 2, you would be able to use properties like the one mentioned above, known as immediate custom actions in Windows Installer, but your files wouldn’t yet be installed on the system.