Pierre,

Thank you for your interest in VisualSVN!

>How to tag a version with Visual Studio and VisualSVN ?
>>> We would like to keep a copy of the whole solution that is released on the 
>>> production server.

Please use VisualSVN->Branch command in the Visual Studio main menu.

Please also consider Subversion documentation "Tags":
http://svnbook.red-bean.com/en/1.5/svn.branchmerge.tags.html.

>How to add into VisualSVN the published version ?
>>> We would like to use VisualSVN to keep the source and the compiled version. 
>>> The compiled version is the result of the publish of the web
application in Visual Studio.

Please consider our Knowledge Base article  "Web Development with
VisualSVN": http://www.visualsvn.com/support/topic/00002/.

>How to update the production server files from the published version in 
>VisualSVN ?
>>> After having published the solution, and updated the SVN version, we would 
>>> like to get the solution from SVN and update the files of the production 
>>> server.

It could depends on type of your production server.  Please could you
provide more details and clarify your question.  Also please consider
the post-commit hooks.

Thank you!
On Tue, Jan 20, 2009 at 12:29 PM,  <pierroto...@gmail.com> wrote:
>
> Hello,
>
> In order to replace our current source control solution (currently CVS
> and PushOK CVS plugin), I have several questions on the use of
> VisualSVN (we work on web application with Visual Studio 2008) :
>
> How to tag a version with Visual Studio and VisualSVN ?
>>>> We would like to keep a copy of the whole solution that is released on the 
>>>> production server.
>
> How to add into VisualSVN the published version ?
>>>> We would like to use VisualSVN to keep the source and the compiled version.
> The compiled version is the result of the publish of the web
> application in Visual Studio.
>
> How to update the production server files from the published version
> in VisualSVN ?
>>>> After having published the solution, and updated the SVN version, we would 
>>>> like to get the solution from SVN and update the files of the production 
>>>> server.
>
> Thanks a lot,
>
> Pierre.
>
>



-- 
Olga Dolidze
VisualSVN Support

Reply via email to