Deploying an SAP SQL Anywhere Database Application Using the Wi. X Toolset. This document describes how to deploy an SAP SQL Anywhere database alongside a Windows application using an installation package created with the Wi. X toolset. Introduction. There are already several blog posts about how to install SharePoint 2013, so I wont duplicate them here. But all of these posts are written assuming that you. This document describes how to deploy an SAP SQL Anywhere database alongside a Windows application using an installation package created with the WiX toolset. Oblivion Streamline 3.1 more. The Most Complete Guide to Visual Studio Toolbox Control Integration. Libor Tinka, Lead Developer, ComponentOwl. Contents. 1. Introduction 2. Prerequisites. Installation Package Netfx Msi Cannot Be FoundWindows Installer i. MSI is a popular method for packaging Windows applications for deployment. There are many ways to create MSI install packages and an easy method is to use the Windows Installer XML Wi. X Toolset. This set of tools provides developers with a quick way of packaging a Windows application for distribution and this document describes how to deploy an SAP SQL Anywhere database alongside a Windows application using an installation package created with the Wi. X toolset. There are other ways to achieve the same result, such as using other software such as Install. Shield or by copying the required files. If you interested in those methods, please refer to the document Embedding SAP SQL Anywhere 1. Commercial Applications Requiring a Database available here http scn. DOC 4. 35. 50. Prerequisites. The steps described in this document were tested under Windows XP and Windows 7 3. SAP SQL Anywhere 1. Simple batch files for integrating updates and drivers in Win7 Page 1 Windows 7 tools DriverPacks. Forum The support forum for the DriverPacksVisual Studio 2. Wi. X Toolset 3. 7. The ADO. NET sample application used in the Wi. X deployment packages requires. NET Framework 3. 5 to run. This document describes deployment for a Windows application. The steps will be similar for other operating systems. See the SQL Anywhere documentation for more information http dcx. Preparation. In this document well be deploying the SQL Anywhere ADO. NET Simple. Viewer sample application that is included in the SQL Anywhere installation. The Visual Studio source code is provided and must be compiled. For the Wi. X Toolset deployment method, a subset of database engine files must be assembled in your computer. The ADO. NET sample used in the deployed application requires SQL Anywhere. NET assemblies. For installation instructions on how to deploy SQL Anywhere. NET components, see the document http dcx. Please note that the SQL Anywhere. NET assemblies are installed automatically if Visual Studio is installed prior to SQL Anywhere. Building the Simple. Viewer Sample. Compile the sample application using Visual Studio Launch Visual Studio. Select File Open ProjectSolution. Open the Simple. Viewer solution file it is found at SQLANYSAMP1. SQL Anywhere 1. 6SamplesSQLAnywhereADO. NETSimple. Viewer. By default, this path resolves to C Documents and SettingsAll UsersDocumentsSQL Anywhere 1. SamplesSQLAnywhereADO. NETSimple. Viewer on Windows XP and C UsersPublicDocumentsSQL Anywhere 1. SamplesSQLAnywhereADO. NETSimple. Viewer on Windows Vista and Windows 7. Select the solution Simple. Viewer. sln and click OK. If running Visual Studio 2. You can go ahead and do that. Open Build Configuration Manager. Change the Active solution configuration to Release. Make sure the Simple. Viewer project shows Release as its selected configuration. Open Project Simple. Viewer Properties. Change Target framework to. NET Framework 3. 5. Chose Build Build Solution. This compiles the Simple. Viewer project as a. NET executable and places the file in the sample project directory inside the folder binRelease. Note that this sample application is compiled for. NET Framework 3. 5. If you wish to compile for other versions of. NET, simply change the target framework under project properties and add the appropriate version of SQL Anywhere ADO. NET data provider. Shut down Visual Studio. Preparing Database Engine Files. To simplify the process, it is recommended that you place all the files required to run the application inside a single folder. Create a folder C Simple. Viewer. Files and copy the necessary files there are 1. Application Executable 2. KB Simple. Viewer. Database 3. 7 MB demo. Database Server Binaries 2. MB dbcis. 16. dll, con. Server License File 1 KB dbeng. Connectivity Library 2. MB i. Anywhere. Data. SQLAnywhere. Database Utilities 8. KB dbelevate. 16. All these files are needed to deploy the Simple. Viewer sample application. Included are several connectivity libraries needed to establish a database connection with. NET applications and the demo database. In total this deployment including the database, database engine and application executable only requires approximately 3. MB of disk space. The Wix Toolset. The Wi. X Toolset builds Windows installation packages from XML source code. This document uses the Wi. X Toolset to copy the Simple. Viewer application and SQL Anywhere binaries, and create its ODBC data source. This document uses the Wi. X Toolset 3. 7, but is applicable to other versions as well. It is worth noticing that the installer package we are about to create does not have a user interface i. It also does not check whether the target computer already has the. NET Framework installed. If you would like to add a user interface and perform checks during the installation, please consult the Wi. X Toolset documentation for instructions on how to code those operations. For reference, the appendix at the end of this paper has a code listing that does exactly that. Building the Installer. Launch Visual Studio 2. On the left panel, select Installed Templates Windows Installer XML and choose Setup Project. Type a name e. g. Simple. Viewer. Installer and a location for the project e. C Simple. Viewer. Installer. Make sure the project is using. NET Framework 3. 5. Note if you do not see the Windows Installer XML project template, then you do not have the Wi. X Toolset installed. Please install it before proceeding. In Solution Explorer, right click on Simple. Viewer. Installer Add Existing Item. Browse to the Simple. Viewer. Files directory you created earlier. Select all the files and click the Add button. Open the file Product. Modify the Product start tag to change the Name, Language, version, Manufacturer, and the Upgrade Code. Product. IdNameSimple. ViewerLanguage1. Version1. ManufacturerSAP Upgrade. Code8. 81e. 72. Important For a 6. Package tag to include the Platform attribute and set it to x. Package. Installer. Version2. 00CompressedyesInstall. Scopeper. Machine Platformx. Enter Simple. Viewer as the product name in Major. Upgrade tag. lt Major. Upgrade. Downgrade. Error. MessageA newer version of Simple. Viewer is already installed. Modify the directory tag as follows to deploy the application to C SQL Anywhere DemosSimple. Viewer. lt Directory. IdTARGETDIRNameSource. Dir   lt Directory. IdSQLAnywhere. DemosNameSQLAnywhere Demos      lt Directory. IdINSTALLFOLDERNameSimple. Viewer    lt Directory lt Directory For this project, we will create two components, Product. Component and Demo. Data. Source. Since we will only create components, delete the Component. Group that is created by default. Modify the Feature tag as follows to reference to these two components. Feature. IdProduct. FeatureTitleSimple. Viewer. InstallerLevel1   lt Component. Ref. IdProduct. Component    lt Component. Ref. IdSA1. 6Demo. Data. Source lt Feature For each component, it is necessary to add a GUID attribute. To create a GUID in Visual Studio, click on Tools Create GUID. Change the Format to Registry Format and click on Copy. Add a new Fragment to contain the Product. Component element. Installing Dotnet Framework 1. Windows 7 beta edition. When I installed Windows 7 beta version on my laptop, it was a relief as i was fed up with vista. The first problem popped while I tried to install Daemon Tools. For people who still have problem installing Daemon Tools, try installing Virtual Clone Drive. It seems Daemon Tools dont have support for beta editions. The next problem arose when I tried to install dotnet framework 1. When I tried doing that, the following error showed up. If user click OK, the installation of. NET 1. 1 will be cancelled, while clicking CANCELproduces another error message similar to below Reg. Svcs. exe No debugger found. Registered JIT debugger is not available. An attempt to launch a JIT debugger with thefollowing command resulted in an error code of 02 s. Please check settings. Microsoft. NET Framework 1. SP1Service Pack 1 has resolved the issue. However, Microsoft does not provide download to standalone. NET Framework 1. 1 installer that integrated with SP1. To fix this, we need to follow the following steps, which is called slipstreaming. We need to sliptstream. NET Framework 1. 1 SP1 into. NET Framework 1. 1 installer, so that both the. NETFramework and the Service Pack can be installed at the same time. Follow these steps 1. Create a new folder named Dot. Net in C drive. The path i used was C Dot. Net 2. Download Microsoft. NET Framework 1. 1 Redistributable Package dotnetfx. Makesure the setup file is saved as dotnetfx. Download Microsoft. NET Framework 1. 1 Service Pack 1 NDP1. KB8. 67. 46. 0 X8. Rename the file to dotnetfxsp. Copy both installation files into the same directory i. C Dot. Net. 5. Open Command Prompt as Administrator. Change to the directory where the two installation files are stored, ie C Dot. Net. 7. Run the following commands one by one. TARGETDIRC Dot. Net Click on Yes and wait for this dialog which says installation complete. Xp C Dot. Netnetfxsp. Dot. Netnetfx. msi p c Dot. Netnetfxsp. msp Wait for the installer to disappear automatically. Install Microsoft. Net Framework 1. 1 with slipstreamed Service Pack 1 by running netfx. Dotnet Framework 1.