VS rant
-
So is Ms going to add some features in VS 2010 to solve the problem of "meta" solutions? I mean either one puts all the projects in one BIG VS solution, or one splits it into smaller ones and has to put up with keeping them in sync with no elegant and efficient way to do it. (Hope this does not qualify as a programming question) (Edit) Things are going to get worse if projects end up being split between vs and blend. Software Conf hell! (/Edit)
You can't turn lead into gold, unless you've built yourself a nuclear plant.
-
So is Ms going to add some features in VS 2010 to solve the problem of "meta" solutions? I mean either one puts all the projects in one BIG VS solution, or one splits it into smaller ones and has to put up with keeping them in sync with no elegant and efficient way to do it. (Hope this does not qualify as a programming question) (Edit) Things are going to get worse if projects end up being split between vs and blend. Software Conf hell! (/Edit)
You can't turn lead into gold, unless you've built yourself a nuclear plant.
Pierre Leclercq wrote:
one BIG VS solution,
My preferred modus operandi! :jig:
Wout
-
Pierre Leclercq wrote:
one BIG VS solution,
My preferred modus operandi! :jig:
Wout
Very nice to see someone thinking this. Very often people rant about the slowness of VS due to big solutions. But on the other hand, one big solution garantees VS can correctly manage all dependencies (assuming those have been configured). This is always a pain in the neck to see code go trough the entire cycle design/code/unit test/test coming back with bugs only to have the developer see it is a build problem and go through the cycle once more for nothing.
You can't turn lead into gold, unless you've built yourself a nuclear plant.
-
Very nice to see someone thinking this. Very often people rant about the slowness of VS due to big solutions. But on the other hand, one big solution garantees VS can correctly manage all dependencies (assuming those have been configured). This is always a pain in the neck to see code go trough the entire cycle design/code/unit test/test coming back with bugs only to have the developer see it is a build problem and go through the cycle once more for nothing.
You can't turn lead into gold, unless you've built yourself a nuclear plant.
Pierre Leclercq wrote:
Very often people rant about the slowness of VS due to big solutions.
True, but it's a good excuse to buy a really powerful machine *tim the toolman grunt*. Also I think they're multi-threading the build properly nowadays, so that should mitigate the problem somewhat on multi-cores.
Wout
-
Pierre Leclercq wrote:
Very often people rant about the slowness of VS due to big solutions.
True, but it's a good excuse to buy a really powerful machine *tim the toolman grunt*. Also I think they're multi-threading the build properly nowadays, so that should mitigate the problem somewhat on multi-cores.
Wout
I
wout de zeeuw wrote:
Also I think they're multi-threading the build properly nowadays, so that should mitigate the problem somewhat on multi-cores.
I've had to turn that off on more than one big solution. It seems if you mix C# and C++/CLI the battle of the build engines completely destroys all hope of the dependency management working things out if it is allowed to compile more than one at a time...I'm not entirely sure it works correctly with just pure C# or C++ if the multi-threading is lef enabled.
-
So is Ms going to add some features in VS 2010 to solve the problem of "meta" solutions? I mean either one puts all the projects in one BIG VS solution, or one splits it into smaller ones and has to put up with keeping them in sync with no elegant and efficient way to do it. (Hope this does not qualify as a programming question) (Edit) Things are going to get worse if projects end up being split between vs and blend. Software Conf hell! (/Edit)
You can't turn lead into gold, unless you've built yourself a nuclear plant.
I very much doubt it. VS2010 is looking more and more like one of the less appealing releases* with every minute. Apparently the VS team is no longer accepting new bug reports for this release[^], which is exactly the pattern we saw during the VS2005 beta cycle (when devs everywhere were screaming for another Beta, but got a buggy RTM instead. * just like VC5, VS2002 and VS2005. It seems every second VS release is a bit of a dog, so I'm not waiting up.
Anna :rose: Having a bad bug day? Tech Blog | Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
So is Ms going to add some features in VS 2010 to solve the problem of "meta" solutions? I mean either one puts all the projects in one BIG VS solution, or one splits it into smaller ones and has to put up with keeping them in sync with no elegant and efficient way to do it. (Hope this does not qualify as a programming question) (Edit) Things are going to get worse if projects end up being split between vs and blend. Software Conf hell! (/Edit)
You can't turn lead into gold, unless you've built yourself a nuclear plant.
What I wish was that you could share source code between solutions instead of having to compile common code into separate assemblies. I see no reason why they can't add a "source namespaces" option to the "add a refernce" feature, and simply scan one (or more) specified folders for namespaces in the actual source code. That's pretty much the only thing I miss about C++ now.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
