Designer forcing Check out

Hello-

We have seen this in the past. If it is asking you to check out the file that means that it is editing it in some small way. It's likely that if you just say yes to the check out and then immediately check in again the next time you view designer you will not be prompted for checkout.

Here's a few posts from people with similar questions:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=275345&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=487499&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=423791&SiteID=1

-Luke

LukeWestendorfMSFT at 2007-10-2 >

There is really nothing scci can do against a badly written editor that requests write access to files even when it's not really necessary...

As a customer, you can either report the bug at http://lab.msdn.microsoft.com/productfeedback/ against the editor (and attach some files reproducing the problem) then wait for the fix to appear in next ServicePack or in next VS version, or you can call product support and convince the designer team to release a QFE.

From scci point of view, here are some tips that might make your life easier:

- instead of CheckingIn the files you can UndoCheckout them

- in SourceSafe, a checkin of unchanged files can be automatically translated to an UndoCheckout (this is a default per-user setting), and can be set in SourceSafeExplorer in Tools/Options/General/CheckinUnchangedFiles

- in VS side you can set in Tools/Options/SourceControl/Environment, OnEdit...PromptForCheckOut, and AllowCheckedInItemsToBeEdited. Then, when you open the file and the designer wants to check it out you'll be presented with a CheckOutOnEdit dialog where you can choose "Edit in memory". When closing the editor/designer you may be prompted to save the changes, and can choose not to save if you know you never made real changes to that file.

Alin

AlinConstantin-MSFT at 2007-10-2 >