Source control management

Hello,
I need some free souce code management tool where i can see the repositories and can create new repositories. I got one but when i am going here step by step, it is not working for me. Please suggest me some other good one for windows authentication.
http://webcache.googleusercontent.com/search?q=cache:http://bonobogitserver.com/install/
Thanks
chirag

Hi,
Are you using Visual Studio? For the Visual Studio issue please ask in the Visual Studio Forum:
Visual Studio Forum:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=visualstudio
Thanks for your understanding and support.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Project management + Source Control

we are using labview 8.5 and not well known source control in a team environment. I'm not sure if it is the souce control that I'm using or other searsons, but I had so much trouble using those combination. I want to know what others thought about project management and/or source control in general.
Thanks,
- Jimmy
- Jimmy

Hi!
   Actually, I've never merged, since I'm the only LabView guy on our development team
   I absolutely agree with the fact that SVN is a good tool, but I should confess that I didn't spend much time in evaluating many other tools (never tried MS tools), for this I rely on my colleagues' opinion.
   I can report that SVN is being used in a graphic studio for pictures versioning of course, they don't need to merge images There's virtually no limit in SVN use...
graziano

Source Configuration Management / Version Control

I was wondering what the Forte raving masses out there are doing about Source
Configuration Management and Version Control type of issues?
Have you been able to implement or "skunk work" a packaged product with your
Forte development environment?
Our shop consists of WindowsNT Forte developers coding for predominantly
Windows95 clients and a HP UNIX Central Server. At this time we currently use a
home grown "system" to handle Source Configuration Management and Version
Control issues. We are now looking to see if there is a better way to do this.
We've identified several Industry Standard packages (SCCS, CVS, Microsoft
SourceSafe etc.) and still haven't found anything very useful.
What I am seeing is that all of the packages so far have direct hooks in C++,
Visual Basic etc.
I have yet to see something with Forte hooks.
Kelsey PetrychynSaskTel Forte Technical Analyst
ITM - Technology Solutions - Distributed Computing (OTC)
Tel (306) 777 - 4906, Fax (306) 359 - 0857
Internet:[email protected]
Quality is not job 1. It is the only job!
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Kindly specify the email address to apply to for the mentioned job

Managing OSB services with source Control

I have a number of services developed within an OSB and all the files .proxy , .biz , etc are stored in my source control system. This works perfectly fine when one team is working on one service.
However now we are looking at branching the service to support multiple development efforts. Which means team A could be making changes to MyService.proxy and team B could be fixing bugs in the same proxy on a different branch.
We want to periodically baseline the branches.
I cannot see any documented approach to how we can merge these changes. Comparing the files as XML is ugly and extremely high risk. Having looked in this forum I have not much discussion on this in the past.
I foresee multiple merge conflicts, overwritten changes and angst ahead.
If anybody has dealt with this and has some clever approaches I would be grateful
-Murph

Hi Prabu,
Thanks that is one approach to minimizing possible conflicts. The difficulty we have is that we are used to multiple teams working on multiple branches and managing merges using SCM tools and diff tools. Once you have a conflict in the OSB (specifically at a proxy level) then there is real problems.
I am toying with the idea of locking mechanisms whcih I have not used in a while to avoid losing work with conflicts.
Cheers
Murph

Visual Studio 2013 slows down + crashes when using Source Control features.

