New Partner kit Setup

Setup New Partner Kit on framework version 5.x  

VIENNA Advantage partner kit 

VIENNA Advantage partner kit allows module base development for that VIENNA provides three projects in solution. 

1. ViennaAdvantage 

2. ViennaAdvantageSvc 

3. ViennaAdvantageWeb 

                                                                                 Figure 1.7 

1. ViennaAdvantage 

This project contains 'Areas' folder which already contains four areas VIS, ViennaBase, ViennaAdvantage and Market. Here VIS and ViennaBase contains base JavaScript libraries, and stylesheets.  Market Area is used to install new modules and update existing modules from Vienna Advantage Market. ViennaAdvantage is an Area in which user develops required functionality. 

If user wants to create new module, then user has to rename ViennaAdvantage Area to Module Prefix Code(MPC) provided by VIENNA then rename ViennaAdvantage Area Registration file to MPC Area Registration and make changes in that file according to instructions written in that file. 

                                                                                 Figure 1.8 

For example if MPC name is ‘VAT’ then file name become VATAreaRegistration. 

1. ViennaAdvantageSvc 

                                                                                 Figure 1.9 

This project is business logic layer and contains business logic classes. This project is referenced in ViennaAdvantage. All Model classes of newly created module comes under Model Folder and processes logic will come under Process folder.  

Rename the dll of ViennaAdvantageSvc to MPCSvc
 

1. ViennaAdvantageWeb.  

It is the hosting project that one can finally deploy for hosting in the IIS, which contains reference of both ViennaAdvantage and ViennaAdvantageSvc projects. 

                                                                                  Figure 2.0 

ViennaAdvantage partner kit can be used for two different purposes.  

1. One way is that partner kit can modify logic of core product (ViennaAdvantage Product). For this, create copy MClass OR Process of core product. Change namespace of class to ViennaAdvantage. For forms and callouts copy and paste required JavaScript files of core product in Script folder of ViennaAdvantage Area, and modify files according to requirements. 

2. Second way is that you work in module specific project in ViennaAdvantage and ViennaAdvantageSvc. 

Create your own MClasses, XClasses, Callout classes and put in module specific project and keep the same structure as we provide in the product projects. In Module Creation topic, you can find steps to create module in detail.  

The benefit of work in module or Vienna Advantage (Vienna Advantage PartnerKit) over directly work in product files is that in former approach, you can list and download Module from the Vienna Market. Second, if you directly update product files and host the application with your custom update product dll. After that you update Vienna Advantage from the Vienna Market then it will replace the product specific dll and your extended work will be lost. But if you work in your specific module then dll, related to your module will only update when re-install, update specific module from Vienna market.