Microsoft Foundation Classes Sample Clauses

The "Microsoft Foundation Classes" clause defines the terms under which the Microsoft Foundation Classes (MFC), a set of object-oriented programming libraries for Windows applications, may be used or referenced in the context of the agreement. This clause typically outlines whether the use of MFC is permitted, any licensing restrictions, and the responsibilities of the parties regarding compliance with Microsoft's terms. For example, it may specify that any software developed using MFC must adhere to Microsoft's licensing requirements or that the parties must ensure they have the appropriate rights to use these libraries. The core function of this clause is to clarify the legal and practical boundaries for using MFC, thereby preventing unauthorized use and ensuring compliance with third-party intellectual property rights.
POPULAR SAMPLE Copied 1 times
Microsoft Foundation Classes. (MFC), Active Template Libraries (ATL), and C Runtimes (CRTs). Microsoft grants you a limited, nonexclusive, royalty-free license to: (a) use and modify the source code version of those portions of the Software that are identified as MFC, ATL, or CRTs (the “VC Redistributables”), for the sole purposes of designing, developing, and testing your software products; and (b) reproduce and distribute the object code version of the VC Redistributables, including any modifications (or enhancements to the functionality of the VC Redistributables), so long as you rename any files created by you that are included in your Licensee Software (as defined below in Section 3.2.1(a)). For purposes of this Section, “modifications” shall mean enhancements to the functionality of the VC Redistributables. For all other applicable redistribution requirements for VC Redistributables, see Section 3.2.
View SourceView Similar (2)

Related to Microsoft Foundation Classes

  • SPECIALIZED JOB CLASSES Where there is a particular specialized job class in which the pay rate is below the local market value assessment of that job class, the parties may use existing means under the collective agreement to adjust compensation for that job class.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Synchronization Rights The Licensor hereby grants limited synchronization rights for One (1) music video streamed online (Youtube, Vimeo, etc..) for up to 500000 non-monetized video streams on all total sites. A separate synchronization license will need to be purchased for distribution of video to Television, Film or Video game.

  • Alignment with Modernization Foundational Programs and Foundational Capabilities The activities and services that the LPHA has agreed to deliver under this Program Element align with Foundational Programs and Foundational Capabilities and the public health accountability metrics (if applicable), as follows (see Oregon’s Public Health Modernization Manual, (▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇▇/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf): a. Foundational Programs and Capabilities (As specified in Public Health Modernization Manual) b. The work in this Program Element helps Oregon’s governmental public health system achieve the following Public Health Accountability Metric, Health Outcome Measure: c. The work in this Program Element helps Oregon’s governmental public health system achieve the following Public Health Accountability Metric, Local Public Health Process Measure:

  • Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.