Creating addon installer without BIDE

Hi all
i would like to know how can an installer project can be created for an addon without the use of the BIDE tools
appreciate the help
Yoav

Yoav,
The SAP Business One SDK Help Center Documentation covers "packaging" your solution in very good detail. You should review this. In the SDK Help Center documentation, look under "Package and Deployment". You can also search this forum and there are many posts on this subject.
Eddy

Similar Messages

How to create a package without BIDS in Microsoft SQL Server Management Studio

I have inherited some SSIS packages that I found I can edit by opening the .dtsx file in my local copy of Microsoft SQL Server management studio. I then get Control Flow tab, Data Flow tab etc. I can add or change or delete any of the control
or data flows. I have found that if I use the same path to the local file where the packages are stored that exists on the server, I can edit the dtsx file on my local machine and copy the dtsx file to the server into the same directory structure and
sucessfully execute the package on the SQL 2008 server.
I have VS 2010 installed. I have read that I have to install VS 2008 to use BIDS from within VS. However, this has not worked out very well. Since I can basically create a new package by deleteing all of the control and data flows from
an existing package, I am in pretty good shape. However, I would just like to know if there is a way to create a new dtsx file from within Microsoft SQL Server management studio. Also one thing I have not been able to change is the event handler
name or package exploration name....it is just an annoyance since it does not cause any problems, just would like to be able to rename it.

Hi Fred,
We cannot develop SSIS package in SQL Server Management Studio. If we use SQL Server Import and Export Wizard, we can save it as a package but the package is rather simple.
We use Business Intelligence Development Studio (BIDS) or SQL Server Data Tools (SSDT) to develop SSIS packages. To develop SSIS 2008 packages, we must use BIDS installed by SQL Server 2008, and the BIDS 2008 can only be integrated with Visual Studio 2008.
To develop SSIS 2012 packages, we use the SSDT installed by SQL Server 2012 which uses Visual Studio 2010 shell and can only be integrated with Visual Studio 2010.
Different versions of SSIS package have different package formats/schemas. If you can create SSIS packages project in you Visual Studio 2010, it means that you have installed SSDT already, and the packages you design are SSIS 2012 packages. If you open and
eidt SSIS 2008 packages in you Visual Studio 2010, the packages will be upgraded to SSIS 2012 package format. SSIS 2012 packages cannot be downgraded to SSIS 2008 packages or deployed to SSIS 2008 server.
Regards,
Mike Yin
TechNet Community Support

Create installer without labview

Hi,
Is it possible to create an installer without LabVIEW? I am supporting Windows 2000 through 7 and the versions of NI software varies with each OS, specifically when dealing with oscilloscopes running Windows due to VISA conflicts.
The two main problems I have with creating installers with LabVIEW (Application Builder):
1) Windows 2000 requires the Product Framework before 2.8.0. This makes it impossible for installers to run on Windows 2000 that require product installation newer than 2.8.0 which is basically every installation for Windows 7.
2) As far as I am aware, the required software has to be installed on a local machine first before creating an installer. Then you navigate to the Additional Installers section when creating an installer to add to the installation. The location path will point to the orignal CD drive or location it was installed from on the local drive. I don't see why this required. Why can the installer be created directly from the extracted files without it being installed on machine?
Thanks
Solved!
Go to Solution.

Wow guys, thanks for two blatent insults. If you don't have anything nice to say don't say it at all.
A little further explaination:
Supporting and maintaining Windows 2000 in 2014, I agree, is cumbersome. However, you have to realize these oscilloscopes that run Windows 2000 in 2014 still cost upwards of $8,000 to replace and the operating system cannot be upgraded. Why do they still cost so much? Because they are very useful tools. And new ones cost $20,000 to $30,000. I don't think that this effort is "los[ing] [the company's] ability to make a profit".
For those of you that are interested in the orignal question posted here is my solution.
I used SFX Builder (http://sourceforge.net/projects/s-zipsfxbuilder/) to bundle NI's software into a single executeable file. Heres the steps:
1) Download all necessary NI software
2) Download SFX Builder
3) Download 7-zip (http://www.7-zip.org/)
1) Extract all NI software into a single folder and use 7-zip to compress into a .7z archive
2) Open SFX Builder and add the .7z archive to the File tab
3) You can easily set the path of extraction to anywhere on the computer, the temp (%temp%) is the most useful
4) On the Tasks tab click the add/plus button and select Run Program, then enter the path where the extraction happened, here is an example
5) Easy peasy!