I have spent two full days trying to resolve this issue but no luck so here we go,
I have created a project using Visual Studio Team Foundation Server plug-in in the past. Later on I switched to
Microsoft Git Provider.
Now when I connect to that project in the Team Explorer and double click on the solution to work on it locally it somehow changes the plug in to Microsoft Git Provider automatically and of course I can't
Commit/Commit and Push since I receive following error in the Team Explorer,
An error occurred. Detailed message: Failed to open directory 'C:/Users/.../AppData/Local/Application Data/'
Manually changing the plug-in to the Visual Studio Team Foundation Server
results in a broken Team Explorer as below,
With Settings leading to an empty pane, and also a warning in the Team Explorer's Changes page telling me the message below if I click on Pending Changes...
Microsoft Git Provider is not the current Source Control plug-in. Change Plug-in
And manually selecting the solution from Solution Explorer, right click and
Add Solution to Source Control, leads to never ending hour glass and (Not responding) visual studio.
New Projects
Creating a new project is straight forward, unless I "Add to Source Control" is checked. If so, again never ending process if Microsoft TFS plug-in is selected in the tools and eventually me Ending the Visual Studio task. And a VERY long process
(40+ mins) if I have chosen Microsoft Git but that finishes successfully rather.
New TFS project from Team Explorer
If I create a new project in my Online Web Studio
Click on Open with Visual Studio Link => Opens and connects to a my newly created TFS in team explorer.
Clicking new in Team Explorer under Solutions to create a new solution and bind it to this Repo
leads to straight crash of Visual Studio and restarting attempt of VS.
So I really can't use Source Control from visual studio other than cloning GitHub's existing repo's on Visual Studio and Committing my current Microsoft Git managed projects.
I have attempted
Repairing Visual Studio (no luck in results)
Devenv.exe /setup (no luck)
Trying to scrap the SCC info on my solution then at least it won't get picked up by source control then I can Check it in as a new project. (no luck and the solution picks the Microsoft Git upon opening it by clicking on the .sln file.) I have followed
these steps in this stack overflow answer.
And lots of mucking around like removing my workspaces almost Thousand times and putting them back, binding and etc.
I am really stuck on this and it's holding me back from staring a new project (which is problematic using Adding to Source Control) and unfortunately is dependent on the old project (which is developed under Visual Studio Team Foundation Server Plug-in which
is throwing tantrums)
Would like to hear you pro-s input on this
Using
Visual Studio 2013 Community edition (recently switched from Pro to Express to Community)
Windows 7 (64-bit)
Git tools
Git windows installation
Nuget Package manager
Visual Studio Log File
http://filesave.me/file/50620/log-txt.html
Mehradzie

Hi Mehradzie,
Based on the description, seems you're working with Git team project in Visual Studio Online(formerly Team Foundation Service). I'd like to know whether you mean Visual Studio Git command tool as the plug-in, and if you're trying to create solutions/projects
with Visual Studio and add them to the created Git team project.
From the screenshot, you're not connect to the Git team project by using Team Explorer. To work with Git team project locally, you can follow the instructions as below:
Connect to Git team project by using Team Explorer, after that you might install Git tools if you connect to the team project for the first time
Clone the remote Git repository to a local git repository and set the path to local git repository
Create a solution and select Git source control, also saved to the local path of the local git repository
Select your branch, and then click "Changes" and Commit the changes
Click "unsynced commits" and push the commit to remote git repository
You can also refer to the links below for more information about getting started with Git in Visual Studio Online.
http://www.visualstudio.com/en-us/get-started/share-your-code-in-git-vs.aspx
http://blogs.msdn.com/b/visualstudioalm/archive/2013/01/30/getting-started-with-git-in-visual-studio-and-team-foundation-service.aspx
If you still have any other concerns, please elaborate more details about your scenario. Thanks for your understanding.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Can teamcenter community be used for source control?

I have this new tool called teamcenter community and I'm trying to see how well it will work with source control for labview. I haven't learned how to use it fully yet, but when I try to open a vi get the error message:
The document could not be opened for editing. A windows SharePoint Services compatible application could not be found to edit the document.
I'm using 8.5. Is this a feature that was added to a more recent environment.
Is this feature a possiblity? So far I've been able to use it to manage file, but haven't had success with folders.

Steve:
Unfortunately, teamcenter isn't supported in LabVIEW (past or present). A full list of supported clients is located in this KB. While it may be possible to use other clients, there hasn't been any testing done with them, so they may very well not work with LabVIEW.
Caleb Harris
National Instruments | Mechanical Engineer | http://www.ni.com/support

What files should not be checked into Source Control?

