ACE FILE Sample Clauses

ACE FILE. In Eiffel for .NET you can specify whether the Eiffel compiler should generate an exe (executable) or a dll (Dynamic Link Library) assembly. The associated option in the Ace file is msil_generation_type. The Ace file is a central control file for Eiffel projects where - among other things - the compilation options of the project is described. The option msil_generation_type (“exe”) forces the compiler to create an executable; the declaration msil_generation_type (“dll”) enforces the creation of a dynamic link library. The class CW_LACE_GENERATOR creates an Ace file that the compiler uses to create a .NET assembly. It sets the option in the Ace file according to the extension of the input assembly. If the original assembly file has the extension “dll” the compiler will generate a dll assembly. Another option in the Ace file is msil_clr_version (x). If the parameter x is set to “v1.0.3705”, the compiler uses the libraries form .NET Framework version 1.0, if it is set to “v1.1.4322”, the compiler uses the libraries from .NET Framework version 1.1. The paramter msil_clr_version (x) is also important: if the compiler tries to use the libraries from a version that is not installed, it fails to generate the contracted .NET assembly. The lace generator sets the CLR2 version of the Ace file to the same version number as used to develop the contract wizard. If a developer takes the Ace file contract_wizard_1_1.ace to create a new project with EiffelStudio, the lace generator adds the line msil_clr_version (“v1.1.4322”) to the generated Ace file. The trick to set the CLR version dynamically is to have a class with the same name in two different files. I have implemented the class CW_CLR_VERSION in the class files cw_clr_version_1_0.e and cw_clr_version_1_1.e. The constant Msil_clr_version returns the right version according to the Ace file name. An exclude clause in the Contract Wizard Ace file makes sure that EiffelStudio only creates a new Contract Wizard project with one of both class files. When the lace generator adds the CLR version to the Ace file it gets the same version as used in EiffelStudio. Table 24 shows a listing of class CW_CLR_VERSION with the parameter set for version 1.1 of the .NET Framework. class CW_CLR_VERSION feature -- Access Msil_clr_version: STRING is "msil_clr_version (%"v1.1.4322%")" -- Msil_clr_version ("v1.1.4322") end Table 24: Class CW_CLR_VERSION When I tested the Contract Wizard on other .NET libraries, I noticed that the Ace genera...
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
ACE FILE. Where applicable, MSCI will deliver directly to Licensee the corresponding Advanced Corporate Events (ACE) file, which will be deemed part of the Services. The ACE file is designed to communicate essential information relating to MSCI Index constituents and future changes in the MSCI Equity Indexes in advance of implementation. The ACE file also includes security level changes resulting from corporate events (regardless of size or index impact) and quarterly index reviews by MSCI. The types of changes communicated in the ACE file include, without limitation, corporate events (acquisitions, mergers, spin-offs, etc.), corporate actions (splits, stock dividends, rights issues, etc.), FIF/DIF/LIF/FOL changes, MSCI’s quarterly index review (QIR), MSCI’s semi-annual index review (SAIR) and changes to Global Industry Classification Standards (GICS).
Sample 1

Related to ACE FILE

  • Employee File 27.01 Upon request to their immediate supervisor, employees are entitled to read, review and be provided with one (1) copy of any document in their human resources file at a mutually agreed time. The Senior Union Official, or designate, with the written authority of the employee, shall be entitled to review the employee's human resource file in the workplace, in order to facilitate the investigation of a grievance. The employee or the Senior Union Official, as the case may be, shall give the Employer seven (7) days' notice prior to examining the file. Employees shall have the right to rebut in writing any document, including but not limited to disciplinary notices and evaluations, in their human resources file. Such rebuttals, other than grievances, shall be attached to the document and placed in the personnel file.

  • Grievance File Records involving the processing of an employee's grievance, such as the grievance form, step appeals/responses, and settlement documents, will be kept in a file separate from the employee’s personnel file. It is not the intent of this section to exclude from the employee's personnel file final disciplinary action documents, including those that result from a settlement agreement.

  • Separate Grievance File All documents, communications and records dealing with the processing of a grievance shall be filed in a separate grievance file and shall not be kept in the personnel file of any of the participants.

  • EMPLOYEE FILES 10.01 A copy of any completed formal evaluation which is to be placed in an employee’s file shall be first reviewed with the employee. The employee shall initial such evaluation as having been read and shall have the opportunity to add her or his views to such evaluation prior to it being placed in her or his file. It is understood that such evaluations do not constitute disciplinary action by the Employer against the employee. Having provided a written request to the Director of Care, or her designate, an employee shall be entitled to her personnel file for the purpose of reviewing any evaluations or formal disciplinary notations contained therein, in the presence of the Director of Care, at a mutually agreeable time.

  • Grievance Files Written grievances and responses will be maintained separately from the employee’s personnel file.

  • Personal File (a) The Corporation agrees that there shall be only one personal file for each employee and that no report relating to the employee's conduct or performance may be used against him or her in the grievance procedure nor at arbitration unless such report is part of the said file.

  • Appendix A – HRIS File Each Board shall provide to the Trustees of the ETFO ELHT directly, or provide authorization through its Insurance Carrier of Record to gather and provide to the Trustees, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the ETFO ELHT and the employer representatives:

  • Personnel File (a) An employee, or the President of the Union (or the President's designate) with the written authority of the employee, shall be entitled to review an employee's personnel file, in the office in which the file is normally kept. The employee or the President, as the case may be, shall give the Employer adequate notice prior to having access to such files.

  • Personal Files 2.5.1 The employer shall ensure that personal files are held in a secure place and access is confined to authorised personnel and the principal concerned.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!