After clearing out my temp folder in an effort to free up some much needed disc space, my Sql Server Data Tools (SSDT) in Visual Studio 2012, no longer builds my data project and Schema Compare is now useless ('cause it's gotta successfully build first). I get the following error message ...
Error 187 04018: The "SqlBuildTask" task failed unexpectedly.
System.IO.FileNotFoundException: Could not find file 'C:\Users\gstenstrom\AppData\Local\Temp\b3546b57-815f-43e1-92a5-831cd4844026.9.tmp'.
OK so the problem is obvious; I have clearly deleted something I needed to keep. However, I cannot replace the file as it's been deleted permanently, so what do I do to fix this issue? I have been astounded as to how little information there is about this out there so far. Any help would obviously be greatly appreciated.
Looking for a Christmas Miracle here ... quick and simple!!! :)
Thank you for your help and Happy Holidays!!
Just had the same issue. I think you figured this out as well, but just for future reference: restarting Visual Studio should fix the problem.
Related
I am using Android Studio v2.1.2..
This is my attempt at android development so, I am making a lot of mistakes..
However when i am correcting them, and trying to build again it's still showing the same errors;
I tried to clean the project, tried restarting Android Studio but of no luck..
Like in this pic, this apostrophe error is not going away.. i had similar errors earlier also..
They were not severe so i kept them that way..
I know this is a stupid question, but anyone could tell me how to solve this I would be grateful.
Thanks in Advance...My Problem
You have this: "Let's take a test!!!" in your values.xml file.
Update it to this: "Let\'s take a test!!!".
Always put a \ before a '(Apostrophe) in your strings.xml/values.xml/etc.
I hope I helped.
My goal was to update a reference from my old DLL to a newer version that was updated to VS2012.
D:\DEV\<old_path>\TEST\bin\Company.dll
D:\DEV\<new_path_2012>\TEST\bin\Company.dll
In the .vbproj file...
<Reference Include="Company, Version=0.0.0.0, Culture=neutral">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\<new_path_2012>\TEST\bin\Company.dll</HintPath>
</Reference>
In the Solution Explorer, Under References, I right-click on the Company reference and click Properties. The Path is listed as...
D:\DEV\<old_path>\TEST\bin\Company.dll
There are no errors or warnings. Everything is appearing to build properly however I lack confidence because of this discrepancy. How can I fix this?
I have tried restarting VS2012 and have tried deleting the TFS Cache. Downloading a fresh copy of this project from TFS on another PC seems to resolve the problem however I would like to better understand how to resolve this without such drastic measures.
I just had this issue crop up, and while this is an old thread it was the first Google result when I did my search, so I thought to offer what had happen for me.
TL;DR: Triple check the hint path - it could be wrong, and VS is using the DLL in the GAC.
My issue came up because I was using a little script to help me update over 250 projects worth of references, and had a small handful that didn't follow normal folder layout. So my hint path was 'correct' at first glance, but because it really wasn't, VS 2013 went to the version of the DLL in the GAC.
Once I clued into what was wrong and fixed the relative path for that project file, hint path and what was displayed in References matched up as it was supposed to.
I need help resolving the following error:
Error 2 Could not copy the file "obj\x64\Release\project_name.xr.xml" because it was not found.
NOTE:
This error does not occur when I package the same solution on x86.
This only occurs on x64.
In addition, this error is now exposed ever since I downloaded VS2012 Update 2.
The error went away as a result of me fixing the list of warnings that resulted from building the solution.
For me the issue was fixed simply by removing spaces from Assembly Name parameter. This can be found in the properties of the Windows 8.1 application project.
Ok, this is a weird problem and I could not solve it till I looked at the solution from Ken.
Click here for his solution
Ken's issue and solution gave me an idea and it worked.
I had x:Class="project_name.App" in my App.xaml file and Ken said the issue was with the app name.
So I removed the .App from x:Class="project_name.App" and just had x:Class="project_name" and received the error "Invalid value for 'project_name'. Event values must be text."
Ok so I put it back in.
Well, then it worked and the error went away.
Um, I do not have any idea why it now worked as it was exactly the same text, but the process of changing it back and forth fixed it. Hope this saves someone hours of pain.
And I am using Visual Studio 2013 Update 2 that I reinstalled onto my PC yesterday since the PC had a melt down and needed a rebuild.
My tabbed open documents are stuck on the same three files for over a month now. When I save and close VS2012 the open files I was working on do not come back on restart. I get the same three old files regardless. I am assuming that the tab cache has issues or something and needs to be cleared, but don't know where to go for this. Has anyone else run into this glitch? Any solutions to refresh the tab'able items so this functionality works correctly again?
It has been three weeks with no answers ... so I finally figured this out on my own. I hate answering my own questions, but here it is:
The SUO file is where all the settings, startup project, and cached user options are kept. With large projects there are times where the .suo file becomes corrupted or too large causing sluggish, or odd behavior with these options. Case in point the outlier I ran into with my open classes not being remembered.
Solution:
Simply delete the .suo file. Visual Studio will create a fresh one for you. I did this and it solved the problem.
NOTE: if you do not see a .suo file in your Solution's root directory try showing hidden files.
The Visual Studio 2012 Professional Edition installed on my PC keeps on showing in error list
"csc.exe" exited with code 1 in Visual Studio 2012
instead of the actual error (e.g. syntax error).
How can I fix this?
I turned on detailed logging in Tools -> Options ... -> Projects and Solutions -> Build and Run.
When you rebuild your solution, you can see the command that gives the error. Copy the command, open a cmd window, go to your project folder, paste and run the command. The output will give you the actual error.
It's some sort of bug in VS2012 I suppose. You could try cleaning your solution, restart Visual Studio and try rebuilding? The above solution should point you in the right direction for finding your error. When opening the file containing the error, the errors should appear in the error list.
This happened to me because I enabled the "treat warnings as error" switch in my project settings and had an unused class member in some file.
I agree that the output window's message is misleading and should be replaced by some message that shows which member cause the build to fail.
Maybe my unswer is too late, but I want to say, that such error could also happen if you copy that project from another solution. That project was sign with .snk file and you added it to TFS (for ex). VS does not upload .snk by default and when you will use your code in the other place, you will not have that file, but in AssemblyInfo.cs there will be mention that your project contains that file. So, c2c2.exe will not build your solution because of this. Quick solution will be just to commnet this line
[assembly: AssemblyKeyFile( #"....\sn.snk" )]
in AssemblyInfo.cs
I had the same issue.
I tried cleaning the solution, deleting the bin/obj folders, repaired visual studio 2013, dump out detailed build info, nothing helped, CSC still exited with error code 1, no more info than that.
In the end it was caused by two variables (a double and double[]) with the same name in the same code block. Strange error to cause it.
If this happened to a project that was working before, verify no devenv.exe is running after closing VS:
-Close all the instances of VS
-Open the task manager
-Verify all the devenv.exe actually get closed, or kill the processes
For me, I still had 3 devenv.exe working; I ended these processes, started VS again, and it worked correctly.