vault not checking in "designer" created files

[bluebsh]

I have Vault 4.1.4 (we cant upgrade to 5 until next year due to budget issues) but my Visual Studio 2008 solution (VS 2008 SP1) when I check in the 40 projects under it, for some reason files which have .designer.vb behind them dont always check in or check in at all... I have problems with the Resources.resx's designer file not even checking into vault at all... so resources.designer.vb if I go into the source tree isn't even there, but resources.resx is (the related file) so if I go to a brand new machine and get the source code from vault, VB.Net complains Resources.designer.vb is missing... this only happens on a few projects, not all, some check in fine... but the oens that dont work, the resources.resx has a lock next to it, the resources.designer.vb has no icon at all beside it for source control... any idea what is going on? this is a pain in the butt having to recreate these files...... thanks!

[lbauer]

Are you using the Enhanced Client or the Classic integration client?

Do other users have the same problem with these projects?

[bluebsh]

the enhanced client

[bluebsh]

and yes, all users have this same problem on multiple workstations all running vault 4.1.4 and VS 2008 Pro SP1

[lbauer]

For some reason these file aren't in source control. You can add them with the Vault GUI Client. The easiest way is to turn on ghosting in the Vault Client. This setting is in the Vault Client under Tools->Options->General->Show non-version-controlled files ghosted in the file list.

Then you should see the designer files in your working folder greyed out or "ghosted". Right-click and select Add. Now when you load your project, do you see the designer files as being under source control?

[bluebsh]

That appears to of fixed it, after manually adding them they now have locks on the files in visual studio like they should!

[lbauer]

Thanks for the update. That's good news. : )

Let me know if we can be of assistance in the future.