B1DE (AddOn Installer) for 64 bit server

Hi All,
I have a problem. One of my client has a 64 bit server. AddOn installation created with B1DE for SAP 2007 doesn't work on that server. After running SAP AddOn is trying to install, and then there is an error. Is there any way to create AddOn installation files that work on 64 bit server?
Regards
Hmg

Both Robin and Owen are right... You need to run your code as forced 32 bit.
The reason is the following:
- A default project in Visual Studio is compiled as "Any CPU"
   - Any CPU means that you code will be executed as 32bit on a 32bit machine, and 64bit on a 64bit machine.
   - The Any CPU option is great for pure .NET (since all parts of it can run 32bit and 64bit)
   - In case of the SAP SDK and the AddonInstaller.dll, these are COM-based unmanaged code
      - If such unmanage code is not written to work with 64 bit, problems like yours can occur (this happens not only for SAP SDK... Tons of API out there have the same problems)
- If you change the Any CPU option to the x86 option, you will force 64 bit mashines to run your code in "simulated" 32bit (Don't worry.. it is quite fast and gives no problems)
We are you this with our 64 bit customers and without any problems...
Lastly, if you wish to know more about this please hear the following podcast that describes the issue in detail (A good listen): http://www.dotnetrocks.com/default.aspx?showNum=341
/Rasmus

How can I double-click a file to open it in default app in my Visual Studio project without creating an installer?

I have an app with code to open a file by double-clicking on it. The app in my Visual Studio project file should start automatically and then open the file automatically. I double-click on the file, then look for the app in my solution folder (I choose the
.exe in the Debug folder). Am I choosing the correct .exe file?
What I'm trying to do is test some code I wrote that will open the associated file type when I double click on it, as opposed to creating an installer, installing the app and then double-clicking on the file to see if it will open in the associated app automatically.

Hi dudefromthebronx,
Yes, I think you could doubt click the .exe file in your local machine.
Of course, maybe you could get it in Bin\Debug or Bin\Release folder, it is related to the current project settings.
But we would know some differences between them:
http://stackoverflow.com/questions/11600162/difference-between-bin-debug-and-bin-release
https://social.msdn.microsoft.com/Forums/en-US/0cde96e6-8dd8-4aa9-adcf-d7f45da13b66/debug-bin-release-folders?forum=vbide
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Creating installer without Distrubution of MAX

I am creating installer but with it MAX shortcut is getting loaded on desktop.How to avoid MAX on desktop while creating installer using LABVIEW 8.5?

When you create the installer, select to export
the MAX configuration so that will be included in your installer and exclude MAX as part of the installer. You should find this in additional installer options while building.
Message Edited by muks on 02-22-2010 04:07 PM

LabView 2012 32-bit, creating an installer to run on Windows 7 64-bit

Hello I have the full development LabView system installed on a 32-bit PC running Windows XP. I'm trying to create in an installer that will be ran on a 64-bit machine running Windows 7. I'm able to create the installer, but when I try to run the installer I get on the Windows 7 64-bit machine I get:
"The version of this file is not compatible with the version of Windows you’re running. Check your computer’s system information to see whether
you need an x86 (32-bit) or x64(64-bit) version of the program, and then contact the software publisher."
I tried changing the compatibility mode under properties, without any success. What else can be causing this issue. Thanks.

There should be abolutely no problem installing or running a 32 bit LabVIEW executable in windows 64 bit. I do it all the time.
There must be something else. can you give a bit more details about your application? Are you including the runtime engine in the installer?
"I tried changing the compatibility mode under properties, without any success"
What exactly did you do here?
LabVIEW "full" does not allow building applications or installers unless you also have the application builder. I guess you have that.
LabVIEW Champion . Do more with less code and in less time .

How to create a domain without using the root user in Sunone Server

Hi,
I am having one requirement to create a domain without using root user in sunone application server 8.1. Does any body know the solution?
Message was edited by:
SPBP

Hi,
If you are using file-based installation, you can install as non-root user and create domains as usual. You can use asadmin command available at <AS_INSTALL>/bin to do this.
ex: ./asadmin create-domain domaindir /tmp/justfortest adminport 4850 --adminuser admin domain_nonroot_test
Did you face any problem doing this in non-root. Unless you have write permissions in domaindir, you won't be facing any problem.
Hope this clarifies your question.
Thanks,
-Balaji.

AddOn installer

Hello,
I am trying to create an installer for my add-on. I've seen the B1DE Professional Installer and I belive I can use it what it has generated and modify it according to my needs. But, I need to create some tables, user defined tables and user defined fields in the database that is requiesting the install. Do I do that in the Install method and how (I know how to create tables and userdefined tables, I just don't know how can you find out in which database)?
Thank you,
Irina

