Why can't I add Shared Binaries to TFS 2008 Source Control? - version-control

I have 2 TFS projects on the same server (ProjectA and ProjectB). Both have the following structure...
$/ProjectName/Dev/Source/ApplicationName/
$/ProjectName/Dev/Source/SharedBinaries/
In ProjectA I can drag dlls into the ShareBinaries directory. In ProjectB, however, I cannot. TFS presents me with the 'Add to Source Control' dialog in which all the dlls are in the 'Excluded items' tab. Each dll has the description 'The item cannot be added because its destination path is cloaked.'.
I can see no difference between how the 2 projects are setup. Help, I'm stumped!

Take a look at your workspace mappings. It sounds like when you drag & dropped the files, Visual Studio created an extra workspace mapping.

I edited the Workspace and added a specific mapping for:
$/ProjectB/Dev/Source/SharedBinaries/*
I also then renamed the existing windows folder, added the SharedBinaries folder through TFS, checked it in then, finally, I was able to drag and drop the dlls. Not quite sure which bit of all that was the key though!

Related

In ABL Web App project, which files should be tracked in a source control?

So we're just starting with a new ABL web app with 11.6 in developer studio.
For now all files in the project structure have been added to the repository. We're already ignoring all rcode, but I wonder what else can be left aside.
Our current project has the following folders:
Any thoughts?
Make sure that your Progress temp-files (-T startup parameter) are outside of the project folder. Ignore crash post mortem files (procore* and protrace*).
Include .project, .propath and typically I'd include .dbconnection as well - assuming the team uses identical DB connection names here.
Everything else should IMHO be under SCM.
The procedure libraries don't need to be in source control. PASOE Content is created along with the project, so you only need to save the files you change. And obviously any folders where you create source code should be in source control, so save the Src folder and subfolders.

I need Netbeans help. NO project's -src node appears so no source files--only -Libraries node shows

I hope it's OK to ask this here. Netbeans forums isn't responding. If not, I'll delete this or ask for it to be deleted. I'm desperate so I'll face the wrath, if any.
I moved my Netbeans projects folder from one directory node to another to make backing up all my stuff easier. BAD MOVE.
Now when I open a project using Files | Open project (ctrl-shift-O) NO source files appear because there is no "+Source Packages" node to expand.
It looks like this for all projects, e.g. one named GBL:
Projects
-GBL
+Libraries
It doesn't look like this anymore:
Projects
-GBL
+Source Packages (How do I get this back?)
+Libraries
The Netbeans Properties for each project shows me the path it's using. Windows 7 Explorer shows me that the src, build, and nbproject folders contain files and ALL the source files are in the src folder for that path.
What have I done and more importantly what should I do to get back to being able to open a project normally?
(I've tried recreating the original Netbeans folder and using Windows Explorer to copy an entire project folder into it but: same result--all I see is the Libraries node under the project's name node.)
I just tried to Clean (and also Build) to see what would happen. Error:
ant -f C:\\Users\\Dov\\Documents\\NetBeansProjects\\BasicShirt -Dnb.internal.action.name=build jar
C:\Users\Dov\Documents\NetBeansProjects\BasicShirt\nbproject\build-impl.xml:[u]231[/u]:
Must set src.dir
I just Set Configuration by right-clicking the project's name and provided a path to the src folder.
NOW I SEE MY SOURCE FILES BUT NOW THIS line in the .xml file is flagged with similar message:
<fail unless="[u][b]test[/b][/u].src.dir">Must set test.src.dir</fail>
NOW what do I do? (Netbeans 7.4.)
If I could get rid of the 7.4 automatic creation of +Test Packages, I might be OK.
If you can help, I'd be very happy.
(I'm considering re-installing 7.3 if available or removing and reinstalling 7.4 and try to avoid the "testing" requirement, but there goes all my many tweaks of 7.4.)
Well, after considerable frustration with the problem, I solved it, essentially.
It's here, in total. My synopsis plus how it helped me follows. In short, I had to set up a new java project based on existing sources using the New Project Wiz and simply direct Netbeans to the sources.
File > New Project
Choose Java Project with Existing Sources.
Type a (new) project name and ...
... make the Project Folder contains the path to where you want the new project to be stored. (For me, this is the folder where Netbeans has been able to find my sources.)
Click Next for the Existing Sources page of the wizard and ...
5a. ... in the Source Packages Folder pane, click Add Folder and ...
5b. ... navigate to your sources and select the source root folder.
Clicking Next goes to the Includes/Excludes pane, which I didn't need to use.

TFS Add a folder but now the files or folder contained within it

I have a mapping as follows
$/Root/App/Folder
mapped to C:\Root\App\Folder
in C:\Root\App\Folder I have an existing folder called New that I want to add to source control but I don't want to add the files (or sub folders) contained within it
Is this possible?
I use TFS Power Tools for adding folder structures to source control because it works easy and fine with the windows explorer.
The mapped folders get a little green icon, only right click on new folder and select "Team Foundation Server" and "Add".
You want to use a "one level mapping" (using an asterix) - this will map the folder, and all the sub-files under it, but not the sub-folders. Once you've setup the workspace mapping, then you can add just the folder to TFS - everything else will be ignored.
For example, your workspace mappings would look like this:
$/Root/App/Folder --> C:\Root\App\Folder
$/Root/App/Folder/New/* --> C:\Root\App\Folder\New
For more information, see this blog post on Workspace Mapping Improvements in TFS 2008

Source Control Association Bindings Problem

I've started working on an existing project at my company that was check into VSS 6.0 about a month ago. It was built using Visual Studio 2005 and C# and references all point to .NET 2.0. I went into VSS and set my working folder as per usual and got the latest version. I've opened this project at which point I'm prompted with this:
The solution appears to be under source control, but its binding information cannot be found. It is possible that the MSSCCPRJ.SCC file or another item that holds the source control settings for the solution, has been deleted. Because it is not possible to recover this missing information automatically, the projects whose bindings are missing will be treated as not under source control.
I click "OK" and that prompt is directly followed by this one:
The associated source control plug-in is not installed or could not be initialized.
That presents me with these options:
Temporarily work uncontrolled.
Permanently remove source control association bindings
How can I rectify this situation? I'd like the project to remain in VSS under control. Any Ideas?
Go to File -> Source Control -> Change Source Control, then select each project that you have under VSS and "Bind" it to the correct directory in VSS, it will prompt you for vss user name and password
instead of rebinding 100s of files, have a look at this solution:
http://regev.wordpress.com/2008/03/29/binding-to-source-control-issue/
"instead of getting the latest version through the source control client, you should have opened Visual Studio and choose: File|Source Control|Open from Source Control… this would have created the solution on the second machine with no binding problems."
Load the solution as usual and then right click on the unavailable project. Then edit the project file to comment the source control settings in the xml.
Then reload the project.
Everything is simple:
first of all, add missing project via Source Control Explorer.
Then, make check-in.
Then add it into solution and make check-in of changed solution file.
Voila!

In Eclipse, how can I move all my source files to a different folder without screwing up the project?

I have created my ActionScript source files in a folder on a Mac (I normally use Windows), and somehow managed to make an Eclipse/FDT project that can see them.
I now need to move them into a svn checkout of an existing project to get them under source control.
I just can't work out how you do this without losing all references in the project.
I'm new to Eclipse and don't really understand any of the terminology (e.g. workspace). Does Eclipse have project files or are they all hidden? Can the project file be moved?
Help me stackoverflow, you're my only hope.
Update:
From the FDT Flash Explorer window I can only seem to be able to move files/folders within projects that exist. Should I create a new project in the place I want first?
Should I move them from within Eclipse or from the file system? Do I need to setup a new workspace afterwards?
The project folder has 2 hidden files: .project and .classpath that have all the info of the project. You just need to copy those files along with your project files.
For instance, you have a project folder in workspace/myproject/, and you want to add it to a checkout svn folder, you just need to copy the complete folder content to the checkout and then add all the files to the svn (including the project hidden ones) and finally commit.
From now on, when you checkout from that svn, you will have the eclipse project files, so all you need to do is create new project, and select the option that says that you already have a project folder with the source files (I'm not near an eclipse IDE to tell exactly the steps, but it's something like this). Eclipse will then import the project with all the settings you had previously defined.
I hope that this answers your question.
Try refactoring your project. Rightclick on the folder to move and then choose Refactor->Move. Don't know if this will solve your problem but it will try to change the references in all projects according to the move.