# Msbuild example for Clarion **URL:** \ **Category:** Tips\ **Created:** [January 9, 2015, 3:49pm UTC](https://clarionhub.com/t/msbuild-example-for-clarion/274 "2015-01-09T15:49:59Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![CarlBarnes](https://clarionhub.com/user_avatar/clarionhub.com/carlbarnes/32/1859_2.png) [@CarlBarnes](https://clarionhub.com/u/CarlBarnes)\ **Post date:** [July 9, 2020, 10:28pm UTC](https://clarionhub.com/t/msbuild-example-for-clarion/274/7 "2020-07-09T22:28:57Z")
Handling circular references with #implib > **[Handling circular references with #implib - Clarion Content - Confluence](https://clarionmag.jira.com/wiki/spaces/clarion/pages/399918/Handling+circular+references+with+implib)** I found Dave Harms had written the above a CMag article on the topic of using #ImpLib with nice screen captures. Be aware the article example uses the **wrong syntax** that flips the file names as LIB EXP. In his post here he shows it right as #ImpLib DllA.EXP DllA.LIB I used the Article to make an example using DLL Tutor that I attached. 1. Make a Win32 Project with a CLW that has nothing but MAP. CODE 2. Make a LibCreate.PR file like below and add it to the SLN under Projects to Include ---- LibCreate.PR ---- #implib ALLFILES.EXP ALLFILES.LIB #implib REPORTS.EXP REPORTS.LIB #implib UPDATES.EXP UPDATES.LIB I don’t use this, I do a 3 pass MSBuild of DLLs, DLLs with Mutual Imports, EXEs. I’m not entirely sure how ImpLib can work with source control and multiple developers. It seems like a “chicken and egg problem.” The EXP file needs to be in Source control for use by the build server to perform #ImpLib. That file is generated and I’m not sure how stable it is so will it merge well? [ImpLibExampleForDllTutor.zip](https://clarionhub.com/uploads/short-url/mlq10IY48PX0pqfkfRCQtLdPF4k.zip) (2.5 KB) --- _[View the full topic](https://clarionhub.com/t/msbuild-example-for-clarion/274)._