versioning

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

what is the best way for versioning your applications?
when becomes application 1.1.0.1 application 2.0.0.0 or something?

(also working with database)
 
The version is: major, minor, build, revision

You change the major version when you add significant features to your
application.

You change the minor version when you add few features or enhancements to
your application not to justify a change of major version.

You change the revision for bug fixes, etc.

You change the build for each build, even if not released to the public.

Notice also that you have AssemblyVersion and AssemblyFileVersion
attributes, with different meanings.

--

Carlos J. Quintero

MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com
 
What are you aiming for.

Numbering? Change the major and possibly minor build numbers in
assemblyinfo.cs.

Source Control? Pin the version whenever you release.


---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
But when a change in software causes a change in the database. How do you
keep them running... (Software1 belongs to database1, software2 belongs to
database2)
 
Normally is on the contrary: a change in the business model causes a change
in the database data model which in turn implies a change in the
application, but anyway databases are not versioned as applications. With
each breaking change, you just need to supply the correct new database file
with your executable and somehow import the data from the old database. If
your database is filed-based (such as Access), you can tie a database file
to a software release using a Source Code Control (SCC) system such as
SourceSafe and use a SCC feature called "Labels".

Not sure if this answers your question...

--

Carlos J. Quintero

MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com
 
During development, you keep the old and the new database and your source
code must use different connect strings.

During deployment, the setup of the new software should update the data
model of the current user database, preserving the data.

--

Carlos J. Quintero

MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com
 
thanks for your reponse

what's the best way for keeping changes between these two databases and how
to apply this changes to the old databases?
(using a sql script or something?)
 
You can use a combination of :

- Documentation tools
- Change tracking tools
- Source code control tools to allow code versioning
- Conditional compilation if you want to avoid branching and have a single
source code but different exes for old and new database
- "If" statements in your code that detect the database version and use some
code or other to be compatible with both database formats using a single
exe.

To change the database format your setup will have to perform a "custom
action" (see the VS.NET setup projects help) and execute some SQL statements
to change tables, etc.

--

Carlos J. Quintero

MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com
 
Back
Top