[±Þ] ¹ø¿ª Á» ÇØÁÖ¼¼¿ä..

VS 2005 ÇÁ·ÎÁ§Æ®¸¦ VSS 6.0 ·Î °ü¸® °¡´ÉÇÑÁö¿¡ ´ëÇÑ Áú¹®ÀÇ ´äº¯µé ÀÔ´Ï´Ù.

Á¦°¡ ¿ö³«¿¡ ¿µ¾î°¡ ¾ÈµÇ¼­¿ä..
Çؼ® Á» ºÎŹ µå¸³´Ï´Ù.

When using VSS 6.0 with VS2005:
- to get new files added in database to web projects you will need to select the web node in SolutionExplorer and do GetLatestVersion; The Get... dialog may not list all the new files in database
- you will not see Renames and Deletes in the Get... dialog nor you'll be able to synchronize them from database to the enlistment (the experience will be similar with using VSS 6.0 with VS2003)
- the projects will not open from source control assynchronously (same as in VS2003)
- if using Utf8 files containing non-English characters you may need to set the file types in VSS Explorer to binary to avoid content corruption (same as in VS2003)
(and there are a couple more minor differences)

-----------------------

Yes, it will work with a similar feature set as VS2003 & VSS.
New features introduced to the SourceSafe 2005 Plug-In for Visual Studio will not work. For instance, to name a few:
• Asynchronous opening of projects
• Remote access over http
• Delete/rename propagation
• Integration on the Open Project dialog


-----------------------
Actually, remote and delete propagation will work, but only from client -> database. Synchronizing deletes/renames using Get dialog will not work (propagation database -> client) as it requires new functionality in the provider.

Another thing that will only work halfway is getting new files added in the database for web projects. VSS 6.0 has no capabilities of enumerating new folders in the database through MSSCCI functions used by VisualStudio; synchronizing new file additions will only work in folders that already exist on the local disk.


²Ù¹÷...

¤Ì¤Ì