Home › Forums › Software Development › Split: .Net and WPF
Tagged: .NET, c++, Visual Studio, WPF
- This topic has 4 replies, 2 voices, and was last updated 9 years, 9 months ago by Anders.
- AuthorPosts
- 27/11/2014 at 17:32 #2123yagoubParticipant
hi,
when i add Tobii.EyeX.Client.dll to my solution (it it doesn’t work ) there is not a small blue arrow , like in samples ,
if you see it , in samples look in explorer solution you will finde the file Tobii.EyeX.Client.dll whith icone in it there is a small blue arrow.. what does it mean ???
thank’s
28/11/2014 at 18:08 #2126AndersParticipantHi yagoub,
the small blue arrow on the file in the Visual Studio solution explorer view means that the file is a link. That is, the file doesn’t belong to the C# project, but is referenced from somewhere else.To create a link: right-click on the project, choose Add/Add Existing, browse to the file, then click the DOWN ARROW NEXT TO the Add button. There you can choose “Add as link”. Yes, this is one of Visual Studio’s best kept secrets.
Once you have added the file, open its file properties and make sure that the Build Action is set to Content and Copy to Output Directory is set to Copy if newer. This is actually the critical part; it doesn’t really matter if you add the file as a link or not.
01/12/2014 at 10:27 #2130yagoubParticipantohh thanks Anders you saved my life …
01/12/2014 at 12:25 #2131yagoubParticipanthi
andersi have an ather problem it is
Could not load file or assembly ‘Tobii.EyeX.Client.Net20, Version=1.1.428, Culture=neutral,
07/12/2014 at 21:53 #2167AndersParticipantIs this happening at compile time or at run time?
If at run time: this can happen if you build your app for “Any CPU” and then run it on a 64-bit OS while referencing the 32-bit Tobii.EyeX.Client.Net20.dll.
Always build for x86 or x64 and reference the appropriate client dll.
- AuthorPosts
- You must be logged in to reply to this topic.