Hi, When I compile the program in VISUAL BASIC, then it generates a version for example 2.0, how can I integrate that version with the Version that Source Safe generates.
I mean If I have the version 2.0 in Visual Basic, I want to have the same version 2.0. in Visual Source Safe.
Because In Visual Source Safe generates like version 1.0, so it creates inconsistency.
Thanks in andvanced
Help: The relantioship Version between VSS & Visual Basic
Hot Topic
- Visual SourceSafe 2005 Database Format
- How to work with Framework 1.0 in Studio 2003
- Treeview becomes non-selectable when a data template is used??
- Integrating help without the Help Integration Wizard - Urgent
- SourceSafe Setup problem
- first Print doesn't work
- Type vbproj not supported by Visual Studio 2005???
- Using an VSS 2005 database with VSS 6.0d
- how to inject files into a target?
- Customizing NavigationWindow and using Property Aliasing
Visual Studio
- intel compiler in visual studio 2005
- 2 Patterns for single Crystal Report (rpt) file
- VSS Extremely slow from one computer
- No items in the toolbox
- How to config Proxy generation?
- Team Suite Beta 2 error "Package Load Failure"
- Adding files generated with text template to project and dynamically create a web application
- Help with Infopath!!!
- How to support INSERT SNIPPET?
- Where's the Help Integration Kit 2005
Help: The relantioship Version between VSS & Visual Basic
baoqs
Lets say your VB program is made up of Form1.frm and Form2.frm. You change your program in a way that affects Form1.frm but doesn't affect Form2.frm. The file Form1.frm will be checked out of SourceSafe and, when you check it back in again, the version of Form1.frm will be increased. The file Form2.frm hasn't been changed so version of Form2.frm won't have changed either.
Typically, what people do is use a Visual SourceSafe Label to identify the collection of file versions that were used to generate a specific version of a program. For example you might use "MyProgram 2.0" as the label to identify the files that were used to generate version 2.0 of your program. That label might be applied to version 17 of Form1.frm and version 99 of Form2.frm.
Then sometime later you might apply "MyProgram 2.5" to Form1.frm version 42 Form2.frm version 99 and Form3.frm version 5 (assuming Form3.frm was added to your project).
How exactly you go about applying these labels and coordinating them with your VB program's version depends a lot in your exact build process - MSBuild versus Ant or Nant versus make files versus hand building the program etc.
It also depends on whether you choose to build first or label first. Some people have a build process that does a "Get latest Version" from SourceSafe, builds whatever has just been retrieved, and then labels the current version of all the files with some suitable string (version related) when the build completes.
Other people prefer to label the project first and then have a build process that performs a Get of the files identified by the label rather than "latest version".