Question to all - what problems do you have opening downloaded files?

Coordinator
Dec 23, 2009 at 5:11 PM
Edited Dec 23, 2009 at 8:32 PM

People keep reporting about troubles opening VS solution because of codeplex source control bindings.

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?

Do you have any other troubles? please let me know.

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.

Thank you

Roman

Developer
Dec 28, 2009 at 8:36 PM

My VS shows TFS login dialog, I click Cancel, and then everything goes fine. Not an issue, really.

>it happens only once, and next time I reopen it VS does not ask any more

In my case it happens every time I open Irony_All solution :)

Dec 29, 2009 at 7:32 PM

I'm running Visual C# 2008 Express Edition (on Vista if that matters) with the code drop from about a month ago (I need to update, I know!  Especially after you fixed the problem with priorities on FreeTextLiterals).  When I try to open the solution I get a message box that says:

"The source control provider associated with this solution could not be found.  The projects will be treated as not under source control.  Do you want to permanently remove the source control bindings from the projects?"

For which I hit "No" -- in case anyone else accessing our SVN can open it with the source control bindings.

Then I get another box that says:

"The project file 'C:\SVN\Irony\Irony.Tests\040.Irony.Tests.csproj' cannot be opened.  The project type is not supported by this installation."

I just hit "OK", and then I get a box:

"Solution folders are not supported in this version of the application.  Solution folder 'Solution Items' will be displayed as unavailable'.

Again, I hit "OK", which then displays:

"The project file 'C:\SVN\Irony\Irony\100.IronySilverlight.csproj' cannot be opened.  The project type is not supported by this installation."

So I hit "OK" yet again, and then everything loads fine from there for me to mess around with.

For me, it's much more of an annoyance than a problem.

Dec 30, 2009 at 3:05 PM

I'm remove all bindings manually.

I'm delete *.vspscc, *.vssscc files and in all .csproj files in Property/PropertyGroup element remove SccProjectName, SccLocalPath, SccAuxPath, SccProvider elements.

Coordinator
Jan 11, 2010 at 8:49 PM

fdddima - so why manually? The simpler scenario (saying OK to message box) - is it NOT working for you?

thanks

Roman 

Jan 12, 2010 at 6:43 AM

Yes, simpler scenario is NOT working for me.

My past experince for some years with MSVS and VSS say me "do it manually, if you know how". :)

MSVS 2008 is simply crashes on some projects, when can't access to source control database. With your project its happens too:

Something like:

 

---------------------------
Microsoft Visual Studio
---------------------------
Unexpected error encountered. It is recommended that you restart the application as soon as possible.
Error: Unspecified error
File: vsee\lib\vapifunctionwrapper\vapifunctionwrapper.cpp
Line number: 169
---------------------------
OK   Cancel   
---------------------------

Unexpected error encountered. It is recommended that you restart the application as soon as possible.

Error: Unspecified error

File: vsee\lib\vapifunctionwrapper\vapifunctionwrapper.cpp

Line number: 169

OK   Cancel   

Then they promt temporarily or permanent remove bindings - but in fact it's remove only for project "025.Irony.Samples.Console", other projects have "unavialable" state.

 

Also i think, what unbinded projects more simply merge with user's current repository (if theys have bindings).