Agent SVN with Visual Studio 6

hadassi · Post by **hadassi** » Sun Apr 19, 2009 7:45 am

The home page states:
"Tested with Microsoft Visual C++ 6.0"
http://www.zeusedit.com/agent/index.html

But I could not get visual studio 6 to work with Agent SVN.
Any help would be appreciated.

Thanks

Post by **jussij** » Mon Apr 20, 2009 12:11 am

But I could not get visual studio 6 to work with Agent SVN. Any help would be appreciated.

EDIT: For details on how to setup Microsoft Visual C++ 6.0 to work with VisualSVN using Agent SVN refer to the last message post in this link: http://www.zeusedit.com/zforum/viewtopic.php?t=7113

The same sort of configuration steps as described above would also be required when running Microsoft Visual C++ 6.0 against the stock standard Subversion server.

EDIT: The Agent SVN installer now handles the creation of the required registry keys. There is also a tutorial of how to configure Agent SVN to work with Visual C++ 6.0 in the Agent SVN help file.

Original Thread
The issue is the Agent SVN installer does not set the ProviderRegKey key and this is why you are not seeing it from inside of the Microsoft Visual C++ IDE

The installer will be fixed

In any case here are some instructions on how to make it all work:

Initial configuration

Step1: Start regedit and find this key: HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider
Step2: Modify the ProviderRegKey string value to be this: SOFTWARE\Xidicone\Agent SVN
Step3: Start Microsoft Visual C++ IDE
Step4: To check the registry key is set correctly use the MSVC++ Project, Source Control menu and at the bottom there should be an Agent SVN menu item.
Step5: Select the Agent SVN menu to bring up the Agent SVN Configuration dialog and set the details to suit (see help for details)

How to Add a Project to the Source Control

Step1: Open a project workspace and lets assume it's called c:\Projects\MyProject
Step2: Select the project from the File View of the workspace panel
Step3: Use the Project, Source Control, Add to Source control menu to bring up the import wizard for this project
Step3: Complete the wizard to import the project to the source control (refer to help for details)
Step4: Close the Microsoft Visual C++ IDE
Step5: Locate and rename the c:\Projects\MyProject project folder to be c:\Projects\MyProject.original
Step6: Locate the c:\Projects\MyProject.new-working-copy folder and rename it to be c:\Projects\MyProject
Step7: Restart Microsoft Visual C++ IDE and open the c:\Projects\MyProject project

The project is now in source control and the Project, Source Control menu will allow you to access and manage the files in the source control.

Cheers Jussi

hadassi · Post by **hadassi** » Mon Apr 20, 2009 6:55 am

OK - Thanks. I can now see the AgentSVN menu.

My problem now is the following:

We are moving from Visual-Source-Safe to SVN. I already created a repository and imported all of the files. Now, I guess I should edit the project (dsp and dsw) files to eliminate the links to VSS. After I do that, how should I proceed in order to make AgentSVN connect to the correct repository? ( I already tried doing so, but could not get agent SVN to work)

Thanks again

Post by **jussij** » Mon Apr 20, 2009 7:53 am

Now, I guess I should edit the project (dsp and dsw) files to eliminate the links to VSS.

Unfortunately Microsoft Visual C++ 6.0 doesn't have an easy way to rebind the source control target, so I think the only option is to edit the dsp file.

After I do that, how should I proceed in order to make AgentSVN connect to the correct repository?

The first thing you have to do is tell Agent SVN where the repository is located. You do this using Step 5 of the Initial configuration shown above (see the Agent SVN help for details).

Next in the dsp file for the project there should be these lines:

Code: Select all

# Begin Project
# PROP AllowPerConfigDependencies 0
# PROP Scc_ProjName "MyProject"
# PROP Scc_LocalPath "."

The Scc_ProjName should just be the name of your project as named in the repository (note this name is case sensitive). To help I would suggest using the repo browser from TortoiseSVN to get the names of the projects in the repository.

The Scc_LocalPath is the local path and it should be the same as the folder as dsp file (hence the period).

