The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,676 other followers

Archive for August 23rd, 2012

iOS, Delphi XE3 and XE2

Posted by jpluimers on 2012/08/23

I hope I read these mobile and iOS parts of the XE3 and beyond : A look at mobile¬†post by John Ray “JT” Thomas¬†correctly: Read the rest of this entry »

Posted in Delphi, Delphi XE2, Delphi XE3, Development, Software Development | 7 Comments »

Is VMware Workstation 9.0.0 out, or is their auto-update system in an identity crisis?

Posted by jpluimers on 2012/08/23

This morning, when starting VMware Workstation 8.0.4, it indicated that 9.0.0 was available.

No news on the VMware website (it still shows adverts for Workstation 8), nor on Wikipedia VMware Workstation page so is their auto-update system in an identity crisis or what?

Two links on VMware Workstation 9.0.0 Build 812388, but not sure if nsane is a good source of information. On the other hand, there is also news on the Bulgarian Kaldata about VMware Player 5.0.0 Build 812388.

Since VMware Player and Workstation share build numbers, and there has been a VMware Workstation Technology Preview 2012 for about 6 months, something could be in the midst of release in time zones where it is not yet 20120823.

VMware workstation checks¬†https://softwareupdate.vmware.com/cds¬†and¬†https://ueip.vmware.com/, but I didn’t decrypt the traffic there yet.

Anyone with the latest official news on this?

Edit 20120823 0631UTC:

Two links I just found:

So yes, there was a temporary 2b || !2b crisis in the update service.

Edit 20120823 0711UTC:

Now it is 20120823 in California too, so now the¬†VMware Workstation¬†pages and VMware Workstation What”s new¬†pages¬†got updated and shows that VMware Workstation 9 is out.

This is the quote from the dialog on the right: Read the rest of this entry »

Posted in Power User, VMware, VMware Workstation | 1 Comment »

Solving the “Some projects have been bound to server locations that may be incorrect.” in Visual Studio 2010 when using Team Foundation System 2010 #VS2010 #TFS2010

Posted by jpluimers on 2012/08/23

A while ago, I inherited a bunch of C# and VB.NET projects. One of them always generated the below error when including it in Team Foundation System (yes, the original projects were salvaged from Visual Source Shredder version 6.0c):

[Source Control]
Some projects have been bound to server locations that may be incorrect.
A location may be incorrect either because it does not contain the majority of the projects' files or because those files are not in the correct location relative to the specified server folder.
You should probably fix all the bindings in the solution. However, you may continue and bind these projects to the specified locations even when some may be incorrect.
[Fix server bindings] [Continue with these bindings] [Help]

First I tried the Help button: it links to a Help page on MSDN explaining the error can be cause with some statistics on projects not being in the source control system. Since all projects were, there, I looked for more information.

I tried finding a “Fix Server Bindings”¬†or a¬†2010 “Some projects have been bound to server locations that may be incorrect”¬†link that fitted my use case (getting projects from VSS into TFS), but the solutions I tried eventually all led to the same issue.

Fixing the server bindings would always fail: the solution (which itself is also a project) would get the status Invalid.

The next steps were these:

  1. add an empty solution in the same directory as the original one,
  2. add that solution to TFS
  3. add the projects from the original solution to this solution one by one
  4. check after each addition of the bindings were still OK using the “File”, “Source Control”, “Change Source Control” sequence on the right.
    (note that you don’t always see “Change Source Control”, if you don’t select the solution in the Solution Explorer before going to the File menu).
  5. text compare both .SLN solution files
  6. observe that “Solution Items” actually is a project just like the others:
    Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{8D9964D4-6129-4B8F-9238-F9161A02B968}"
    ProjectSection(SolutionItems) = preProject
    ...
    Framework\Config.dll = Framework\Config.dll
    ...
    EndProjectSection
    EndProject
  7. add the existing solution item from the original solution to this solution one by one, check
  8. check after each addition of the bindings were still OK¬†using the “File”, “Source Control”, “Change Source Control” sequence on the right.
    (note that you don’t always see “Change Source Control”, if you don’t select the solution in the Solution Explorer before going to the File menu).
  9. copy the non-existing solution items to the solution one by one using the text compare tool (yes, a lot of the projects are dirty and contain references to files that are not in the version control system)
    save after every copy, then reload the project in Visual Studio
  10. check after each addition of the bindings were still OK¬†using the “File”, “Source Control”, “Change Source Control” sequence on the right.
    (note that you don’t always see “Change Source Control”, if you don’t select the solution in the Solution Explorer before going to the File menu).
  11. after a few files, suddenly the “Invalid” appeared, so the issue has to do with missing files.

Reading the Help more carefully, with in the back of my mind keeping “Solution Items” all as projects, I finally got the cause:

When some percentage of Solution Items cannot be found locally, and are not in the version control system, Visual Studio marks the solution binding to the version control system as “Invalid”.

The temporary solution is to ignore the error, until I have found all the missing files (they are scattered around some network shares), or made sure they are not needed at all.
There are many of those (you recognize them from the missing padlock icon in the Solution Explorer).

Version control rot is just like link rot, that’s why one of the high priority action items is to introduce for build automation¬†at this client, then deploy those as clean builds into the Develop and Test stages of the DTAP, then verify if the solutions still work).

–jeroen

Posted in .NET, C#, C# 1.0, C# 2.0, C# 3.0, C# 4.0, C# 5.0, Development, Software Development, Source Code Management, TFS (Team Foundation System), VB.NET, Visual Studio 2010, Visual Studio and tools | Leave a Comment »

 
%d bloggers like this: