TortoiseSVN - New files are marked as ignored rather than unversion - tortoisesvn

I am creating new files on my project but for some reason they are marked by TortoiseSVN as ignored by default rather than unversion, so I keep check changes in without new files then I have to go manually to the folder right clicking on the file to add it to finally check it in, this make the whole process really annoying.
Any idea?
Regards

Possibly you configured to ignore all new files unintentionally.
Click the right mouse button in the project folder and then select TortoiseSVN > Properties.
If there is a property "svn: global-ignores" with Value "*" or "*.*", remove the property or edit it to remove the two mentioned values.

These files are ignored due to (some) ignore-rules. You have to detect this rule, if you don't want to continue adding files by hand

Related

.gradle\caches\6.1.1\file-changes\last-build.bin (Access is denied)

I've tried to delete .gradle folder or delete last-build.bin file, but it isn't work. Could everyone have the solution to this problem ? thank you...
One simple solution is
I believe that another solution for that could as much be related to hidden folders. If that is the problem:
Check if your User folder is not hidden C:/User..
On the tab menu, select View.
On your far right there will be Options, select.
It will display Folder Options with the following tabs: General, View and Search. Here again, be sure to select View.
Navigate to Hidden files and folders.
And under that folder, just select Show hidden files and folders radio button.
Should that not do the trick, then move on to check if ALL the folders related to that path all the way to Caches are not hidden. The culprit here, should be that the: .gradle\caches is hidden.
Therefore, tap on the folder and unhide it activating the Caches folder(don't open it - just select it) and clicking View once again. Just next to Options on your far right, there should be Unhide selected items on the left. Of course, Unhide them and wait until the attributes are well applied. Now you are good to go, you should not experience that problem any longer.
I think that should do the trick if by any means your folder got hidden. Be sure to do that first, before following any of those technical steps. If your folders are hidden, Android Studio or Intelli j for that matters, cannot access the path in question.
Goto File -> Invalidate caches / Restart
Shutdown Android Studio
Rename/remove .gradle folder in the user home directory
Restart Android Studio (It will download gradle metadata and data)
Gradle build succeed
Rebuild project. Done.
reference

Visual Studio 2012- How do you delete a new file?

I have Visual Studio 2012 with TFS. I created a new file (call it "x.h") and before I checked it in I decided I didn't need it.
MSDN makes it sound so simple:
In either Solution Explorer or Source Control Explorer, browse to the folder or file that you want to delete.
Select the items that you want to delete, open their shortcut menu, and choose Delete.
When you are ready, check in your changes.
So I went to Source Control Explorer, right-clicked the file, and chose Delete. It was removed from source control and my pending changes but is still on disk and in the Solution Explorer. When I right-click the file in Solution Explorer, Delete is not an option and Exclude From Project is disabled.
I might have more luck if I check it in first then delete it but that seems very unnecessary. Hopefully I'm just missing something obvious!
How do I delete this new file ("x.h") from my solution?
Yep. It was something obvious.
You can't delete files from the Solution while it is building.
I just tried again and the Delete option magically reappeared. I realized that it has stopped a build since I last tried.
In short, there are three different angles that a user can try to delete a file while a build is occurring and the behavior is different for each.
Undo the file add from Pending Changes -> Nice error messages are given.
Delete the file from Source Control Explorer -> It lets you remove the file as I described in the question but leaves it on disk and in Solution Explorer (same behavior regardless of whether or not a build happening).
Delete the file from Solution Explorer -> It quietly prevents you from shooting yourself in the foot and doesn't explain why.
The right way to do this is to cancel the build (or let it complete), then delete from Source Control AND from Solution Explorer.

How do I permanently exclude the bin and obj folders from TFS 2012 checkin?

I mucked around with TFS settings and I accidentally included the bin and obj folders for TFS 2012 checkin, and even checked them in already. I don't want this because these files change often and aren't meant for inclusion.
I've checked What happened to "Exclude from Source Control" in VS2012. The accepted answer doesn't work because the bin & obj folders and the DLLs inside those folders don't appear in the "Promote Candidate Changes" list, even after excluding them. The second most popular answer also doesn't work permanently. I press yes to all and it removes them from the included changes list, but when I do any action involving rebuilding, they're added to include list again.
I'm looking for a permanent solution which will permanently exclude these folders and the files inside from checkin, and if possible also removes them from the TFS server.
TFS 2012 has the option to drop a .tfIgnore file in your workspace.
Visual studio has a UI to create the file for you:
While you can manually create a .tfignore text file using the above rules, you can also automatically generate one when the Pending Changes page has detected a change.
To automatically generate a .tfignore file
In the Pending Changes page, in the Excluded Changes section, choose the Detected changes link.
The Promote Candidate Changes dialogue box appears.
Select a file, open its context menu, and choose Ignore this local item, Ignore by extension, or Ignore by file name.
Choose OK or Cancel to close the Promote Candidate Changes dialog box.
A .tfignore file appears in the Included Changes section of the Pending Changes page. You can open this file and modify it to meet your needs.
The .tfignore file is automatically added as an included pending change so that the rules you have created will apply to each team member who gets the file.
Or create it from the command line using echo . > .tfIgnore and then open it using notepad.
Another trick is to name the file .tfIgnore. in explorer and save it. You'll probably be prompted if you want to change the extension, the answer, in this case, is: yes.
For Excluding Bin folders ,Tick "Show Solution Changes" Under View options in "Included Changes"
I called in the help of our TFS admin.
We couldn't make a .tfignore file, but what did work was the following:
Check in both folders in TFS;
Delete the dlls and pdbs which are unique to the project from the source control explorer and check in this change.
Rebuild the project locally, try to check in and confirm that there are no pending changes.
the dependent assemblies remain in TFS, but since these rarely change, this isn't a big issue.

Add an already existing directory to a directory in Solution Explorer

I want to add an already existing directory to a directory in Solution Explorer, but whenever I right-click on the directory and select Add => Existing Item, I can only add individual files, but not directories.
How do I add an already existing directory to a directory inside a Project inside Solution Explorer?
Click the 'Show all files' button at the top of the Solution Explorer and right click the folder desired and select 'include in project'.
Drag and drop the folder from Windows Explorer onto your Visual Studio solution window :)
Source here
or simply copy & paste into solution explorer.
VS 2012 seems to distinguish between 'Solution Folders', which are only folders containing either other solution folders, or containing project folders. The drag-and-drop works (with my settings) only for the project folders, and no for the solution folders.
If I add a new solution folder, nothing happens on the machine. If I drag-and-drop a machine folder to the main Solution, it refuses to accept it. If I drag-and-drop the folder to a Solution Folder, I get an error message saying this cannot be done.
Some other answers are missing an important point: if the folder is not in a project in the solution it is impossible to add the folder
This is the solution:
1) Add a new folder to the sln - it does not care that the folder already exists on the disk because this a virtual folder in the sln
2) Add the file to the folder using "add existing files"
When dealing with a solution level folder that has been removed for some reason, and now needs to be added back, open the .sln file in a text editor like notepad++.
Find your "FolderName" in the section that looks like this...
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "NewFolder1", "NewFolder1", "{73ED84FC-F250-4CCC-B267-34CEB67F2883}"
EndProject
Delete from "Project" to "EndProject" ONLY for the specific Project/Folder you're having trouble with.
You may get a message in VS2012 that says your solution has been modified by an external source. Choose the option to "Discard" your changes for the external changes. Lastly, add your solution level folder, and add your project(s) to that folder as existing items, drag/drop them, or copy and paste them, according to your preference.
For those who had a hunch it could be done but weren't able to do it, NOTE: Drag Folder or Files ONTO the name of the Project Name in Solution Explorer in the least
Expand the "Project" item in the menu bar and select "Show All Files". Then locate the folder you wish to add in the Solution Explorer (folders that are not currently included will be light grey with a dotted outline instead of the usual solid icon) right click the desired folder and select "Include in project"
Once finished select "Show All Files" from the Project menu again to return to the regular view.
(This is very similar to Radenko Zec's answer, but does not require the "Show All Files" button to already be present in a toolbar. I would just leave this as a response to his answer, but I don't currently have the reputation to leave comments.)