Good afternoon.
Running RoboHelp 11, integrated with Team Foundation Server and Visual Studio 2010.
When my two colleagues recently "got" the latest project files from Source Control, they also got items that had been removed or deleted. For example, I had removed all conditional build tags from my project, but their version still included the build tags. Eventually, thanks in part to an old post from Peter Grainge, we realized that the PSS in Source Control contained a lot of that old information. We deleted the PSS and stopped checking it into Source Control. Problem solved. No more conditional build tags or unwanted Single Source Layouts, etc. (I think the PSS got checked in by our Release Engineer when he was trying to solve some other problem. Two years ago it was not being checked in.)
I vaguely remember reading something somewhere once upon a time about not checking certain RoboHelp project management files into Source Control. So far I've not found any such information in the RoboHelp Help or online.
Does anyone know where I can find a list of RoboHelp HTML project management files, such as the PSS file, that should never be checked into Source Control?
Many thanks.
Carol Levine

Look in Snippets on my site.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Service Control Manager - 7000

I installed Oracle Client on a Windows Pro 2000 computer. In the Event Log I received next message:
Source: Services Control Manager
ID: 7000
Failure at start of service "OracleWebAssistance0" because of a mistake. The service has not answered inquiry in due time.
I have a Oracle8i on Netware 6.0 server. In the Services list OracleWebAssistant is working.
What's the problem?
Michael S. Androsov
EXPOCENTR

Hi Santosh,
Does this issue occur in your personal computer or in domain environment?
Please take the following steps for troubleshooting:
1. Run gpedit.msc
2. Edit Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assingment -> Profile system performance
3. Add Administrators and NT SERVICE\WdiServiceHost
For more information, please refer to the following thread similar to this issue.
http://social.technet.microsoft.com/Forums/windows/en-US/e4d701f5-a63f-4fee-9b09-89ea9b07e1c3/the-diagnostic-service-host-service-failed-to-start-due-to-the-following-error?forum=w7itprogeneral
Hope it will be helpful.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

APEX Version/Source control

Hi,
I would like to know how other people are managing this. We have developed our own way which works 99% of the time however there are some flaws.
We require that more than one user be working on an application at a time and that these different pages can be released to production at different times.
We have some pretty large applications, some business critical.
1) We export the full application into our CVS application
2) We export each page individually and assign module numbers as we do with apps forms etc
3) Initially the full application is released to prod
4) Any subsequent page changes are done to the page export and that page only is released. The revision is increased on that page module.
5) If any changes to shared components are made then the full application is released.
All updates are stored in packages which we manage as per our normal apps packages without any problems. Our problems are with apex applications.
Let's say user A has exported page 1 of an application and is working on a large change.
User B is also working on a very small change which involves adding a new item to a list.
User B wishes to release his change but cannot do so at page level because of the shared component - he must release either full app or do a separate export for that component.
He cannot release the full app because user A is still using it.
The only thing he can do is do an export of the components and then import that. This is then not version controlled. It is not acceptable for us to have to export and manage every single component individually (I know you can do them as one whole but then if two users are modifying shared components then the issue arises again!)
There is always a mis-match between the application full export and the pages. If we ever had to recover an app, our strategy is to install the full app and then the individual pages. This isn't ideal however so long as we keep things up to date then we have to accept it.
Does anyone have any better procedures than this?? With APEX becoming more and more popular then I believe it needs to become a little more formal in this area. Or perhaps I am just missing something?
I've read the thread Source/version control with APEX? but it doesn't really relate to the issue above.

Hello Chris,
I'm not sure how you organized your project, but a typical APEX project for me has different components:
- PL/SQL where all business logic is in
- External JavaScript files to do some client side things
- External CSS files to handle the look and feel
- APEX application(s)
So for all of the above you want source control. We use Subversion. For the first three (plsql, javascript, css) I guess it's trivial how do this as they are just files.
For APEX you can export your application every night (and even split it into different components if you want). So that gives you one or more files as well which can be loaded in Subversion.
If you want to do team development in APEX; we use following features:
- Locking of Page
- Build Options
- Entering Comments
If it's a very big project you might want to split your APEX application in multiple ones which can work together (same Authentication scheme, same Theme etc. by Publish and Subscribe option).
APEX itself is also build in APEX, and they use different applications as well, but you don't see it in APEX itself, you just see it by the changing APP number in the url.
I'm not sure how familiar you are with all of the above, but this is roughly the way we do it.
Hope that helps and give you a clearer view.
Regards,
Dimitri
http://dgielis.blogspot.com/
http://www.apex-evangelists.com/

