Project Checks Out Unexpectedly When Opened

Question

All,

In Visual Studio 2008 with TFS 2008, a SSIS project will always prompt for checkout when opened.  No explicit changes have been made.  However, there are three differences when I compare the local and server versions of the .dtproj file.  Any idea why this is occuring. 

• Server Version

        <ProductVersion>10.0.4000.0</ProductVersion>

        <Name>HRD_ODS 71.database</Name>
        <FullPath>HRD_ODS 71.database</FullPath>

• Local Version

       <ProductVersion>10.0.2531.0</ProductVersion>
       <Name>HRD_ODS 6.database</Name>
       <FullPath>HRD_ODS 6.database</FullPath>

---

Orlanzo

Answer 1

Seems your local version does not commit to server side, so the project always show as checkout.

However, I move it to TFS Version Control forum, since this forum is for VSS tool only, thanks.

---

Bob Bao [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Hi Orlanzo, 

Thanks for your post.

First, I suggest you upgrade your VS 2008 and TFS 2008 both to VS 2008 SP1 and TFS 2008 SP1. 

This issue only happened on this one SSIS project? And try to open this one SSIS project on other clients, still occur the same issue?

Try to perform check in on your SSIS project, if there’s changes can be checked in, please select to check in local changes or undo the local change to ensure there’s no change between TFS Server and your local for this SSIS project. Then reopen it again. 

If you have any further research of this issue, please share your experience here.  

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 3

Hi John,

Thanks for your help.  I was able to resolve this problem.  After review, members of development team were working with various levels of the SQL Server 2008 client tools.  Some had Service Pack 1, others had SP-2, and a couple had 2008 R2.  Leveling everyone to the same version resolved the issue relating to the ProductVersion attribute.

The <Name> and <FullPath> attributes were/are a bit more of a puzzle.  There are multiple projects A, B, C, ... under one solution S(Main).  Someone created and checked in an addition solution file for project B - S(B).  Whenever someone opened the project it would create a new .database file locally for project B.  This triggers a checkout to modify the .dtproj file. 

I resolved this issue by deleting the extraneous solution S(B) and .suo files.  Finally, I edited the dtproj file to point to the correct .database file. 

Both steps resolved the issue I had.  It isn't entirely clear why additional .database files were created, but the problem hasn't reocurred.  I'd appreciate your thoughts on what may have caused the behavior.

In any event, I'm good to go and appreciate your willingness to help!

---

Orlanzo

Answer 4

Hi,

We are also experiencing this same issue (Visual Studio 2010, SSIS 2012 with SSDT and TFS).

-- even when none of my colleagues does any changes

• I check-out a .dtsx package file and edit
• When I attempt to check-in some files (usually .dtsx package files), Visual Studio asks if I want to save the entire list of .dtproj and .sln files (from the entire solution) to disk
  • If I chose “No”: it’llnot continue the check-in
  • If I chose “Yes”: it’ll check-in the proper files BUTit’ll also check-out ALL the .sln and .dtproj files
    • It usually does two changes to each .dtproj file, the main one being thatit tries to point to a DIFFERENT .database file
• This a major hassle:
  1. We’d have to remember to ALWAYS use [Undo Pending changes] on these false check-outs
     • Or else, nobody else from the team can check-in anything into the solution
  2. èThis reduces us to a “one-person-at-a-time” scenario for check-ins which istoo restrictive
• The above behavior indicates that, for some reason, each SSIS project modifies the.dtproj file in memory
  • I do not understand that part clearly

Best regards,

Radu Popa