Ever since I put my project in to Visual Source Safe, the revision and build numbers never change. Another side effect is that when I launch Visual Studio, it say sI haven't worked on the project for a long time even though I am in it daily.
Please help!
Jim
Revision and Build not changing in VB.NET project since Source Safe
Hot Topic
- Constructing a dynamic query with the 'OR' operator
- ==> I need help. Add-in 101 <==
- VS2005 Pro Install problem
- VS2005 Install Launches Whenever I Run VB6, MSProject or Visio
- Access 2003 Stand-Alone and Win 2003 Server Certificate Services.
- i want help in creating crystal reports from scratch
- Excel COM addin parameter limit?
- VSTO and ReportViewer
- grid width
- How can I catch "Add a breakpoint" event?
Visual Studio
- MouseGesture Working correctly?
- Help deployment Microsoft.VisualStudio.Tools.Applications.Runtime error '8004040a'
- problem with SS utility
- Webcam preview in an Avalon app
- Source code control
- Source code control
- usage of the VSSItem.get_Version() method
- SQL Server Express that includes a limited edition of Report Server?
- Remove MFC help as default F1-match
- Using SDk with VS2003
Revision and Build not changing in VB.NET project since Source Safe
sawer
I checked and neither the SUO nor the .user file is under SCC. I didn't realize that the revision number only incremented each day. I am used to vb6 where it got incrememted every time you compiles the .exe. In other words, it may be working and I just didn't know it. i will take notice as to whether it changes each day.
Jim
Vivek.V
Sorry, I'm not familiar with the assemblies versions.
Can you explain me when these versions change Also, do you know where VS persists them between the changes
In msdn help I see that "The default build number increments daily. The default revision number is random.". I changed the computer date and rebuild, but nothing changed (with the project uncontrolled). So, it's probably something else.
Until now, I can see 2 possible situations:
- VS stores the build/revision in a file that is supposed not to be under source control (the suo or vbproj.user perhaps ), but you added that file to VSS by mistake and now it's readonly on disk, preventing VS to change the numbers
- VS stores the build/revision in a controllable file (vbproj ). In this case it's a bug in VB that when the build/revision is supposed to change they don't call scci to checkout the file storing the build/revision.
Thanks,
Alin
isiran
In my assembly info I have a
<
Assembly: AssemblyVersion("1.1.*")>This should cause the Revision Number and Build Number to increment.
I have a form to show the version info.
lblVersion.Text = "Version: " & Application.ProductVersion
This always shows the same version. It worked before I put in under Source Control in VSS.
Jim
tkh
How did you put the project into VSS Have you used AddToSourceControl commands
> the revision and build numbers never change
What exactly are you doing to change these build numbers What is the expected results and what is actually happening
Thanks,
Alin