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!
Related
We've updated to Visual Studio 2017 and switched to Team Services (VSTS) as our source control. I've migrated a few old projects and am using the Microsoft Installer Project extension to provide compatibility for the original setup projects.
However, there seems to be a potential issue with source control when working with the setup projects. Attempting to make any change results in the error:
The command you are attempting cannot be completed because the file 'Setup[Productname].vdproj' is under source code control and is not checked out.
Modifying files of other projects within the solution work correctly and trigger checkout from the repository.
I have not been able to determine a way to properly check out the setup project and work with it under the new source control. I'm unsure if it's a bug with the extension or if it simply lacks support for VSTS.
Has anyone successfully been able to work with setup projects (.vdproj) in conjunction with VSTS? If not, is there a workaround?
Edit:
Image of context menu:
You can apply the following workaround, since it seems to be a bug in the installer extension:
Choose 'Open file in File explorer' in your context menu
Open the project file in your favorite texteditor
Make a dummy change (adding a space character in an empty spot is enough)
Visual studio will prompt to reload the project and has explicity checked out the project file.
see also here
I submit a feedback here: The command you are attempting cannot be completed because the file 'Setup[Productname].vdproj' is under source code control and is not checked out
The workaround is that you can check out the project manually. (Right click the installer project > Check out for edit)
I am trying to run an Xpage locally (in Chrome if it makes any difference) from a local NSF and am receiving the error:
Build path contains duplicate entry: 'org.eclipse.jdt.launching.JRE_CONTAINER'
I have copied all the ExtLib Features and Plugins to the correct directories as required.
Anonymous is set to Author.
I cannot find any information on how to resolve this. There was an open ticket on OpenNTF 6 years ago but no resolution.
[Update]
As Jesse Gallagher pointed out on Twitter, you can access the .classpath file without going through the ODP setup via the Navigator perspective. I would still recommend setting up source control since it gives you:
local change history in DDE (even if you don't use the ODP in git/hg)
the ability to track any changing file during development, aka- a rogue change to your .classpath file (I recommend installing Cameron Gregor's Swiper plugin)
is fairly easy to set up
as a developer, version control is the best way to cover your butt
[/Update]
I believe you quite literally have a duplicate entry in your NSF's build class path. This has to do with the Eclipse version Domino Designer is based on is being confused by its defined class path. I recommend the following:
if you don't have it set up already, set up source control for your NSF
open the (hidden) file .classpath, which can be found in the root of your On Disk Project (ODP) folder with a trusty text editor (Notepad++, etc.)
search for org.eclipse.jdt.launching.JRE_CONTAINER
if you find more than one, you will need to deconflict your class path (aka- remove one; it may be best to make a backup of the file)
if you don't have "Build Automatically" checked (in your Project menu), you may need to open Package Explorer and right-click your ODP, then perform a "Sync with NSF"
You should be able to de-conflict your build path via the Project > Build Path screen, but this is an easy way to search the whole thing in one shot.
Here's an example the .classpath file from a working app.
An example of a situation where others (using gradle, in this case) ran into a duplicate issue with org.eclipse.jdt.launching.JRE_CONTAINER.
Setting up source control with an NSF, right-click NSF, Team Development, Set Up Source Control:
Note: If you need a little more info on how to set up source control or want to know more about where to park the ODP (aka- if you haven't done this before), I recommend checking out David Leedy's Notes in 9 episode 131: Using SourceTree for Better XPages Source Control. Even if you don't use SourceTree, it's worth it to understand that the ODP should not be placed in your Notes Data directory, etc.
I am using eclipse 4.2 and Subclipse 1.8.20.
I am trying to add the contents of /WebContent/WEB-INF/classes to version control (this is also the default output folder of my project).
First let me state that this is possible with TortoiseSVN. I do understand why by default Subclipse ignores this directory, and I tried to change the Team settings, but I am not seeing a relevant entry for *.class files:
Is this at all possible with Subclipse?
More info:
Old an unanswered similar question: http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=473163
Same topic but opposite question: How can I ignore build directory in Subclipse?
It is a horribly bad idea to version your build directory. Every time Eclipse does an auto-build it will cause all of the files to need to be committed again.
To answer your question, all Eclipse team providers automatically ignore any resource that is marked as "Derived" by Eclipse. The Derived flag is set on files that are created by the Eclipse builders. If you select one of these files that are ignored in Eclipse, right click and choose Properties. Navigate to the Eclipse Resource page. There will be a bunch of checkboxes. You should see that one of these is labelled Derived and will likely be checked.
Do not try to change the checkbox value. I am just pointing out where you can see and confirm this.
I've recently moved to using TFS 2012 and have edited a couple of files and checked in without any problems. However, I've just started work on the EF data model and despite being able to open the file the "Update Model From Database" option on the Entity designer right-click menu is greyed out / disabled.
I'm a bit baffled by this. I've tried checking out the file with the "Allow other users to check out but prevent them from checking in" but that doesn't make any difference. Nor does checking out the whole folder the project is in.
Does anyone know what I'm doing wrong?
EDIT:
I've discovered that if I create a project in TFS and add an entity model to it then I can update it. However, if I import an existing project into TFS and then try to edit the .edmx file then that's when the problem happens.
I managed to work out the problem, I'll post it here just in case anyone else suffers with this:
The project wasn't set up properly. I was editing the files in the "local path" having not opened the project first (seems kind of stupid now, but this is my first time with TFS and I'd assumed opening the project in TFS opened it as a project in VS).
When I double-clicked on the .csproj file within the Source Control Explorer I was prompted with: "The solution you have opened is under source control but not currently configured for integrated source control in Visual Studio. Would you like to bind this solution to source control now?"
Clicking "Yes" opened the project correctly and I could run the update the model from the database.
I am using eclipse 3.5.2 with Team Foundation Everywhere plugin (TFS plugin).
I have several blackberry projects in my eclipse workspace which i have successfully added to TFS. However I have found that the BlackBerry_App_Descriptor.xml is not being updated in TFS when i make changes to it.
For example when I change the name and version number of the application TFS see's no change in the file so when I check in the server version is still the old data. We are developing on several machines so having changes i do on my machine not propigate to the others is causing problems.
Does anyone know why this is happening? I can see from visual inspection of the .xml file that it is changing but why does TFS not considered it any different?
I have tried manually 'check out for edit' on the file, then change the name and check it back in. But it sees that there are no changes and disreguards my checkin.
Thanks,
Stephanie
Incase anyone else runs into this, it seems that the eclipse plugin for TFS is having issues with comparing XML files. If i manually change the XML contents and save to disk. Then do 'Compare local with server version' it will say 'files are identical'. What I ended up doing was removing the file from TFS. Doing my edits on a local version then readding it. It gets the updates into TFS so the whole team gets the same version. Wish it would just work though because now everytime we want to change anything in an xml file its a long process instead of being a simple update/checkin