I have a strange issue occuring. When I check VS .NET Web application C# files from vault, sometimes, the InitializeComponent() contents get erased during checkin. I have not seen this issue reported. I am running the latest client. Is this a known issue? What is the resolution? We have been losing work.
Jeff
InitializeComponent() Contents Get Erased On Checkin
Moderator: SourceGear
Not sure I follow - are you saying the file reverts to a previous version after it is checked in? after it is checked out? That it doesn't get checked in with the right contents?
Check the file history (from the Vault GUI client), where you can see the differences that were checked in for each version.
You might check the status of the file in the Vault GUI client before checking it in (until we find out what is happening). If the status is something other than Edited, that might indicate a problem.
Check the file history (from the Vault GUI client), where you can see the differences that were checked in for each version.
You might check the status of the file in the Vault GUI client before checking it in (until we find out what is happening). If the status is something other than Edited, that might indicate a problem.
-
blueston
Further Details
To clarify the issue: we use the standard InitializeComponent() function in the .aspx code-behind file, to initialize things like event handlers.
The contents of this function are fine when the page code-behind is retrieved from Vault. But after checkin we will notice that immediately after checkin the function is there but its contents have been erased.
This is occurring for several people using different machines in different offices, though for some of us it does not occur at all. Possibly this is a VS.NET 2003 issue, or a compatibility issue with Vault. I'm not sure. Currently, we have to manually inspect .aspx.cs pages every time we check them in to make sure everything is OK. A general search on Google did not turn up any information on this issue.
The contents of this function are fine when the page code-behind is retrieved from Vault. But after checkin we will notice that immediately after checkin the function is there but its contents have been erased.
This is occurring for several people using different machines in different offices, though for some of us it does not occur at all. Possibly this is a VS.NET 2003 issue, or a compatibility issue with Vault. I'm not sure. Currently, we have to manually inspect .aspx.cs pages every time we check them in to make sure everything is OK. A general search on Google did not turn up any information on this issue.
What version of Vault are you on?
I guess the main question is: When you do a checkin, does the repository version increment and did the changes make it into the repository? (you can check this via the Vault GUI client, and do a Show History on the file).
If it looks like instead of checking in the file it undoes the checkout (and puts a copy in an _sgbak folder), it might be a problem that was fixed in Vault 3.0.6.
I guess the main question is: When you do a checkin, does the repository version increment and did the changes make it into the repository? (you can check this via the Vault GUI client, and do a Show History on the file).
If it looks like instead of checking in the file it undoes the checkout (and puts a copy in an _sgbak folder), it might be a problem that was fixed in Vault 3.0.6.