Develop Reference

Project output files deleting when rebuilding entire VS solution, causing build failure

Before building anything, here is the output folder of the problematic project:
It is empty
After building the whole solution, I get this error:
Severity Code Description Project File Line Suppression State
Error CS0006 Metadata file
'C:\Users\Grant\Source\Repos\raderag\ExcelConnectRTDKraken\KrakenOrderSystem\bin\x86\Debug\KrakenOrderSystem.dll'
could not be
found KrakenOrderTestClient C:\Users\Grant\Source\Repos\raderag\ExcelConnectRTDKraken\KrakenOrderTestClient\CSC 1 Active
Which makes sense, because there is nothing in that folder. So I rebuild the problematic project by itself, and the rebuild is successful. The output folder looks like this:
All dlls are there. So far so good
Now when I try to rebuild the entire project, I get the same exact error as before and the files in that output file are gone.
Here's what I've tried:
I rebuilt the problematic project successfully. I then rebuilt every single project in the solution one by one to see if they would delete the files in that project output. None of them did. I then tried rebuilding the whole solution, and got the same error with the output files gone.
Sorry that I don't have more information. Please let me know what more I can provide to accelerate a solution to my problem. Thank you!
Edit:
Oddly enough, the rebuild of the entire solution actually sometimes works. It doesn't always delete those files, although 90 percent of the time it does, and I can't find the cause for it's success and failure. It's seemingly random.
Edit:
Even more absurdly, without changing anything the solution now successfully builds 90 percent of the time and fails for the same reason 10 percent of the time.

"The path .. would result in a file outside the App Bundle and cannot be used" Error, mono touch / Xamarin

i am currently facing a really weird and annoying error message after migrating my Xamarin.IOS - Project to the 64bit unified - API. The exact error message is:
/Users/falcowinkler/Dev/AHK_App -Kopie/AHK_App_iOS/../ahk_app_ios/resources/.DS_Store:
Error: The path '../ahk_app_ios/resources/.DS_Store' would result
in a file outside of the app bundle and cannot be used. (AHK_App_iOS).
I get that error not only for .DS_Store but also for two other files.
Here are the things i tried.
Clean / Rebuild
delete bin / obj Folder and rebuild
I deleted the files that throw the error, just to get another message that the project is missing these files. I added them again after that, and got the same error as above again
I tried moving my project to other locations, but the error does not change in the slightest.
I tried to remove all problematic files, before migrating, which didn't work as well.
Does anybody know where all the file references are stored in Xamarin, so i can view/edit them to find out what the error is?
I mean the DS_Store file is just a tiny file from mac - finder architecture, is not even necessary for my project, but still it is referencing it, i will just have to kick out these references i guess.
If anybody encountered these issues as well, and has a solution, pls leave a quick post here, thanks :)
Update
I am now pretty sure that there are some misplaced references to files in my project, i saw a similar issue on git hub. But how can i wipe them out? I tried removing my entire resources Folder and adding it again, but it didn't help either. Error message now looks as follows:
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets:
Error: Bundle Resource '../ahk_app_ios/resources/.DS_Store'
not found on disk (should be at '/Users/falcowinkler/Documents/AHKKopie/ahk_app_ios/resources/.DS_Store') (AHK_App_iOS)

If anyone else has this problem, just search your project files for the filename. The .csproj File will appear, where you will be able to wipe out the reference to the file, causing the problem.

If you are using Xamarin Studio, you can delete the .DS_Store under your Ios project [ProjectName.iOS] under the Resources folder

Payload file FileListAbsolute.txt does not exist compile error

Trying to debug this error. The exact error is:
Error 15 Payload file
'C:\svn\myproj\obj\Debug\myproj.csproj.FileListAbsolute.txt'
does not exist.
It occurs when trying to build my solution in VS2012.
I don't know what this file is, or does, but it is definitely there in the solution. It seems to be an auto-generated file of some sort.
Any explanation for what this error might mean or how to fix it?
The file contains a list of every single file in the solution it would seem.

Odds are something got out of sync in the obj folder, which is an intermediate folder where Visual Studio stores things to make builds faster in subsequent runs.
Steps I would try, in this order.
Clean the project
Clean your solution.
Delete the bin and obj folders
Restart VS
Reboot.

I used the notepad++'s find in files, the problem was "Data\license.xml", so I deleted it from csproj by double clicking on line(pic) in notepad++'s find results window.