Hi Irina,
I think the usual method is to build this functionality in to the add-on itself rather than the installer. If you built it in to the installer, it would be difficult to install the add-on on a site with multiple companies and particularly on a site where a new company is created after the add-on was installed.
There are probably a few ways to do this but here's the way I see implemented most often in third-party and SAP add-ons:
1) You install the add-on as normal (ie using the standard ard and exe files in Add-on Administration)
2) When you start the add-on, the add-on will perform a check to see if all the required UDFs and UDTs exist in the current company.
3) If fields are missing, automatically create them. Personally I'd prefer the add-on to prompt me before this action takes place (but most add-ons just go ahead and create the fields without prompting )
4) Once all UDFs and UDTs have been created, the add-on works as normal.
The add-on perfoms the check every time it is started but, after the first time, all objects are found so this step is skipped.
Kind Regards,
Owen

AddOn installer for C# in SAP 2004

Hi,
I have a question. Is there an AddOn Installer for C# in SAP 2004? Or do I have to write it by myself?
Regards,
Hmg

Hi Szymon,
You can use B1DE package you can donwload for free from SDN. It will create an installer in Vb.NET but it is very easy to adapt the code to C#.
Regards
Trinidad.

Problem creating Addons

Hi,
I've probably missed something obvious, but I can't see mto get this to work.
Using the B1DE, I created an Addon project. Made no changes to the code.
Then I also used the B1DE to create an installer for this Addon.
Compiled both, ran the AddonRegDataGen batch file, and then installed the Addon in SAPusing this ARD.
And it worked, no problem.
Now, I made a change to the Addon code.
Then recompiled it.
Then ran the AddonRegDataGen again to get a new ARD file.
Removed the existing Addon from SAP, and tried to install the new version.
It installs fine, but when I try to run it, i get
"wrong executable digital signature for add-on"
I'm sure I missed something, but what?
Thanks in advance!

Hi David,
Thanks for the advice.
That was the problem - I did not realise that I would have to copy the new .exe for the addon into the "AddonFiles" folder in the INSTALLATION project each time I rebuilt the addon (since when you make the installer you point it at the output folder of the addon project).
Anyway, its working now so thank a million!
Regards,
Stephen

Addon Installer - Wrong Signature

Hello Experts,
I create an Addon for my company and the installer at the end of installation a error message tells me: Wrong Signature...
SAP Version: 8.82 PL11
Visual Studio: 2010
B1DE
I created a installer wiht B1DE and the ARD with the tool that is within the SAP DVD
I also try to create with INNO SETUP but the problem there sometimes its the last call to EndInstal gave an error.
Please help me ...

Hi Cristian,
When you use B1DE, the ARD is automatically generated, you dont need to generate 'ard' manually.
Check Creating and Registering Add-on on SAP B1 on how to generate via B1DE
When the ARD tools generate the 'ard' file, it get a signature from the .exe installer file.
you will get the message if the .exe installer file is not the same file you used to generate the 'ard' file.
Regards
Edy

Addon Installer exception

hey
i am still a rooky in sbo and SAp in general.
i am creating the addon:blanket agreement that i find in the SDK help center
well the module blanket is running correctly.
but when i create the addon installer and try to run t get the exception(from french):"the object instance is not assigned to an object".
i now the meaning of message but i dont how to solve it.
if you have any idea pls let me know thank you

This the script of my installer hope sombody can help.
ps:when i check the install directory after the failer of the installation i foun the blanketagreement temp file.
'the addon intallation script
Public Class Form1
    Inherits System.Windows.Forms.Form
