VisualSVN 1.7注册版下载

VisualSVN 是Visual Studio下的一个插件，是VisualSVN Server的客户端工具，需要配合TortoiseSVN 使用。

因其是收费插件，所以在网上搜了个注册机，特内部发布（只在RSS里显示，以后一些内部存档的东东将采取这种方式进行发布）。

 

当前最新版本为 1.7.3 。下载地址为： VisualSVN-1.7.3

 

注册机下载地址为：https://files.cnblogs.com/lzhdim/Crack.rar

 

下面翻译于VisualSVN的Documentation 

Now you choose the directory where your code will be stored. VisualSVN can add your code to a new or an existing repository. When VisualSVN creates new repository it creates the default repository structure with branches, tags and trunk folders. Initially your code will be stored in the trunk folder.

 

After this operation is finished all source files and folders in your solution will be marked as added to Subversion. Added files will be indicated by yellow icons in Solution Explorer. But all changes are still local and have not been sent to the target repository yet. This allows you to review the results of adding your solution to Subversion before the operation is finished.

To commit your solution to Subversion, select VisualSVN | Commit menu item, enter a comment and click OK. The first versions of your source files will be sent to the target Subversion repository.

After you committed your solution to Subversion you should see green icons in Solutions Explorer indicating that your code is controlled by Subversion and you have no local changes. You are ready to work!

 

While updating you'll see TortoiseSVN's Update window that will show you which files of your solution are need to be updated.

 

You can see an overview of the changes you've made by using TortoiseSVN's Show Changes window. To open the window choose the VisualSVN | Show Changes command on the main menu.

Please note that you can examine your changes without network access. This makes it easy to manage your changes-in-progress even when you are somewhere without a network connection.

 

Subversion reverts the file to its pre-modified state by overwriting it with the cached “pristine” copy from the .svn area. You can also undo any directory modifications. For example, you might decide that you don't want to rename a file after all.

For further details about resolving conflicts please consult the chapter called Resolve Conflicts (Merging Other's Changes) in the Version Control with Subversion book.

 

Please choose the VisualSVN | Commit main menu command to send all of your changes to the repository. When you commit a change, you need to supply a “log message”, describing your change. Your log message will be attached to the new revision you create.

At this point, you need to update your working copy, deal with any merges or conflicts that result, and attempt your commit again.