Hello i im running Visual studio 2022 professional. I have downloaded libiec61850-1.5.1 libIEC61850 I have compiled the code whit cmake. I have then opened it in visual studio code. The problem is that the References in the example projects could not be resolved.
I have tried the following things.
Remove the references then add them again save and rebuild project.
Remove the references the save rebuild project, closed and started visual studio again
the tried add the references.
Tried edit the path directly in vcxproj file.
I downloaded the libIEC61850 a second time to make sure there was no corrupt files. Made
a new compile whit cmake. still got the same problem,
Updated the visual studio to the newest update.
Anybody that have a idea what the problem can be. I have searched the a found nothing that could help. i have checked this post also
The problem was that Link to library dependencies was not set to "True".
After i changed this the reference error did go away.
Related
I installed recently the Xamarin platform and i created a default Xamarin.Forms Shared project using VS2015 and under the Droid project References i get a yellowish icon on System.ObjectModel library as you can see...
The weird thing is that in the beginning everything compiles but when i add a Cross-Platform -> Forms Xaml Page the compiler throws error on the InitializeComponent() method call.
I tried to manually reference System.ObjectModel.dll from the path C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades without any luck. When i right-click on the properties i get this
but in the file system properties everything seems to be correct.
All the above are with the default options.
Does this happen to you or it's just me? (i tested it in two computers)
If you have any questions i will update the post after this message...
Welcome to Xamarin! It's like tap dancing your way through a field of land mines. But XAML is awesome. Here is what worked for me: update your nuget of xamarin forms, do clean build, see the error/warning, restart visual studio, do a clean, restart visual studio again, do a build, spin your chair around 3 times counter-clockwise, and voila, the error is gone. It's like magic! No need to manually much around with dlls, it will just work.
Try to delete the contain of bin folder in PCL project and android project. and clean the solution try it again.
reference: http://xamarin103.rssing.com/browser.php?indx=50717177&item=8379
user: PubuduGayan, The second option that He suggested.
I hade same problem. Adding reference from C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Facades... didn't work me.
What worked for me was to change (Tools/Options/Project and Solutions->Build and Run) Verbosity from normal to minimal, even if system.objectmodel reference-warning is still there.
Maybe this will work for developers too who are facing same problem
I faced the same problem. Deleting the reference helped in resolving the warning since System.ObjectModel was not used at all.
I have glut32.dll file which needs to be in the Debug folder whenever I compile a source. It's very frustrating to manually put in the Debug folder of each project file to have it run properly.
Is it possible I can put it in some folder and point the project to it?
I am a newbie with Visual Studio 2012.
Before this question being tagged as a duplicate, I want to add I keep seeing suggestions Referencing third party dlls, but I couldn't get it.
Any help appreciated !
If you add a project reference to this DLL, I believe it should be copied to the Debug folder automatically.
I recently upgraded from Visual Studio 2012 to 2013 and am having issues in an MVC project. Specifically the intellisense is messed up and says there are errors when there are not.
The project still builds however, and works fine. Has anyone had this problem and been able to fix it?
Try to clear the project (Menu > Build > Clear 'MyProject') and then Rebuild the project. Note that for me clearing the solution does not work, must clear the project.
For me, VS2013 seems to 'forget it knows MVC'! All my MVC references break, all my #Url and #Html stuff breaks. The fix is to clear the project.
I have had this problem. For me it was broken references that didn't read as broken. If you look at the ones that are saying they are broken, then delete and recreate the references you will likely be able to fix the problem.
I just added an existing MVC project to VS 2012 that i downloaded from Codeplex. The problem is when i'm trying to build or run the project i get a lot of errors that VS can not find references and namespaces. If i open a new MVC project then i'm not getting this errors and everything runs fine. So it only occurs when i try to open an existing project.
Can someone help me with this please?
From the VS 2012 menu select Tools->Library Package Manager->Package Manager Settings. A window will appear. Check the checkbox labeled "Allow NuGet to download missing packages during build" under the Package Manager->General heading. Click the OK button to apply the setting.
Next in the Solution Explorer right-click the Solution node and select Enable NuGet Package Restore. Perform a Clean Solution and then a Build Solution. A .nuget folder should be downloaded into your solution and all compile errors related to missing references should be resolved.
This is what worked for me.
I'm working with some application handed over by another person in which I must document the requirements, build and deploy processes.
The problem here is that Visual Studio (2005) is throwing a lot of errors since it can't find the references for the dlls.
This obviously won't let VS build the project.
Everything works fine on the persons computer but not on mine, even though the project references the same folder where the dlls are, the bin folder.
How can I circumvent these problems and get VS to properly reference the dlls?
The following printscreen shows the references screen for the project.
My guess is that your DLL uses a more recent .NET framework than your application does.
Check the properties for your DLL source (right-click on the DLL code in the solution explorer and choose Properties). Go to Application - Target .NET framework and compare the version to the one the application itself uses (right-click on the project code). Note: under your application properties check both the settings under Application - Target .NET framework AND under Publish - Prerequisites.
For what it's worth, even after changing the .vbproj file and removing many lines about hard coded values,
I eventually checked out the project again removed all references to the given DLL and then added it using the GUI.
Lesson learned, don't try to change out one DLL for a newer version without using VB2005 GUI.
The easiest solution will probably be to transfer everything to another project. It will be incredibly time consuming to find where visual studio has left the hard coded path at.
WOOT!!!! Compile the DLL file to a lower version of the .NET framework, and it will fix the problem!!!!
The paths in the project file cannot be the same or the assemblies referenced have a different version.
It might be worth unloading your project and the editing it to inspect where it's looking and for what version.
I had the same problem with an older Visual Studio Project that I opened in Visual Studio 2008. I tried to add new references to the project and got permanent errors that the dll's cannot be found. After the migration of the Project to Visual Studio 2010 I got the following error message when I tried to add a new reference:
'mySample.dll' or one of its dependencies, requires a later version of the .NET Framework than the one specified in the project. You can change ...
After changing the projects .NET Framework to a newer version everything works fine.
Good suggestions in other answers. In my case, it was because the libraries weren't copied (downloaded) successfully: the files existed, but were 0 kB.
Did a clean, which removed all the DLL's and then VS2008 complained it couldn't find the references (Duh!!!) and wouldn't rebuild....luckily I had and old version of the dll's and replaced them in the directory AND THEN did a rebuild to replace them...all references are now OK and we're back to normal....good old VS 2008