Could not load file or assembly Telerik.OpenAccess - c#

I added references to telerik dlls in the codeBut, when I am building the project I am receiving an error randomly.
Error1Unknown build error, 'Could not load file or assembly'Telerik.OpenAccess, Version=2015.1.220.1, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342' or one of their dependencies. Can not find the file specified.
I am not using openaccess assembly at all. I have no idea why this keeps coming randomly. I am not even able to find the dll anywhere to add it to the project.
Kindly help me fix this issue.

For me (and after searching around, for many others) this was due to dll files erroneously remaining in the bin folder, even after cleaning the solution. In my case the dlls were somehow left over while switching from one git branch (which included some dlls that depended on Telerik.Openaccess) to another.
I manually cleaned out my bin folder and rebuilt my solution and the problem went away.

The same problem is discussed in the Telerik forums: https://www.telerik.com/forums/unable-to-build-the-application-after-adding-telerik-references.
What you can do is to:
delete the contents of the licenses.licx file and save it.
delete any references to the Telerik.OpenAccess.dll in the project. If needed edit the solution file of the project in a text editor and remove the reference from it.
Last but not least delete your VS and .NET cache - Clean Up ASP.NET and Visual Studio Cache and Temp Files

Related

Where does WiX cache path names?

Following on from my issues with a simple Visual Studio Installer Package, I'm making the switch to WiX. The learning curve is annoying, because once I've set this up I'm going to forget how it works before I need to do it again next project. But anyway, here we go.
My environment is Visual Studio 2019 and Azure DevOps (the full TFVC). The projects involved are class libraries and a WPF application all written in C#. I also have the WiXWax extension thingy to give me a GUI for adding projects and dependencies quickly.
When I created my WiX project I stupidly included a typo in the name of the project and consequently in the underlying folders. When I noticed this I decided to fix it;
Unload the projects
Using the source control explorer, rename the folder
Using notepad, open the sln file and correcting the path to the project, and the project name
Using notepad, open the project file and correct its references to the path and project name
Rename the project files
As you can see I have changed every reference to the the incorrect spelling.
Unfortunately, Visual Studio won't load the project. I get an error telling me this:
C:(correctly spelled path that matches the file system and file names).wixproj
: error : The project file
'C:(path with a typo in it)(correctly spelled project name).wixproj'
has been moved, renamed or is not on your computer.
Now the message is partly correct, because the file it says has been moved or renamed has in fact been renamed. If I click on the error it opens the wixproj file (it's just an xml of course). This file doesn't have a self referenced location though, the only things that's close is the include to the projects which haven't changed and are correct (..<correct detals>.csproj)
I have opened every xml file including the solution files and wix project files and none of them contain the typo (Ctrl+F, case insensitive, not whole word - no results).
I have tried "Removing" the WiX project from the solution and re-adding it, but I get the same error and it doesn't add it to the solution file.
What is remembering the old path name, and how can I make it forget it?
edit: I've also tried Ctrl+Shift+F per Klaus' suggestion and it finds no references.

Unity lost almost all Assembly references

I have an unity project in which I added an external .dll via NuGet.
After that my project lost almost all assembly references. (Error CS0234)
I tried reimporting all assets.
I deleted the Library-Folder and let it rebuild and reinsert the deleted one.
I checked the manifest.json; It contains "com.unity.modules.ui": "1.0.0", .
Since the Unity Editor and Visual Studio throw me that error I can't run the project.
Can I rebuild the assembly references in any way, so I can save my project?
I found the problem and the solution:
The problem:
You need to insert the .dll you wan't to access into your Asset folder. I did that. I simply took the whole constructed folder hierachy from the NuGet installation folder.
There were multiple versions of the same .dll in there. Also there was a .xml file with assembly code in it.
The solution:
Just copy the .dll and avoid multiple dlls and the xml file. Unity will take care of that itself.
If you lost your assembly references, take a backup of the manifest.json from the Package folder and replace the corrupt one.

References can not be reinitialized after check-in from visual studio team service

I did check-in to download source code for the first time, but i got some missing references. I've tried following ways but it doesnt work for me:
Add references: Right click -> add references then find references (after adding the references, there is nothing change, you can see in the photo below)
Dlls were set to Copy Local (I even can not change the copy local to
true)
Adding namespaces to both web.configs did nothing.
I used VS2015. is there any way to update it correctly? thanks
Generally, source code does not contain dll's, since they are vey big files. So I would not normally expect to get dll's from source control. You would usually have to build the solution and hope that Nuget is enabled to download the dll's from where they are stored.
However, the dll's you are showing come with the .net framework, so this should not be an issue, unless of course, the solution file is expecting to find the dll's in some /bin directory.
You can find which directory the dll's are expected to be in by right clicking on the missing dll and then clicking on 'properties'. This should show you the referenced dlls path in the properties window.
If the dll is not in that path you can do one of 2 things:
Delete the reference and add a new reference to the dll, where it actually exists
paste the dll in the path that is being referenced by the solution.

Path Issue Causing System.IO.FileNotFoundException

I added a solution to my project, just for unit tests (NUnit)
I have included references to all of the dlls the test solution needs
but..
I am getting the following file not found error:
System.IO.FileNotFoundException: Could not load file or assembly '\bin\Debug\bin\aLibrary.dll' or one of its dependencies. The system cannot find the file specified.
The issue is that on build, all of my dlls are correctly getting placed into
MySolution/bin/Debug , which is what I have the path set to in the project properties, but the error is telling me that the application is looking in MySolution/bin/Debug/bin
The solution settings show the correct path
If I copy those dll files from MySolution/bin/Debug to MySolution/bin/Debug/bin all works as expected.
Question
I have no idea where the path is being set. How do I correct or where should I look? Any ideas are welcome.
Thanks
Thanks
Right click on the project, go to properties, reference paths and check if you need to change the path: more described here: https://msdn.microsoft.com/en-us/library/ayds71se(v=vs.120).aspx

How to find out where my error is coming from?

I have an annoying error that's been popping up, and I don't know where it is coming from. The error is:
Error 31 Unable to copy file "app.config" to "bin\Debug\Framework.Tests.dll.config". Could not find file 'app.config'. Framework.Tests
The problem is, I don't have a bin\Debug folder anywhere, and it does not say from where it is trying to copy app.config. Double clicking on the error doesn't bring me to any code where it is trying to copy, so that doesn't help me either. So I don't know where I should make the app.config.
How can I find this out?
You have added a reference to a file called app.config or Visual Studio did this for you. The file does not exist on the disk, presumably because after adding the reference you later deleted the file.
Search for the missing file in your Solution Explorer, and either delete the reference or create the file.
It is most likely in the root folder of one of your projects, and should have a yellow triangle warning icon showing that the file is missing.
In an MSTest project the app.config is the one that you would like to provide any calls to the ConfigurationManager class.
It resides in the root of your test project.
The bin\debug folders will be created once the project compiles for the first time. Show all files in the solution explorer should help as they are not (and should not) be included in the project.
HTH
You probably do have a bin\Debug folder beneath your project folder, being the build target folder created by Visual Studio when you build your project for the Debug configuration.
My guess is that something (a test framework perhaps) still has the DLL file loaded, so Visual Studio can't delete and replace the existing Framework.Tests.dll.config file with the contents of your app.config. [Note: the project build action for app.config files is to copy it to the target folder renamed to match the executable with an extension of .config appended.]

Categories

Resources