Why does Rebuild ALL Fail after moving solution folder to a different location?

I have a C# web application that I've been working on which has built properly since I began working with it. I moved the entire solution into a different folder, and now, when I try to build it says "Rebuild All failed" with no other errors. I have reviewed the verbose output from build; but, I don't see anything that jumps out at me as causing the problem. If I move the solution back to the original location, it will build again. Anyone know why the new location breaks the build?
Thanks.

The most likely cause of this error is that the location you are moving the solution to is not trusted.
For example, if you move the solution to a protected folder like C:\Program Files or C:\Windows or a network location.
If this is not the case, please advise where you are moving the file too and perhaps share any errors from your build log.

I believe I found it- turns out, moving it several directories deeper may have blown the maximum path size for NTFS (see this question: VS2010 - same soltuion (IE SVN checkout), different locations, one builds, one fails any ideas?). I moved my project to a root directory in c: and now it's compiling normally in VS2010.
A friendlier error would have been nice; but, hey, what can you do?

SVN keeps corrupting files with "<<<<<<< .mine", how to fix?

I've got a Visual Studio C# project which is under version control (SVN).
I've always commited and updated the project without any problems. But a couple of hours ago Visual Studio throws the following error when I try to launch/rebuild the project:
Files has invalid value "<<<<<<<
.mine". Illegal characters in path.
I don't know how to fix this problem. What should I do?

That happens when svn encounters a conflict: You changed a file, the file on the server was changed and it cannot (easily) be merged automatically. You need to decide what is the correct solution now.
Subversion just adds the diff into your source file (and creates files next to it, called OriginalName.mine (unchanged) and OriginalName.rsomething (unchanged, server version)).
Fix the conflict and tell subversion that this is resolved.

just delete the obj folder and it will worked fine.

Remove the code that shouldn't be in the file throwing the error and remove the the three files with extensions .mine, .<somerevision> and .<some_other_revision>. svn updated files that now contain 'conflicts' and you need to resolve these conflicts by hand. Usually this means you edited a file, someone else edited the same file and checked in changes and you didn't pay attention when checking out the changed file.

Delete every thing you have in obj folder .
Remove your obj folder from svn version control . Because on every build it get updated and when other developer commit changes to solution SVN is unable to marge obj folder files and raise error
Files has invalid value "<<<<<<< .mine". Illegal characters in path.

Please read the Basic Usage chapter in the subversion book. It has a section about Merging conflicts by hand which explains the conflict markers you're seeing.

Removing the debug folders worked for me (see comment-not answer above).
I got this after moving 12 folders from one section of svn to a new section. So if you get this after moving a project and the error does not point to an actual file, this is likely your issue.

If you have AnkhSVN or VisualSVN installed resolving this is most likely as easy as right clicking the file in the solution explorer and selecting edit conflict.
This will open the changed file in your merge editor. (See Tools->Options->Source Control->Subversion User tools for AnkhSVN). With a good merge tool like the free to use SourceGear DiffMerge or TortoiseMerge, resolving the conflict is just a few mouseclicks away.

I have had this happen on a large scale where the files get marked resolved but the conflict metadata is still there. I wrote a regular expression for visual studio to find these, for instances where it is not feasible to simply revert the changed files.
http://www.codetunnel.com/blog/post/90/ever-merge-with-svn-and-mess-up-when-resolving-conflicts-read-on

I closed the IDE, then deleted the obj folder and restarted the IDE and rebuilt my Code. This worked for me.

Inside your project :
odj folder -> Debug -> project name.csproj.Filelistabsolute.txt(snb.csproj.Filelistabsolute.txt)
Inside the text file
>>>>>>>.mine and >>>>>>>.r150 occurs
to remove the things the program works

1)Just save your local changes whatever u have edited in the file
2)revert the file
3)update it from SVN
4)Paste your local changes

If you are using TortoiseSVN you should have a right click option on the file called Edit Conflicts. This should bring up TortoiseMerge which is able to read those obnoxious notations stuck into the file (really, to break your code so you KNOW there's an issue and don't blindly check it in).
TortoiseMerge will read it properly and present you with a 3-way merge. This was what I was looking for. Although it is true that it does also create the separate .mine and .rxxx and .ryyy files, and there are various manual and command-line ways to deal with all this.

Have a simple solution. just delete all file from debug folder and rebuild the solution, an error display on the screen "There were build errors. Would you like to continue and run the last successful build? click on "Yes" button. Now stop the program and run normally.