HI,
When you work with sourcesafe in the folders of your solution
sourcesafe generate some files that have the binding information. If
you eliminate those files you got that message.
If you don't wan't to work with sourcecontrol you must go in the IDE
menu at File --> SourceControl -->Change Source Control and choose the
unbind button. This action will remove all the binding files of your
project.
If this workaround doesn't work, you must delete the files with
extensions .vssscc , mssccprj.scc , vssver.scc of your folders in your
solution also you must open your .sln, .etp , .csproj files as plain
text and delete all entries starting with SCC* , by example :
SccProjectName = "SAK"
SccLocalPath = "SAK"
SccAuxPath = "SAK"
SccProvider = "SAK"
SccProjectFilePathRelativizedFromConnection56 =
Negocio\\Servicios\\Seguridad\\Seguridad.Acciones\\
SccProjectUniqueName57 =
Negocio\\Servicios\\Seguridad\\Seguridad.Mensajes\\Seguridad.Mensajes.csproj
SccProjectTopLevelParentUniqueName57 = Negocio\\Negocio.etp
SccLocalPath57 = .
CanCheckoutShared = false
SccProjectFilePathRelativizedFromConnection57 =
Negocio\\Servicios\\Seguridad\\Seguridad.Mensajes\\
This workaround will solve your problem.
Regards,
Oscar Espinosa
z f - 07 Sep 2005 12:50 GMT
it worked,
interestng to point that after deleting the first scc 4 entries (the only
ones), and re-binding the project to source-safe.
opening the .sln was successfull.
but the csproj after re-binding was the same as the csproj before.
> HI,
>
[quoted text clipped - 31 lines]
>
> Oscar Espinosa
Oscar_Uio - 08 Sep 2005 12:24 GMT
Yes, the csproj still the same. The sln file is the one that containing
all the binding information and paths for sourcafe.
The csproj files have sme binaries references to the sourcesafe
database
Oscar Espinosa