How to store SQL sproc, scripts from Visual Studio 2012 in source control TFS?

I have VS 2012, SQL Management 2012. From VS 2012, how do I store my sproc and table scripts in TFS source control?

Hi bthumber,
Regarding TFS issues, I would like to recommend you post the question in the Visual Studio Team Foundation Server forums at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=vstfs
. It is appropriate and more experts will assist you.
Thanks,
Lydia Zhang

Siebel Tools Business Services for Source Control verification

One of the challenges with integrating Siebel Tools with a Source Control repository is that it is far too easy for an user to check in code to the Siebel Repository without that code getting checked in correctly to the Source Control repository (i.e. Subversion).
They can turn off the source control, have it setup incorrectly, or have some permissions issues which they don't know about. Since Siebel does all check-ins as an after though you can have the two code repositories (Siebel Tools and Subversion) out of sync.
Was wondering if anyone out there has used any of the out of the box Business Services (that start with Siebel Tools..) to build an automated process that would compare the objects in Siebel (via SIF-XML) to the files that got stored in the Source Control repository.
Or how have you mitigated this risk?

There are 2 things required to meet your need:
1) be able to generate a config.jar file from the resources in the source control in a command line tool.
2) deploy this jar file into alsb
WRT 1) this is something we want to address by adding an ALSB ant task, but it's not available today. You best bet is also to put the config jar in the source control.
WRT 2) this is already there. You can use the MBean APIs or WLST scripts to deploy the JAR.
Gregory Haardt
ALSB Prg. Manager
[email protected]

Source Control continued...

Using the Repository hooks, one can trap workspace integrations and create
.cex and .pex files of the changed objects, which can be read into the SCM
tool. Right?
But how do you handle the situation where a class has been renamed? How do
you deal with all those other classes that have attributes that are of this
renamed class type? What if you want the full source code of 6 weeks ago,
before several big changes including class renames? Can you then recreate a
complete .wex file, where all the changes before 6 weeks ago are included,
but all changes since 6 weeks ago are excluded?
Is is perhaps more feasible to create a full .wex file every day, or every
week, and store that in an SCM tool? But then, what's the use of these
repository hooks?
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch

It sounds like you simply store the whole repository file in your SCM. How
else do you store partitioning schemes, which can't be exported as far as I
know.
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
-----Original Message-----
From: Roland Ottersbach [mailto:roparcs.de]
Sent: Monday, November 27, 2000 9:06 PM
To: Rottier, Pascal
Cc: 'Forte Users'
Subject: Re: (forte-users) Source Control continued...
Hi everyone,
I'd like to take part of this discussion, as we developed a integration to
continuus configuration management suite
from continuus software. This integration goes beyond simple version control
system. It handles the software
issues as any other integration using the SCM-Hook. But it overs a lot more:
As Continuus overs as one of a few providers task based CM we support full
support of task based CM as
simple as it gets. The more we handle different releases of software
products.
The integration takes care of partition informations as well, so that with
your
sources the deployment information
and the application information is stored and can be restored any time.
Guess
you have to go back to a former
release of your product and you have released this software to certain
customers: You would like to restore your
software at that point completely, including partition information. We can
do
this.
But the best thing about this integration is, that you don't care about
retrieving your software out of the CM Tool manually
and place it back in a production repository. The integration cares for this
too. By a click you get a brand new repository
at any release you've integrated before and want to go back to as a manner
of
maintanance or merging.
Fell free to contact me, if you like.
We've choosen Continuus, because we know it a long time. Is very powerful
but
sometimes a little bit sophisticated
too. Nevertheless it overs a lot of things you would like to use, if you go
deep into configuration and change management.
Regards
Roland Ottersbach
Workflow and Change Management
parcs IT-Consulting GmbH (ww.parcs.de)
Birlenbacher Strasse 14 K
Germany
eMail roparcs.de
Mobile 0049 (0) 171 374 5171
Telefon 0049 (0) 271 870 6421
"Rottier, Pascal" schrieb:
Using the Repository hooks, one can trap workspace integrations and create
.cex and .pex files of the changed objects, which can be read into the SCM
tool. Right?
But how do you handle the situation where a class has been renamed? How do
you deal with all those other classes that have attributes that are ofthis
renamed class type? What if you want the full source code of 6 weeks ago,
before several big changes including class renames? Can you then recreatea
complete .wex file, where all the changes before 6 weeks ago are included,
but all changes since 6 weeks ago are excluded?
Is is perhaps more feasible to create a full .wex file every day, or every
week, and store that in an SCM tool? But then, what's the use of these
repository hooks?
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com--
Roland Ottersbach
Workflow and Change Management
Parcs IT-Consulting GmbH (www.parcs.de)
Birlenbacher Strasse 14K
57078 Siegen, Germany
Phone 49 (0) 271 870 6421
Mobile 49 (0) 171 374 5171
Email roparcs.de

