Multiple copies of lvanlys.dll is causing build problems.

[Mark_L]

My project is using multiple copies of lvanlys.dll.   This is causing build conflicts.  Does any know the solution to this?

[mikeporter]

I think I remember this coming up recently, but I don't remember what the resolution was. Try doing a search on the forum for the name of the DLL.

Mike...

[Mark_L]

I looked up lvanlys.dll but did not find a solution.   

[tyk007]

Rename the dll file as part of the build (via the prefix option) for dependencies. You'll effectively have multiple copies at run-time loaded into the process memory space but no conflicts.

[Mark_L]

Ok, I will try this.  thanks.  I will let you know how it works.  

[Mark_L · Accepted solution]

We mass compiled, created packed project libraries and removed unused (downlevel) code from disable structures.  What ultimately helped was to update to the VISION driver on the target PC.  

More info in this thread

http://forums.ni.com/t5/LabVIEW/The-full-development-version-of-Labview-is-required-to-fix-the/td-p/...

So I am not certain what exactly fixed the multiple copy issue but I think just getting the code cleaned up helped.  Now we no longer have multilple copies of lvanlys.dll.

Thanks for your help.