Welcome to MSDN Blogs Sign in | Join | Help

WEPOS and POS for .NET Team Blog

Helpful information and examples on how to use WEPOS and POS for .NET
Installing POS for .NET from Your Installer

Version 1.12 of the installer for POS for .NET is available for download here: http://www.microsoft.com/downloads/details.aspx?FamilyID=EAAE202A-0FCC-406A-8FDE-35713D7841CA&displaylang=en

 

The download from this website contains a self-extracting archive.  Once the archive is downloaded and extracted, you will find the following content:

 

Setup.exe - This is the installer setup program for POS for .NET.

1033 - This folder contains language localization files for the setup.exe installer.

Documentation - This folder contains release notes used by the setup.exe installer.

POSFor.NET - This folder contains the POSfor.NET.msi and related files used by the setup.exe installer.

Res – This folder contains resources used by the setup.exe installer.

VCRuntime – This folder contains the installer for the Visual C runtime.

 

If you would like to install POS for .NET on your local system, simply use the Setup.exe program to perform the installation.  When you run the installer, you will be presented with a number of installation options:

 

      Typical – Installs the POS for .NET runtime components and the PosDM command line tool

      Complete – Installs POS all components (runtime, PosDM, and SDK)

      SDK – This installs the SDK documentation and sample code

 

The installer can also be used from the command line or to perform silent installs from within your own installer.  To see a list of available options, run the setup.exe with the /? option from the command line. The most commonly used options include:

 

      /ADDLOCAL [feature list or “ALL”] – silent install of the specified features

      /REMOVE [feature list or “ALL”] – uninstall the specified features

      /REPAIR [feature list or “ALL”] – silent repair of an installation.

 

The “/ADDLOCAL” feature will add the components specified (if they are not already installed) using a silent install.  The feature list is a common separated list and may include one or more of the following options:

 

      Runtime – Indicate the POS for .NET runtime

      Posdm – Indicates PosDM management tools

      SDK – Indicates the SDK

      ALL – Specifies all of the above components

 

For example, to perform a typical installation one could invoke setup from within their own installation program with the following options:

     

      Setup.exe /ADDLOCAL Runtime,Posdm

 

 

Other MSI arguments (such as /s for silent install) may also be passed on the command line.

 

It is recommended that when installing POS for .NET from another installer to use the setup.exe instead of the MSI.  This will ensure that all dependent components (such as the C runtime) are installed and properly configured.

 

 - Sylvester

 

Posted: Friday, June 20, 2008 11:17 AM by posblog
Filed under: ,

Comments

glenharvy said:

Is there a method I can use in my project to detect whether POS for dot Net is already installed?

# July 4, 2008 8:15 AM

pksandbox said:

I know this isn't the correct forum to ask this question. But is it possible to send a beep to a POS printer like EPSON T88 TIII?

# July 6, 2008 4:03 PM

glenharvy said:

As good a place as any to ask .... what is the address of a forum that we can ask these questions and at least get peer-to-peer support.

TIA.

# July 6, 2008 10:19 PM

posblog said:

If you use our installer, you do not need to check if POS for .NET is already installed, as the installer will do this for you.  However, there is a ProductVersion key in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\POSfor.NET\Setup that indicates the version of the product installed (if installed).

- Sylvester

# July 7, 2008 10:52 AM

posblog said:

For general community support questions, there is a usenet newsgroup available (microsoft.public.windows.embedded.pointofservice) from Microsoft's usenet server.  

The newsgroup is also available via web:

http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.embedded.pointofservice

As to the question about getting a printer to beep, there are no commands in UnifiedPOS specific for doign this with a printer.  It may be possible via directIO - you would need to find out from your printer maker as this is would be device specific.  It might be better to just have the computer beep.

# July 7, 2008 10:58 AM
Anonymous comments are disabled
Page view tracker