Source Code Management

Hi
I am busy designing a new Java environment for our company. We are migrating from Forms to JEE. I would like to know what would be the best practice (if one exists) wrt source code management. Currently I am going with the following,
1. All original source code saved on development application server (Linux).
2. Use SVN to manage source from development application server.
I am not totally convinced that this is the correct method of managing source code.
What are my options?
Should the source be placed on a seperate file server independant of my application server?
Kind regards.
Leon.

Development servers is used to be quite unstable sometimes so I would prefer to store the SVN repository on some kind of file server, where a file backup procedure is already implemented. If you're using some kind of cruise control or automatic testing you could checkout the source code to the development server to run it from here or to build distributions.
I'm familiar with both CVS and SVN and think that SVN is serving us best. We're just using a file based repository, on a network drive, protected by the normal file system permissions mechanism. I'm almost always using Tortoise SVN as client but the SVN client in JDeveloper is just fine, but I think the Tortoise SVN plugin in the explorer is just better.

The project file is not bound to source control, but the solution contains source control binding information for it.

This may be more of a SQL Server Management Studio question, but I couldn't find a SSMS forum...
I've got a database solution that contains several projects. They're just to keep track of changes to stored procedures, triggers, views, etc in a few databases I maintain. There is a problem with two of the projects though. No matter what I do, I can't seem to get them bound to source control right. When I open the solution, I get:
The project file is not bound to source control, but the solution contains source control binding information for it.
With two options, use solution binding and remove solution binding. If I keep the solution binding, everything works fine. But it's really annoying to have to deal with every time I open the solution. If I remove the solution binding, the projects are now unbound again. If I try to fix them (using the change source control or Add Selected Projects to Source Control options under the File->source control menu), I just end up in the same situation. I've even tried deleting the projects and re-creating them from scratch, then re-adding them to VSS. If I open the solution files in a text editor I can see the SCC tags in every project, but these two. Since I can't manually add the tags, and Management Studio itself only seems to want to bind them the wrong way, I'm getting really frustrated.
Can anyone point me toward a way to bind these so they work like the rest?

However, that does not appear to be the ONLY cause of the problem. I am a single user and only using TFS2010 and SSMS2008R2. My issue is that I wanted a solution file for each project so that they could managed independently, and a super-solution
file that contained all projects, so that I could perform system-wide searches and cross-checks.
I solved the problem by:
1. Choosing the option to use solution binding, then
2. Adding another project to the solution. This forced the re-write of the solution file.
3. Adding another script to the project. This forced the re-write of the project file.
4. Checking in all changes.
5. Deleting the new script and the extra project,
6 Checking in all changes.
This appears to have solved the problem.

Re: Source Configuration Management / VersionControl

We have tried using Forte SC hooks with a commercial package (CA Endevor)
to manage application releases but have reverted to homegrown scripts and
Unix SCCS. As far as controlling source access in the repository we find
that Forte's checkout/integrate feature works fine.
David Campbell,
CSC Australia
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi,
The Source Control is supported from MII 12.1. The NWDI can be configured in SAP MII for version control.
You can visit this link for more comprehensive details.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0d998ba-2076-2d10-b3be-90909838e4d2?QuickLink=index&overridelayout=true
Regards
Anuvrat

Source control management

Similar Messages

Maybe you are looking for