Why does TortoiseSVN show icon overlays on the folders but not on the files

TortoiseSVN seemed to be slowing down my Windows Explorer a whole lot. So I scouted around and was reminded (via google) that there is a feature available via the TortoiseSVN Settings dialog where you can exclude certain paths from the Icon Overlay treatment.
So I excluded the whole of the D: drive (by putting the line D:* in the "Exclude paths:" area), and then included back my working folder (by putting D:\Petert\PWC* into "Include paths").
But now what happens is that the folders in my working folder get the Tortoise overlays, but not the files!
Well, it so happens that my folder is called " D:\Peter\PWC " - notice that I had accidentally included an extra "t", as in "Petert", in this folder name in the excluded paths as described in my question!
After correcting the typo in the "Exclude paths" text box - voila, my files also get the Tortoise icon overlays.
It seems to indicate something else: i.e. that if you exclude a folder and its subfolders from Tortoise's icon overlay feature, it will nonetheless flag any versioned folders. Which I suppose is quite helpful and probably doesn't take up too much time, etc., and anyway warns you that you have versioned files there which you might like to include via the "Include paths" in the Settings dialog.
Look at TortoiseSVN documentation. It says you may have problems with overloaded images if there are too many ovreloaded images installed in your system by other software.
This is the setting "Show excluded folders as normal" in action. That setting, if active, shows the 'normal' overlay for versioned folders, but since the folder(s) are excluded the status isn't fetched but only the normal overlay is shown instead. This is for performance reasons: it's much much faster to just check for an .svn folder than to fetch the whole status. But people still want to see whether a folder is versioned or not - that's why that option exists.
May not be the problem you were having, but I was finding the overlays were not on the files either and folder overlays seemed to always been green ticked. I found the setting under overalys to include network drives (my respositories were on network drives) and suddenly all the overlays started appearing for everything.

Resources