Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - sperry

Pages: [1]
1
General Board / Version Control Not Working
« on: March 23, 2004, 08:19:59 am »
I am trying to integrate my EA project with Source Control.  This process is very confusing ???.

I start with Package Control\Configure to specify the XML file name.  (NOTE: I do not check the Version Control checkbox at this time, since it always generates the same error about the file already being in Source control, but marked for deletion.  It doesn't matter what filename I put in, the same error is always displayed.)  I then select Package Control\Save Package to file.  Once this is complete I add the new XML file to Source Control manually.  I then attempt to perform a Package Control\Get Package but the XML file I just added is not shown.  I must reload the project in order for that dialog to refresh with the XML file I just added to SourceControl.  I then do a Package Control\Get Package, selecting the XML I added to source control.  EA imports the XML file without issue.

I now want to edit the package, but I noticed that EA thinks the package is checked out.  I then attempt a check-in.  It goes through it's check-in process, but when I look at the Package Control menu, it still believes it's checked out (The check out menu option is grayed out and check in and Undo checkout are enabled).  I then try manually checking the file out and reloading my project.  I execute the check in again, and again it does it's processing and in SourceControl I now have a new version.  When I then view the Package Control menu, it still thinks the file is checked out.  I try reloading the project, but to no avail, it still thinks the file is checked out.

How do I get the package checked in?  Nothing I seem to do is working.  Any help would be greatly appreciated.

Thanks,

-SP

PS I'm running EA 4.0 Build 771.

2
General Board / Re: Version Control
« on: February 26, 2004, 05:22:06 am »
You may also want to look at some products from SourceGear.  They provide two products, SourceOffSite and SourceGear Vault.  Both of these products have full support for the VSS interface.  

SourceOffSite is a server based tool that interfaces with an existing VSS repository.  It speeds access to the repository specifically for remote development.  But I have also found it to be a much faster interface than accesing the repository directly.

SourceGear Vault will import your VSS Repository and store it in SQL Server.  It provides a Web Services Interface that is accessed with a VSS compatible interface on the workstation.  It is also much faster than VSS and it eliminates the file share repository requirements.  It will also import existing VSS repositories, including all history.

VSS is also included as part of Visual Studio .NET 2003.

-SP

3
General Board / Re: .Net Framework Class Libraries
« on: February 26, 2004, 05:55:23 am »
I tried using this tool on System.dll and received an 'Ambiguous Reference' error.  What am I doing wrong?

-SP

4
General Board / Re: Code Templates: Making Changes
« on: February 26, 2004, 05:39:35 am »
Is there a complete reference, or White Paper, on modifying and using the Code Templates?

-SP

5
General Board / Re: Configuration Management Tool
« on: February 26, 2004, 04:56:59 am »
You may also want to look at some products from SourceGear.  They provide two products, SourceOffSite and SourceGear Vault.  Both of these products have full support for the VSS interface.  

SourceOffSite is a server based tool that interfaces with an existing VSS repository.  It speeds access to the repository specifically for remote development.  But I have also found it to be a much faster interface than accesing the repository directly.

SourceGear Vault will import your VSS Repository and store it in SQL Server.  It provides a Web Services Interface that is accessed with a VSS compatible interface on the workstation.  It is also much faster than VSS and it eliminates the file share repository requirements.  It will also import existing VSS repositories, including all history.

VSS is also included as part of Visual Studio .NET 2003.

-SP

Pages: [1]