Also if you bring up regedit and find this debug option:

Code: Select all

HKEY_CURRENT_USER\Software\Xidicone\Agent SVN\HelpDebug

If you set this to 1 it Agent SVN will create a log file in the Agent SVN installation folder.

The output in the log file should look something like this:

Code: Select all

===================================================================
       Agent SVN, Version 1.00
       Xidicone P/L  Copyright (c)  2004-2009
       All rights reserved
       http:\www.zeusedit.com
===================================================================
-------------------------------------------------------------------
   Project Details
-------------------------------------------------------------------
          Command: svn.exe
             User: jussij
          Project: MyProject
          AuxPath: file:///D:/Projects/svnroot
  Local Directory: d:\projects\myproject
  Default AuxPath: file:///D:/Projects/svnroot
      Return Code: 0
-------------------------------------------------------------------

In the details above the AuxPath is the location of my repository as set in the Agent SVN configuration dialog and Project is the name of the project in the repository.

This should hopefully help get the connection details setup correctly.

But if you can't, just post some of the connection details from the log file and a listing of the repository project you are trying to connect to and I will try to get you up and running

Cheers Jussi

Post by **jussij** » Tue Apr 21, 2009 11:35 pm

Here is some more information about binding a project in Visual C++.

How to Manually Bind to the Project

Unfortunately there is no easy way to change the bindings from within the IDE like there is in Visual Studio so the only other option is to manually bind the project files.

Assuming the Visual C++ project is called MyProject this is how to bind the project to the Subversion repository:

1: Make a backup copy of the MyProject.dsw and MyProject.dsp files.

2: Make sure the Agent SVN has been configured with the correct location of the Subversion repository for example:

Code: Select all

file:///D:/Projects/svnroot

3: Make sure the MyProject project exists in the Subversion repository for example at this URL:

Code: Select all

file:///D:/Projects/svnroot/MyProject/trunk

4: Open the MyProject.dsw file and make sure the the following lines exist:

Code: Select all

Project: "MyProject"=.\MyProject.dsp - Package Owner=<4>

Package=<5>
{{{
    begin source code control
    MyProject
    .
    end source code control
}}}

5: Open the MyProject.dsp and make sure the following lines exist:
To bind the project:

Code: Select all

# Begin Project
# PROP AllowPerConfigDependencies 0
# PROP Scc_ProjName "MyProject"
# PROP Scc_LocalPath "."

6: Open the MyProject.dsw in Visual C++ and the following output should be displayed in the Source Control output window:

Code: Select all

-------------------------------------------------------------------
   Project Details
-------------------------------------------------------------------
          Command: svn.exe
             User: jussij
          Project: MyProject
          AuxPath: file:///D:/Projects/svnroot
  Local Directory: d:\projects\myproject
  Default AuxPath: file:///D:/Projects/svnroot
      Return Code: 0

NOTE: To unbind the MyProject completely the lines in the MyProject.dsw file become:

Code: Select all

Project: "MyProject"=.\MyProject.dsp - Package Owner=<4>

Package=<5>
{{{
    begin source code control
    end source code control
}}}

and in the MyProject.dsp file the lines become:

Code: Select all

# Begin Project
# PROP AllowPerConfigDependencies 0
# PROP Scc_ProjName ""
# PROP Scc_LocalPath ""

Post by **jussij** » Tue Jun 30, 2009 7:25 am

Initial configuration

Step1: Start regedit and find this key: HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider
Step2: Modify the ProviderRegKey string value to be this: SOFTWARE\Xidicone\Agent SVN.....

The latest release of Agent SVN now creates these registry keys during the installation process: http://zeusedit.com/agent/index.html

More information has also been added to the help file to cover the project import process.

Cheers Jussi

hadassi · Post by **hadassi** » Mon Jul 13, 2009 9:51 am

I just got back to setting-up the integration.
I have a project tree that looks something like:
Root
A
B
C (the project file is here)
D

I changed the .dsp and .dsw files as ordered (although I was not sure about the actual project directory. Should it be "Root" or "Root\C"?)

I still get error messages:

https://yyyy:8443/svn/ImPr/$/aaa/bbb/C,%20WTAAAAAA: (Not a valid URL)

----------------------------------------------------------------------Agent SVN, Version 1.00

----------------------------------------------------------------------
https://yyyy:8443/svn/ImPr/$/aaa/bbb/C,%20WTAAAAAA: (Not a valid URL)----------------------------------------------------------------------Agent SVN, Version 1.00

----------------------------------------------------------------------

I did not see any log file in the installation directory

Thanks again

hadassi · Post by **hadassi** » Mon Jul 13, 2009 11:10 am

OK. After deleting *.opt and *.ncb, I managed to get a little further.
My current problem is that I get a message

Could not connect to source code control project "aaaa".

Could it be due a problem with my evaluation license?
How do I fix that?

hadassi · Post by **hadassi** » Mon Jul 13, 2009 11:24 am

How o I change AgentSVN's configuration (after setting it up the first time)?
Selecting:
Project->Source Control->Agent SVN,
just brings up the tortoiseSVN repo-browser

hadassi · Post by **hadassi** » Mon Jul 13, 2009 12:00 pm

OK. I changed the
HKEY_LOCAL_MACHINE\SOFTWARE\Xidicone\Agent SVN\ActivateExec
key to "", and got the configuration dialog back.

Now things seems to be working. Two new questions:
1. Is there a way to replace the diff and history dialog boxes to use another tool (such as TortoiseSVN)?
2. Why do I get a whole buch of

Command: svn.exe propget AgentSVN <filname>

lines on startup. This is really slow!

Post by **jussij** » Tue Jul 14, 2009 1:16 am

Agent SVN, Version 1.00

In the can see you are running an olded version of the plugin. I would suggest getting the latest Agent SVN 1.20 version found here:

http://www.zeusedit.com/agent/bin/asvn-v120.zip

This latest version has had a lot more information added to the help file to help with configuration and setup.

OK. I changed the
HKEY_LOCAL_MACHINE\SOFTWARE\Xidicone\Agent SVN\ActivateExec
key to "", and got the configuration dialog back.

That is a very good point. I will fix this by writing a simple application that brings up the configuration that can be run via the Start Button

Now things seems to be working. Two new questions:
1. Is there a way to replace the diff and history dialog boxes to use another tool (such as TortoiseSVN)?

I will see it this is possible

2. Why do I get a whole buch of
Quote:
Command: svn.exe propget AgentSVN <filname>
lines on startup. This is really slow!

I think the the debug option is turned on in the registry (as described earlier) and needs to be turned off.

With the debug option on the startup can be very slow

Cheers Jussi

Post by **jussij** » Mon Jan 10, 2011 1:28 am

Now things seems to be working. Two new questions:
1. Is there a way to replace the diff and history dialog boxes to use another tool (such as TortoiseSVN)?

The latest version now has an option to use an external difference tool.

The latest version can be found here: http://www.zeusedit.com/agent/bin/asvn-v140.zip

Cheers Jussi

Yanka · Post by **Yanka** » Mon Mar 12, 2012 2:11 pm

Anyone know how I can use Subversion SVN source control in combination with VS .NET 2005 to have source control for a website served on IIS with Frontpage extension 2002?

Post by **jussij** » Mon Mar 12, 2012 5:36 pm

The Agent SVN help file contains a tutorial on getting VS .NET 2005 to work with Subversion.

Also the Agent SVN implements the MS-SCCI interface so as long as your IDE implments this interface, in theory it should also work.

If your IDE does support this interface, the Agent SVN help file should contain enough information to make this work (i.e. most IDEs that support MS-SCCI are configured in a similar manner).

But if you have issues getting Agent SVN to work with your IDE feel free to send me an e-mail along with the Agent SVN log file.

With the help of the Agent SVN log file it should be possible to make any MS-SCCI IDE work with Agent SVN.

Cheers Jussi

Agent SVN with Visual Studio 6

Agent SVN with Visual Studio 6

How do I make Agent SVN recognize projects already in the SC