Single VS.NET solution for source code

Jan 11, 2010 at 3:40 PM
Edited Jan 11, 2010 at 3:41 PM

Hi! thanks for publishing the source code! How about creating a single VS.NET solution for the whole source code? (Esp. for those poor guys who do not have final builder!)

Thx, Dietrich

Coordinator
Jan 12, 2010 at 6:45 AM

Hi, Dietrich!

I understand you´re looking for a single VS solution. But trust me, not having one is on purpose. Splitting the code not only logically into components but also physically into "component workbenches" (the VS solutions for each component containing its implementation accompanied with tests) serves a very important purpose: it´s a "firewall" against entropie. That ways changes in one component are even less prone to affect other components. Also working on a component in its own solution increases focus.

As you might guess from this we won´t fulfill you your wish ;-)

What we could think about, though, is an alternative build script, eg. NAnt based or using MSBuild. On the other hand, though: FinalBuilder is such a cool tool, no professional developer should be without it. It´s like VS or R# or some unit testing framework. Get FinalBuilder and make your programmer life easier in many regards. I use it every day for all sorts of tasks. I never write a single batch file again. With FinalBuilder so many things can be automated so intuitively. The single license is not expensive. And for a whole team the floating license is pretty cheap too.

-Ralf

Jan 13, 2010 at 12:05 PM

Hi, Ralf!

Yes, an alternative msbuild script would do the job!

-Dietrich

Coordinator
Jan 18, 2010 at 4:05 PM

Hi,

We have now added a batch file for building all solutions and merging the XcoAppSpaces.dll. The file is called "buildAll.bat" and can be found in the build directory. Hope this helps!

-Thomas

Jan 19, 2010 at 10:42 AM
Edited Jan 19, 2010 at 10:43 AM

Hi,

batch file works great - thx!

-Dietrich