#Region " Code généré par le Concepteur Windows Form "
    Public Sub New()
        MyBase.New()
        'Cet appel est requis par le Concepteur Windows Form.
        InitializeComponent()
        'Ajoutez une initialisation quelconque après l'appel InitializeComponent()
    End Sub
    'La méthode substituée Dispose du formulaire pour nettoyer la liste des composants.
    Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)
        If disposing Then
            If Not (components Is Nothing) Then
                components.Dispose()
            End If
        End If
        MyBase.Dispose(disposing)
    End Sub
    'Requis par le Concepteur Windows Form
    Private components As System.ComponentModel.IContainer
    'REMARQUE : la procédure suivante est requise par le Concepteur Windows Form
    'Elle peut être modifiée en utilisant le Concepteur Windows Form.
    'Ne la modifiez pas en utilisant l'éditeur de code.
    Friend WithEvents Label1 As System.Windows.Forms.Label
    Friend WithEvents Label2 As System.Windows.Forms.Label
    Friend WithEvents chkDefaultFolder As System.Windows.Forms.CheckBox
    Friend WithEvents txtDest As System.Windows.Forms.TextBox
    Friend WithEvents chkRestart As System.Windows.Forms.CheckBox
    Friend WithEvents cmdInstall As System.Windows.Forms.Button
    <System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
        Me.Label1 = New System.Windows.Forms.Label
        Me.Label2 = New System.Windows.Forms.Label
        Me.txtDest = New System.Windows.Forms.TextBox
        Me.chkDefaultFolder = New System.Windows.Forms.CheckBox
        Me.chkRestart = New System.Windows.Forms.CheckBox
        Me.cmdInstall = New System.Windows.Forms.Button
        Me.SuspendLayout()
        'Label1
        Me.Label1.Location = New System.Drawing.Point(88, 24)
        Me.Label1.Name = "Label1"
        Me.Label1.Size = New System.Drawing.Size(200, 23)
        Me.Label1.TabIndex = 0
        Me.Label1.Text = "Blanket Addon Installer"
        'Label2
        Me.Label2.Location = New System.Drawing.Point(8, 80)
        Me.Label2.Name = "Label2"
        Me.Label2.Size = New System.Drawing.Size(200, 23)
        Me.Label2.TabIndex = 1
        Me.Label2.Text = "Installation Folder"
        'txtDest
        Me.txtDest.Location = New System.Drawing.Point(8, 120)
        Me.txtDest.Name = "txtDest"
        Me.txtDest.Size = New System.Drawing.Size(288, 20)
        Me.txtDest.TabIndex = 2
        Me.txtDest.Text = "TextBox1"
        'chkDefaultFolder
        Me.chkDefaultFolder.Location = New System.Drawing.Point(8, 160)
        Me.chkDefaultFolder.Name = "chkDefaultFolder"
        Me.chkDefaultFolder.TabIndex = 3
        Me.chkDefaultFolder.Text = "CheckBox1"
        'chkRestart
        Me.chkRestart.Location = New System.Drawing.Point(8, 184)
        Me.chkRestart.Name = "chkRestart"
        Me.chkRestart.TabIndex = 4
        Me.chkRestart.Text = "CheckBox2"
        'cmdInstall
        Me.cmdInstall.Location = New System.Drawing.Point(112, 224)
        Me.cmdInstall.Name = "cmdInstall"
        Me.cmdInstall.TabIndex = 5
        Me.cmdInstall.Text = "Button1"
        'Form1
        Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13)
        Me.ClientSize = New System.Drawing.Size(320, 270)
        Me.Controls.Add(Me.cmdInstall)
        Me.Controls.Add(Me.chkRestart)
        Me.Controls.Add(Me.chkDefaultFolder)
        Me.Controls.Add(Me.txtDest)
        Me.Controls.Add(Me.Label2)
        Me.Controls.Add(Me.Label1)
        Me.Name = "Form1"
        Me.Text = "SAP Business One"
        Me.ResumeLayout(False)
    End Sub
