Option to skip auto-ranorex assembly references

Ranorex Spy, Recorder, and Studio.
brogdonm
Posts: 4
Joined: Thu Dec 19, 2013 11:39 pm

Option to skip auto-ranorex assembly references

Post by brogdonm » Thu Dec 19, 2013 11:59 pm

I have a PCL (portable class library) DLL that I use in other code projects (that are not Ranorex based), when I add this existing project to a Ranorex solution, it changes the project by adding a bunch of Ranorex assemblies. The library will never call any of the methods/functions within the Ranorex assemblies, so there is no need in the inclusion. And when I open the project within another solution, which is on a development machine without Ranorex, I get a load of warnings stating it can't find the referenced assemblies. Granted, I am still able to compile and run with the warnings, but it would still be nice to not see the warnings, potentially masking out real warnings that I care about.

Is there a setting in the Studio to skip this inclusion? If so, could someone point me in the right direction. If not so, I would recommend it as a feature in future release/updates.

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Option to skip auto-ranorex assembly references

Post by Support Team » Thu Jan 02, 2014 3:45 pm

Hello brogdonm,

Ranorex libraries are referenced automatically if you open your project in Ranorex Studio.
We have implemented it since a lot of our customers make use of our Ranorex libraries.

Unfortunately, there is currently no specific setting to ignore these warnings but possibly in a future release.
Would it be an option for you to add your DLL as a referenced assembly in your solution?

Regards,
Markus (T)
.
Image

krstcs
Ranorex Guru
Posts: 2683
Joined: Tue Feb 07, 2012 4:14 pm
Location: Austin, Texas, USA

Re: Option to skip auto-ranorex assembly references

Post by krstcs » Thu Jan 02, 2014 3:52 pm

If you are actually using the library as a library, you should compile it to a DLL and just include that compiled DLL in your Ranorex project instead of linking the actual library project.
Shortcuts usually aren't...