Good morning,
I've got an ASP.NET MVC VB2008 .NET 3.5 project I'm upgrading to ASP.NET MVC3 VB2010 .NET 4.0 and it seems to be going OK so far.
I have got it into a working state and all the tests run correctly so it is ready to commit to subversion.
The problem is that to get the tests to update for .NET 4.0 I had to put the classes in a different folder, delete the project and recreate the project in the same place then put the classes back into it.
Now TortoiseSvn can't commit the folders as it already has copies of those folders, even though if I take them out and update the project they're not put back into the project.
Is there any way I can get tortoisesvn to overwrite the old files even though they are technically new files?
Regards,
Harry
You've probably lost the hidden ".svn" folders used to keep track of changes.
Tortoise has an "export" feature. Right-click-and-drag the top level of you modified project to a safe place, choose "Export all here" from the menu.
The check your project out again to a new location, and drop the exported copy on top of it.
Delete any files/folder that shouldn't be there using Tortoise's "Delete" right-click menu item.
It should then be OK to check in, then clean up the mess we've made! :)
I had the same problem as yours. What I did was:
delete the old folder that you have for the project
create a new folder and redo "SVN Checkout"
Then you will have the standard menu back to your SVN.
Related
After using a "GetLatestVersion" to retreive my coworker's new project added to Source Control, we realized that the folder structure was incorrect. He deleted the issues on Source Control and everything looked great there. It runs on his end.
Unfortunately for me, even after running the "GetSpecificVersion" and checking all the overwrite boxes, I cannot get the new version of his project on my local workspace.
Ok.
How now do I delete the project on my end without TFS knowing (so I don't have toCheckInanything and TFS doesn't think it needs to bring anything onto the server from my local workspace).
It makes most sense to me to:
- log out of Source Control, close the project and Visual Studio,
- go into my workspace folder and delete the coworker's broken project
- log back into Source Control, bring up the workspace project in Solution Explorer, and re- "GetLatestVersion" and overwrite files.
Has anyone had this problem before? I'm working in VisualStudio 2012
Are you 100% positive that your co-worker did in fact check in all of his changes that "fixed" it? I would start by double checking that. In team explorer, make certain that they do not have any files that need to be checked in under "Excluded Files".
If you have a TFS Build Server, make certain that the CI build (or you can manually run it) was successful. This will at least prove whether TFS has the project buildng correctly.
If you don't have a TFS build server, have another co-worker pull it down to verify that everything got checked in correctly.
If you are sure that they checked in everything ok and it is still not working for you, try pulling it down to a different directory. Also, you can manually delete your copy of the solution through file explorer and then pull it down again (with the overwrite checked).
I have Visual Studio 2012 and when I'm trying to get last version it doesn't work and it says that it's says that "All files are up to date". It is because I deleted file locally after I got it from TFS and I guess in Visual Studios memory it's written that there were no changes from that time I got it and now it doesn't let me download it although I don't have it.
How to "tell" VS that my local folder is changed?
P.S. I guess it can be also done with "Get specific version" but that option doesn't appear to me when i right-click on file I want to get from server.
EDIT:
I found that my workspace changed automatically (or rather with me not being concentrated while making new project), so VS was actually checking other directory all the time. For all those who might have the same problem - check your local path and if you see that it's not good, change it.
Here is how you can change it:
http://social.msdn.microsoft.com/Forums/en-US/tfsversioncontrol/thread/d0c6982f-4f5e-4b1c-830b-3af9fb127922/
You are right, TFS saves what version he gaves you and changing/deleting it without to notify TFS, you won't get anything. The "Get Specific Version ..." is what you need. Therefore rightclick on the item you want, in context menu choose "Advanced --> Get Specific Version". Check the second option to "Overwrite all files even if the local version matches the specified version".
Not saying this is a solution, but I had similar issues after remapping one of my projects. Ultimately what I did was delete my local Solution File (.sln) and re-opened the project via the Project File (.vbproj). After that I was able to see all of my latest file versions that appeared to not be down loading. Once you click save on anything it will re-prompt you to save a new solution file.
i don't know if this is specifically what the OP was trying to accomplish, but here's my story: my machine crashed, had to get it reimaged; once VS2015 was installed, i went to source control explorer, right clicked the branch i needed >> Advanced >> Get Specific Version, checked the "Overwrite..." boxes, clicked "Get" and got the "All files up to date..." message. buster. obviously the code was NOT up to date.
fast forward: i fixed this issue by deleting my workspace's pertinent mapping to code base i needed, saved it, and re-added it.
hope this saves some headaches.
You'll want to Get Specific Version and to check the box to enable overwriting of existing files. That will ensure you're actually up to date.
You can also switch from a server worspace to the new local workspace which should also help solve issues like this.
I am trying to migrate my working sets to a new installation. While searching the web I found this link which says that by copying the file <DATA FOLDER>\workspace\.metadata\.plugins\org.eclipse.ui.workbench\workingsets.xml we can get our original working sets back. I tried it, but it only restores my working sets and they are empty with no database inside them.
What am I missing here? Does any one know how to get all the working sets from old installation and put it into new installation of Domino Designer?
Databases in designer are held as eclipse projects, so you would need to copy project directories inside workspace directory. You can see their directory names in designer just after database title.
Although, I wouldn't recommend that, because different designer versions may have different structure of its content.
I had the same issue. I migrated from the same Notes 8.5.3 release on the old computer to the new computer, so after reading the tips above, I decided to just replace the whole workspace folder under the C:\Lotus\Notes\Data\ folder on my new PC with the workspace folder on my old PC.
It worked! When I opened the Designer client, I had all my working sets complete with database icons. I don't know anything about the workspace folder, so I probably would be cautious applying such an approach if I were migrating to a new release, but since I had not yet started to work on the new PC, I was prepare to reinstall the software if necessary.
FYI, if you don't want to lose your custom commands in the Domino Administrator client when migrating to a new PC or when installing another release of Notes on the same PC, you simply copy the domadmin.nsf database file from the old environment and replace the one in the new environment (if it exists, it won't yet exist if you haven't launched the app after a new install). If you have upgraded to a new Notes release, then open this domadmin.nsf DB in Designer in the new environment and refresh its design from the StdAdminDatabase template (domadmin.ntf).
http://www.lotusguru.com/lotusguru/LGBlog.nsf/d6plinks/20100310-83ESQC
The Notes client being totally closed, backup or restore the following directories :
..data/workspace/.metadata/.plugins/..
com.ibm.designer.domino.ide.resources
org.eclipse.core.resources/.projects
org.eclipse.core.resources/.root
org.eclipse.core.resources/.safetable
org.eclipse.ui.workbench
I am trying to use TFS storing non-VisualStudio source code. Working with Visual Studio 2012 and Microsoft's online Team Foundation Service.
I've setup a TeamProject and mapped its root to a local folder. All it contains at the moment is a BuildProcessTemplates folder in it. (which was created as part of the TeamProject)
I copied my source code externally (using windows explorer) into the TeamProject root folder on my hard drive and since my TFS workspace is NOT a server workspace but rather a local workspace, I was expecting VS to detect the folders/files and show them in Pending Changes window .... yet it doesn't.
Interestingly, new files in the root folder are detected as "Excluded Changes" but new folders are not detected.
What am I missing?
First make sure the newly added folders contains files.
Are there any Detected changes shown in the Excluded Changes section?
Pending Changes > Detected changes link > The Promote Candidate Changes dialog box appears > check the files you want and click Promote.
I can't say I have ever noticed nor expected TFS to automatically pick up files or folders added to a mapped directory as pending changes.
I always just add them manually using the 'Add existing items' option from the source control view.
It may actually do (or at least be meant to do) the auto-detection, but I can't say I've ever relied on it. I don't think it's something to fret too much about - adding them manually is easy enough, and the 'Add existing items' option is usually smart enough to show you which files are not already under source control, so even if you need to add even more files later, it shouldn't be too much extra effort.
Using Xcode 4.0 sometimes when I remove resources from the project they still appear in the app when I run it, both in simulator and device. I remove the resource from the Resources group by removing reference only, but afterwards also remove the actual file in Finder, and yet the resource magically appears in the app.
Doing a project clean did not help.
Xcode 4.0 has a lot of problems managing its projects' "derived data". Try opening the Organizer (Cmd-Shift-2) and clicking the Projects tab. Select your problem project in the source list, then find Delete button next to the Derived Data section near the top. Go ahead and confirm deleting the derived data, then build again (this will take longer as Xcode re-indexes your project).
Does that fix it?
A bundle (and hence also an app) is just a directory, as seen from Unix and Unix-derived tools' point of view.
My guess is that they are still in the bundle because Xcode left a copy there once, and removing the originals in the source directory does not remove the copies in the built app bundle.
If you delete the app from the build directory (or the build directory altogether), you shouldn't see them any more inside a freshly built app.