uniPaaS2.0 is a native .NET application, so in order to run uniPaaS on your machine, you must have .NET framework installed on your machine with one of the following configurations:
• Both .NET Framework V2.0 SP1 and Microsoft Visual C++ 2008 Redistributable.
You can install them by running the NetFx20SP1_x86.exe and VCRedist_x86.exe files from the Scripts\RIA folder.
• .NET Framework V3.5 (or above)
Network Installation
The .NET runtime security policy (by default) disables code from running if it exists on a network drive. To run uniPaaS from a network drive you need to adjust your security policy.
This can be done via the Microsoft .NET Configuration tool or by running the following command:
c:\Windows\Microsoft.NET\Framework\v2.0.50727\caspol.exe -machine -addgroup All_Code -strong -file <path>uniRTE.exe -noname -noversion FullTrust -name uniPaaS_Assemblies_Access -description "Code group granting trust to uniPaaS assemblies"
This command needs to be executed only once in each of the computers.
You can also add a –silent key for a silent installation.
Online Changes
In uniPaaS V2.0, the Online GUI is based on the .NET framework instead of Win32.
The .NET framework does not support all the appearances and control behaviors that were supported in previous versions, so there is a change in the uniPaaS Runtime appearance as well.
For a full list of changes, refer to the What's Different in uniPaaS V2.0 help topic.
Some of the major enhancements are described below.
.NET Integration in Online and Batch Tasks
.NET Integration was introduced to RIA applications in uniPaaS V1.8.
With this release you can enhance your Client/Server application offering by easily embedding and integrating any .NET control or assembly in your Online and Batch tasks.
For more information on how to add and manipulate .NET modules, see the .NET Tutorial sample installed with uniPaaS.
New Features, Feature Enhancements and Behavior Changes
uniPaaS V2.0
6
Online MDI
The Online Runtime MDI Frame is now defined as any other form in the Main Program (similar to the Rich Client MDI Frame).
The benefit of this change is the centralizing of all the form properties from the different locations they were once defined in, into a single location.
The MDI can be disabled by defining Open Task Window = No in the Main Program properties.
Online Frameset
Splitter forms are now defined using a frameset form for an Online task (as in Rich Client tasks) instead of using a Splitter form.
User State Persistency in Online Tasks
The Online task’s form state persistency is now defined as a simple Yes/No