#End Region
    Friend WithEvents FileWatcher As New System.IO.FileSystemWatcher
    'EndInstall - Signals SBO that the installation is complete.
    Declare Function EndInstall Lib "AddOnInstallAPI.dll" () As Int32
    'SetAddOnFolder - Use it if you want to change the installation folder.
    Declare Function SetAddOnFolder Lib "AddOnInstallAPI.dll" (ByVal srrPath As String) As Int32
    'RestartNeeded - Use it if your installation requires a restart, it will cause B1 application to close itself after the installation is complete.
    Declare Function RestartNeeded Lib "AddOnInstallAPI.dll" () As Int32
    Private strDll As String ' The path of "AddOnInstallAPI.dll"
    Private strDest As String ' Installation target path
    Private bFileCreated As Boolean ' True if the file was created
    Private Sub ExtractFile(ByVal path As String)
        Dim AddonExeFile As IO.FileStream
        Dim thisExe As System.Reflection.Assembly
        thisExe = System.Reflection.Assembly.GetExecutingAssembly()
        Dim file As System.IO.Stream
        file = thisExe.GetManifestResourceStream("AddOn.BalnketAgreement.exe")
        ' Create a tmp file first. After the file is extracted change the
        ' extension to exe.
        AddonExeFile = IO.File.Create(path & "BlanketAgreement.tmp")
        Dim buffer() As Byte
        ReDim buffer(file.Length)
        file.Read(buffer, 0, file.Length)
        AddonExeFile.Write(buffer, 0, file.Length)
        AddonExeFile.Close()
        ' Change file extension to exe
        Try
            IO.File.Move(path & "BlanketAgreement.tmp", path & "BlanketAgreement.exe")
        Catch
            IO.File.Delete(path & "BlanketAgreement.tmp")
            IO.File.Move(path & "BlanketAgreement.tmp", path & "BlanketAgreement.exe")
        End Try
    End Sub
    Private Sub Install()
        Environment.CurrentDirectory = strDll ' For Dll function calls will work
        If chkDefaultFolder.Checked = False Then ' Change the installation folder
            SetAddOnFolder(txtDest.Text)
            strDest = txtDest.Text
        End If
        If Not (IO.Directory.Exists(strDest)) Then
            IO.Directory.CreateDirectory(strDest) ' Create installation folder
        End If
        FileWatcher.Path = strDest
        FileWatcher.EnableRaisingEvents = True
        ExtractFile(strDest) ' Extract add-on to installation folder
        While bFileCreated = False
            Application.DoEvents()
            'Do not continue running until the file is copied...
        End While
        If chkRestart.Checked Then
            RestartNeeded() ' Inform B1 that restart is needed
        End If
        EndInstall() ' Inform B1 that the installation has ended
        MessageBox.Show("Finished Installing", "Installation ended", MessageBoxButtons.OK, MessageBoxIcon.Information)
        Windows.Forms.Application.Exit() ' Exit the installer
    End Sub
    Private Sub frmInstall_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        ' The command line parameters, separated by '|' will be broken to this array
        Dim strCmdLineElements(2) As String
        Dim strCmdLine As String     ' The whole command line
        Dim NumOfParams As Integer   'The number of parameters in the command line (should be 2)
        NumOfParams = Environment.GetCommandLineArgs.Length
        If NumOfParams = 2 Then
            strCmdLine = Environment.GetCommandLineArgs.GetValue(1)
            strCmdLineElements = strCmdLine.Split("|")
            ' Get the installation destination folder
            strDest = strCmdLineElements.GetValue(0)
            txtDest.Text = strDest
            ' Get the "AddOnInstallAPI.dll" path
            strDll = strCmdLineElements.GetValue(1)
            strDll = strDll.Remove((strDll.Length - 19), 19)   ' Only the path is needed
        Else
            MessageBox.Show("This installer must be run from Sap Business One", "Incorrect installation", MessageBoxButtons.OK, MessageBoxIcon.Exclamation)
            Windows.Forms.Application.Exit()
        End If
    End Sub
    Private Sub chkDefaultFolder_CheckedChanged(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles chkDefaultFolder.CheckedChanged
        txtDest.Enabled = Not (chkDefaultFolder.Checked)
    End Sub
    Private Sub FileWatcher_Renamed(ByVal sender As Object, ByVal e As System.IO.RenamedEventArgs) Handles FileWatcher.Renamed
        bFileCreated = True
        FileWatcher.EnableRaisingEvents = False
    End Sub
    Private Sub cmdInstall_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles cmdInstall.Click
        Install()
    End Sub
End Class
thanks for your help.

How to create an installable

Hi everybody,
I have developped an aplication with forms 6.i, it contains 65 forms, 1 library, 1 menu, 20 reports, now i need to deliver it to the customer, and i need create an installable that contains those fmx, plx, mmx and pdf files, and contains a runtime for forms and report (ifrun60.exe and rwrun60.exe) also, it will be very good if i can create an executable file , like SETUP.EXE, and this file install my application.
I used the project builder but i didn't get any result.
Can you tell me how to do it.
thanks in advance.

Hi,
the most efficient way of deploying Developer runtime is described in my paper at http://www.orafaq.org/papers/runfrmwp.pdf .
It's pretty much a trivial hack, not supported by Oracle but it works without a hitch.
So far it's the fastest possible deployment option for all C/S version od Developer.
regards,
Ales

Creating Runtime Installer for VI with VISA Read VI

Greetings Fellow Users,
Please let me know which 'ADDITIONAL INSTALLERS' the LabView RunTime engine requires in order to run a VI that reads from the built-in serial port (COM 1) of a Windows XP PC. For instance, I include LabView Run-Time engine 8.0.1 to creat an installer for the VI. If I want to load and run this .exe on a PC that has no other NI software, do I need to include any of the following as 'ADDITIONAL INSTALLERS':
->NI-SERIAL 1.8?
->NI-VISA RUNTIME 3.4?
->NI-DAQmx 8.0?
What does the NI-VISA RUNTIME do anyways? Also, when I do include some of these, I have to dig out my LanVIEW installations CDs and they are loaded from teh D:\. What is the cleanest way to load these onto my HDD so that LabView will select these automatically.
Thank you.

FLT CTRL 6 wrote:
Greetings Fellow Users,
Please let me know which 'ADDITIONAL INSTALLERS' the LabView
RunTime engine requires in order to run a VI that reads from the
built-in serial port (COM 1) of a Windows XP PC. For instance,
I include LabView Run-Time engine 8.0.1 to creat an installer
for the VI. If I want to load and run this .exe on a PC that has
no other NI software, do I need to include any of the following as
'ADDITIONAL INSTALLERS':
->NI-SERIAL 1.8?
->NI-VISA RUNTIME 3.4?
->NI-DAQmx 8.0?
What does the NI-VISA RUNTIME do anyways? Also, when I do
include some of these, I have to dig out my LanVIEW installations CDs
and they are loaded from teh D:\. What is the cleanest way
to load these onto my HDD so that LabView will select these
automatically.
Thank you.
->NI-SERIAL 1.8?
This is the driver used for serial port controller boards and
interfaces from NI. You do not need that software when trying to access
built in serial ports or ports on interface cards from other
manufactureres than NI.
->NI-VISA RUNTIME 3.4?
This is the software LabVIEW uses to talk to all kinds of IO interfaces
including serial ports. This is what you will need. Runtime means it is
a stripped down version without LabVIEW, C, VB, Delphi and whatever
development bindings and examples etc.
->NI-DAQmx 8.0?
This is the software driver for NI data acquisition devices (analog IO, digital IO, counter , timers).
These are all to be considered drivers and (very maybe apart from
NI-VISA) it is usually not a very good idea to include drivers into the
application installer. If you use them your user is likely to have
bought his own kind of hardware and no matter if he happens to have
bougt the newest SuperPCI interface board with 256 ultra-high-speed
serial ports over wireless connections or an old standard PCI board
with 2 RS-232 interfaces they both will have come with a CD that is
appropriate for that device, whereas the NI-Serial driver you included
is only appropriate for NI serial boards that are still AND already
sold at the moment when that driver was released. The same applies for
any other driver software.
NI_VISA being able to connect to standard built-in serial ports could
be considered different but it isn't really. I have included NI-VISA on
application installers in the past only to find out that the included
NI-VISA version did not run or not run reliably on newer machines with
new OS versions, so we had to point the customer to the NI site to
download the newest version anyhow, or even burn a new CD with updated
NI-VISA versions and express ship it.
Basically including any kind of driver software in the application
installer may seem like a good idea but will usually cause lots of
additional support after some time due to incompatibilities with newer
OS versions, new hardware, etc.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Creating addon installer without BIDE

Similar Messages

Maybe you are looking for