Dll Fi.e Error In Bricscad
I am working on a WPF, C# 3.0 project, and I get this error:
See the BRX sample project that is installed with BricsCAD. It contains 4 build configurations: DebugAcad, ReleaseAcad, DebugBcad, ReleaseBcad. Check the project settings in these configs. You can compile the sample with our BRX SDK for BricsCAD, and with ObjectARX for AutoCAD. This is a process which basically re-installs all of the settings and system files that Windows needs to run, and is a great way to get the mshtml.dll file back onto your system. To repair Windows, you must have the Windows installation CD for your system and then follow this tutorial on how to repair your computer. I've been using McAfee for almost a year and I've read that Mcafee has a tendency to delete unfamiliar dll's. But this problem only cropped up since last week. I've tried setting the dll attributes to read only, with no help. Again, the file names are not deleted from the directory, but the size of the files is listed as 0 bytes.
This is how I reference my usercontrols:
It happens after every failed build. The only way I can get the solution to compile is to comment out all my user controls and re-build the project, and then I uncomment the usercontrols and everything is fine.
I have checked build orders and dependencies configurations.
As you can see, it seems to have truncated the DLL file's absolute path.. I have read that there is a bug with the length. Is this a possible problem?
It's very annoying and having to comment, build, and uncomment, the build is becoming extremely tiresome.
Peter Mortensen71 Answers
Dll Fi.e Error In Bricscad 7
I just had the same problem. Visual Studio isn't building the project that's being referenced.
- Right click on the solution and click Properties.
- Click Configuration on the left.
- Make sure the check box under 'Build' for the project it can't find is checked. If it is already checked, uncheck, hit apply and check the boxes again.
- (Optional) You had to do it for both Release and Debug modes on the solution properties.
This can still happen in newer versions of Visual Studio (I just had it happen on Visual Studio 2013):
Another thing to try is to close Visual Studio and delete the .suo file that is next to the .sln file. (It will be re-generated the next time you Save all (or exit Visual Studio)).
I've had this problem when adding new projects to the solution on another machine and then pulling the revisions in, but the .suo file can be corrupted in other cases as well and lead to very strange Visual Studio behaviour, so deleting it is one of the things I always try.
Note that deleting the .suo file will reset the startup project(s) of the solution.
More on the .suo file is here.
The suggested answer did not work for me. The error is a decoy for another problem.
I found out that I was targeting a slightly different version of .NET and this was flagged as a warning by the compiler, but it was causing building to fail.This should have been flagged as an error and not a warning.
Peter MortensenWell, my answer is not just the summary of all the solutions, but it offers more than that.
Section (1):
In general solutions:
I had four errors of this kind (‘metadata file could not be found’) along with one error saying 'Source File Could Not Be Opened (‘Unspecified error ‘)'.
I tried to get rid of ‘metadata file could not be found’ error. For that, I read many posts, blogs, etc. and found these solutions may be effective (summarizing them over here):
Restart Visual Studio and try building again.
Go to 'Solution Explorer'. Right click on Solution. Go to Properties. Go to 'Configuration Manager'. Check if the checkboxes under 'Build' are checked or not. If any or all of them are unchecked, then check them and try building again.
If the above solution(s) do not work, then follow sequence mentioned in step 2 above, and even if all the checkboxes are checked, uncheck them, check again and try to build again.
Build Order and Project Dependencies:
Go to 'Solution Explorer'. Right click on Solution. Go to 'Project Dependencies..'. You will see two tabs: 'Dependencies' and 'Build Order'. This build order is the one in which solution builds. Check the project dependencies and the build order to verify if some project (say 'project1') which is dependent on other (say 'project2') is trying to build before that one (project2). This might be the cause for the error.
Check the path of the missing .dll:
Check the path of the missing .dll. If the path contains space or any other invalid path character, remove it and try building again.
If this is the cause, then adjust the build order.
Section (2):
My particular case:
I tried all the steps above with various permutations and combinations with restarting Visual Studio a few times. But, it did not help me.
So, I decided to get rid of other error I was coming across ('Source File Could Not Be Opened (‘Unspecified error ‘)').
I came across a blog post: TFS Error–Source File Could Not Be Opened (‘Unspecified error ‘)
I tried the steps mentioned in that blog post, and I got rid of the error 'Source File Could Not Be Opened (‘Unspecified error ‘)' and surprisingly I got rid of other errors (‘metadata file could not be found’) as well.
Section (3):
Moral of the story:
Try all solutions as mentioned in section (1) above (and any other solutions) for getting rid of the error. If nothing works out, as per the blog mentioned in section (2) above, delete the entries of all source files which are no longer present in the source control and the file system from your .csproj file.
Peter MortensenIn my case it was caused by a .NET Framework version mismatch.
One project was 3.5 and the other referencing project 4.6.1.
Peter MortensenClosing and reopening Visual Studio 2013 worked for me! Free download 4k video songs.
Peter MortensenWell, nothing in the previous answers worked for me, so it got me thinking about why am I clicking and hoping when as developers we should really try to understand what is going on here.
It seemed obvious to me that this incorrect meta data file reference must be held somewhere.
A quick search of the .csproj file showed the guilty lines. I had a section called <itemGroup> that seemed to be hanging onto the old incorrect filepath.
So a simple fix really:
- Backup your .csproj file.
- Find the incorrect paths in the .csproj file and rename appropriately.
Please make sure you backup your old .csproj before you fiddle.
Peter MortensenI also met this problem. Firstly you have to manually build you DLL project, by right-click, Build. Then it will work.
BlueRaja - Danny PflughoeftI got the same error 'Metadata file '.dll' could not be found', and I tried several things described above, but the reason for the error was that I was referencing third-party DLL file which was targeting a .NET version higher that my project target .NET version. So the solution was to change the target framework of my project.
Peter MortensenIn my case, I have my installed directory in mistaken ways.
If your solution path is something like 'My Project%2c Very Popular%2c Unit Testing%2c Software and Hardware.zip', it cannot resolve the metadata file, perhaps we should prevent some invalid words like %2c.
Renaming the path into normal name resolved my issue.
I added a new project to my solution and started getting this.
The reason? The project I brought in was targeting a different .NET framework (4.6 and my other two were 4.5.2).
Peter MortensenFor me, it was trying to find a DLL in a path that used to contain the Project, but we'd moved it to a new directory. The Solution had the correct path to the Project, but Visual Studio somehow kept looking in the old location.
Solution: Rename each problem Project - just add a character or whatever - then rename it back to its original name.
This must reset some global cache of some kind in Visual Studio, because this clears both this issue up and several like it, while things like Clean do not.
Chris MoschiniChris MoschiniFor me it occurred when I included a new project to a solution.
Visual Studio automatically selects .NET framework 4.5.
I changed to version .NET 4.5.2 like the other libraries, and it worked.
Peter MortensenFor me the following steps worked:
- Find the project that is not building
- Remove/add references to projects within the solution.
I was pulling my hair out with this problem also, but after trying the previous answers the only thing that worked for me was to open each project in my solution 1 by 1 and build them individually.
Then I closed Visual Studio 2013, reopened my solution and it compiled fine.
It's strange, because if I clicked each project in my Solution Explorer and tried to build them that way, they all failed. I had to open them alone in their own solutions.
Peter MortensenMy instance of the problem was caused by a common project that had a duplicate class name in it (under a different filename). It is strange that Visual Studio could not detect that and instead just blew up the build process.
Peter MortensenI got this problem in Visual Studio 2012 in a solution that had many projects. Rebuilding each project in the solution manually in the same order as the Project Build Order (right-click and rebuild in Solution Explorer) fixed it for me.
Eventually I got to one that gave me a compile error. I fixed the error, and the solution would build correctly after that.
Peter MortensenIn my case the issue was that I'd manually deleted a non-compilation file which was marked as 'missing'. Once I deleted the reference to the now-missing file and recompiled - all was well.
Coming back to this a few years later, this problem is more than likely related to the Windows maximum path limit:
Naming Files, Paths, and Namespaces, Maximum Path Length Limitation
Peter MortensenIn my case, the problem was caused by a simple build error,
error CS0067: The event 'XYZ' is never used
that, for any reason, did not show up in the error window.
Because of that, the Visual Studio build system seemed to miss the error and tried to build dependent projects, which in turn failed with the annoying metadata message.
The recommendation is -as stupid as it may sound-:
First look at your Output Window!
It took me half an hour before this idea hit me..
Peter MortensenI too had the same error. It hides as in the below path.The path which I referred to for the DLL file is like 'D:Assemblies FolderAssembly1.dll'.
But the original path in which the assembly referred was 'D:Assemblies%20FolderAssembly1.dll'.
Due to this path name variation, the assembly could not be retrieved from its original path and hence throws the 'Metadata not found' error.
The solution is in Stack Overflow question How do I replace all the spaces with %20 in C#?.
Peter MortensenIt looks like such kind of errors related to the fact that Visual Studio doesn't provide correct information about an error. The developer doesn't even understand the reason for the failed build. It can be a syntax error or something else. In common, to solve such problems you should find the root of the problem (for example, look at the build log).
In my case the problem was in fact that the Error List window didn't show any errors. But really there were syntax errors; I found these errors in the Output window, and after fixing them, the problem was solved.
I'd faced the same problem. In my case I'd referenced to a class library project with higher .Net version than my project and VS failed to build the project and raised the same error you posted.
I simply set .Net version of my class library project(the one that had broken the build) identical to the .Net version of referenced project and problem solved.
Code_WormCode_WormIf you have a space in your solution name, this will also cause the issue. Removing the space from your solution name, so path doesn't contain %20 will solve this.
Just pointing out the blatantly obvious: if you don't have 'Show output window when build starts' enabled, make sure you're noticing if your build is failing (small 'build failed' error in lower left)!!!!
tbonetboneI had this error when I was trying to publish a web application. Turned out that one of a class properties was wrapped into
but the property usage was not. The publishing was done in Release configuration without the DEBUG symbol, obviously.
Based on the error message I don't believe the file path is being truncated. It looks to just be incorrect. If I'm reading the message correctly it appears to be looking for the DLL file at ..
WORK=-ToolsVersionManagementSystemBusinessLogicLayerbinDebugBusinessLogicLayer.dll
This is not a valid path. Is it possible that you have a macro definition in the build process set to an invalid value?
Peter MortensenThis error may be shown if you use fake assemblies. Removing fakes leads to successful build of the project.
Dll Fi.e Error In Bricscad Windows
Peter MortensenI am running Visual Studio 2013.
It appears that the build dependencies were incorrect. Deleting the *.suo files did fix the problems I had.
Peter MortensenFor my case it was that I had commented out classes in a specific (empty) namespace:
When I removed the namespace code and the import (using) commands of it - it fixed the problem.
In the build it was also saying - along with the missing DLL file of the project:
error CS0234: The type or namespace name 'W' does not exist in the namespace 'X.Y.Z' (are you missing an assembly reference?)
Peter Mortensenprotected by Community♦Jul 9 '15 at 4:54
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?