Visual Studio 2005 problem

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
jimmurray
Posts: 24
Joined: Fri Jan 11, 2008 7:24 am

Visual Studio 2005 problem

Post by jimmurray » Wed May 21, 2008 12:41 am

Got a problem using Vault (4.1.1.18060) which didn't happen on the pre 4.1 release. Having big problems when checking in a project for which a new datasource ('.datasource' type file). When doing this the VS client hangs requiring VS needing to be ended via task manager. When I go to the Vault client and try and check in the changes I get an error saying the .csproj 'needs merge' ??? - i'm the only one that has changed this project and only by adding a datasource! I select 'resolve merge status' to get round this and try the checkin again. I then get an error telling me the datasource alreadfy exists, then an error telling me the .resx file already exists etc. In order to resolve the problems I need to take a copy of the local files, delete them from within vault and then put them back in the local folder and then cehck them in. As you can imagine this is a total pain!

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed May 21, 2008 8:14 am

Are you using the Enhanced or Classic client in Visual Studio?

What type of project are you adding this datasource to?

jimmurray
Posts: 24
Joined: Fri Jan 11, 2008 7:24 am

Post by jimmurray » Wed May 21, 2008 9:29 am

Enhanced client, project is a 'class' project that will create a dll containig a number of windows forms. Each of these forms contains a grid with a .datasource object as their 'datasource'. This 'datasource' is a business objct that comes from another project/dll that is in the solution i.e. it is not a linkg to a database. Example:

<?xml version="1.0" encoding="utf-8"?>
<!--
This file is automatically generated by Visual Studio .Net. It is
used to store generic object data source configuration information.
Renaming the file extension or editing the content of this file may
cause the file to be unrecognizable by the program.
-->
<GenericObjectDataSource DisplayName="RunItem" Version="1.0" xmlns="urn:schemas-microsoft-com:xml-msdatasource">
<TypeInfo>MES.Data.RunItem, MES.Data, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null</TypeInfo>
</GenericObjectDataSource>

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Wed May 21, 2008 9:41 am

Hi Jim. I'm sorry for the difficulties this issue has caused you.

We've fixed an issue very similar to this for the upcoming 4.1.2 release. We haven't yet announced a release date for 4.1.2, but I can offer you a pre-release build. Email me at ian at sourcegear dot com if you'd like to try that.
Ian Olsen
SourceGear

jimmurray
Posts: 24
Joined: Fri Jan 11, 2008 7:24 am

Post by jimmurray » Thu May 22, 2008 2:18 am

Hi Ian,

Did you get my email?

Jim

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Thu May 22, 2008 8:05 am

I did. Did you not get my response? I sent it yesterday at 11:15 (GMT-5).

I'll send it again now.
Ian Olsen
SourceGear

Post Reply