This question appears to be the same as described in this recently created issue:
This issue keeps surfacing from time to time, so I need to clarify it - what's going on and how much trouble this is. I had an impression that this is not a big deal - when you try to open the solution with bindings, VS shows you message box - smth like
"Cannot connect to TFS, bla-bla", you click Ok, and then solution opens without source control, and you can run and play with it without any problems. For me it happens when I am not connected to Internet, it happens only once, and
next time I reopen it VS does not ask any more. I thought this is not a big deal (to click Ok on message box), it was expected behavior according to Codeplex documentation, so I never worried about this.
Now it appears a different story emerges, from your post and some previous ones. It looks like to open the solution you have to go through some manual process of removing bindings (deleting vss files?), otherwise you can't open/see anything. Is this the
case? Then we need to have a second look at it. I don't mind doing it myself for release download, so you guys don't have to do it.
My question to everybody, especially those running "smaller" versions of visual studio:
What is your experience with opening the project? Is it more than simply clicking a button on warning box?
What seems strange for me with your situation - I also have VS Professional, so your version is not "smaller" than mine; then why you have this trouble at all?
Let's work it out, identify the procedure for removing bindings for release version, and I'll follow the process each time I upload the release.
There was an earlier discussion with comments on how to remove the bindings, need to look at it one more time Again, I was under impression at the time that this wasn't a big deal.
Apologies to everyone if this is not the case. This is similar to the issue with unit testing framework. At the beginning I used nUnit, but then decided to move to VS built-in unit testing. I thought that would simplify things for everybody,
but it turned out, VS unit testing framework was not available in smaller versions of VS. So I'm planning to move it back to nUnit in some near future - I want to also refactor unit tests a bit at the same time, so it has to wait for its turn.