This isn't the project you're looking for



  • The project I'm currently working on is split up into multiple VS solutions (workspaces in other IDEs' terminology) to avoid introducing unintended dependencies. (Whether this is TRWTF is up for debate).

     I discovered this morning that two of solutions have projects called  (slightly anonymised) Example.Web.Common. The problem is that they're not the same one. Someone forked the project at some point and didn't rename it (or change the name of the dll it builds), opening up all kinds of confusion. In order to bring sanity I'm now having to merge the two.



  • @pjt33 said:

    VS solutions (workspaces in other IDEs' terminology)

    Or "project groups" by other other IDEs.



  • @derula said:

    @pjt33 said:
    VS solutions (workspaces in other IDEs' terminology)

    Or "project groups" by other other IDEs.

    Insert pedantic dickweedery about whether solutions, workspaces, and project groups are really all analagous ideas. (I actually was kind of interested that you'd draw that comparison but my questioning of what led you to do so was coming out as pedantic dickweedery anyway.)



  • @kilroo said:

    @derula said:
    @pjt33 said:
    VS solutions (workspaces in other IDEs' terminology)

    Or "project groups" by other other IDEs.

    Insert pedantic dickweedery about whether solutions, workspaces, and project groups are really all analagous ideas.

    The real WTF is how bad the Delphi IDE still is. There were some improvements from Delphi 7 to XE, like cold folding and being able to indent multiple lines by selecting them and hitting tab (or outdenting by hitting shift+tab). Also sometimes there are popups with useless information when you hover certain words with links in them that do absolutely nothing when clicked. But that's about it for the improvements.

    (Of course, I only have the Starter Edition which I think leaves out one vital IDE feature, but still... it's kind of embarrassing that the standard KDE text editor is better at automatic indentation than this really expensive IDE)



  • @derula said:

    @kilroo said:
    @derula said:
    @pjt33 said:
    VS solutions (workspaces in other IDEs' terminology)
    Or "project groups" by other other IDEs.
    Insert pedantic dickweedery about whether solutions, workspaces, and project groups are really all analagous ideas.
    The real WTF is how bad the Delphi IDE still is. There were some improvements from Delphi 7 to XE, like cold folding and being able to indent multiple lines by selecting them and hitting tab (or outdenting by hitting shift+tab). Also sometimes there are popups with useless information when you hover certain words with links in them that do absolutely nothing when clicked. But that's about it for the improvements.

    (Of course, I only have the Starter Edition which I think leaves out one vital IDE feature, but still... it's kind of embarrassing that the standard KDE text editor is better at automatic indentation than this really expensive IDE)

    The language itself is not bad, but the IDE still sucks although it has improved a lot from the pile of steaming shit it once was.  I recommend a separated environment because it doesn't like VS2010 and SQL Server R2.


  • ♿ (Parody)

    When deployed, do the various executables and DLLs end up in the same directory? Otherwise, how does one DLL for a particular program interfere with another's? Are they going into windows\system32 or something? Or are they really all dependent on each another?



  • #1 not a WTF, and very common on large systems [if my current system was in one SLN, then it would crash trying to load the 300+ projects]

    #2 is a MAJOR WTF.  With a hiddent realy problem... If you have two projects with the same internal GUID, and they are both active in VS (even in different instances), insanity will ensue... Never "clone" a project unless you  reall know what you are doing!



  • @boomzilla said:

    When deployed, do the various executables and DLLs end up in the same directory? Otherwise, how does one DLL for a particular program interfere with another's? Are they going into windows\system32 or something? Or are they really all dependent on each another?

    I found out when adding a project which was using one version of the "Common" one to a solution which contained the other. But we would probably have run into it later when trying to work out WTF that new class which had just been added wasn't showing up. Both forks had already had about 6 changes since the common ancestor.


Log in to reply