Making builds/releases

[Yuriy Zubarev]

Hello everyone,

I've been Java developer for a long time and one of the thing I learnt
is an importance of stringent build process. Java has de facto
standards on directories structure, package names, build routines
(ANT, for example) for test and release versions of a product and so
on.

I was wondering if there are standards/suggestions for .NET
development using either internal facilities of Visual Studio or
external tools or both. It would be interesting to read articles on
this topic if such exist.

Thank you,
Yuriy Zubarev

[Max]

You may notice the following structures for windows applications and control
libraries
<ProjectName>
<ProjectName>\bin
<ProjectName>\bin\Debug
<ProjectName>\bin\Release
<ProjectName>\obj
<ProjectName>\obj\Debug
<ProjectName>\obj\Release

See also Projet Properties and Build Configuration Manager.
"Yuriy Zubarev" <yu***********@yahoo.ca> wrote in message
news:3f***************@shawnews.vc.shawcable.net.. .

Hello everyone,

I've been Java developer for a long time and one of the thing I learnt
is an importance of stringent build process. Java has de facto
standards on directories structure, package names, build routines
(ANT, for example) for test and release versions of a product and so
on.

I was wondering if there are standards/suggestions for .NET
development using either internal facilities of Visual Studio or
external tools or both. It would be interesting to read articles on
this topic if such exist.

Thank you,
Yuriy Zubarev

[Dmitriy Lapshin [C# / .NET MVP]]

Hello Yuriy,

You might want to review the approach outlined at the end of the following
article:
http://www.devcity.net/net/article.a...s=xprogramming

(see the "Automating the Test Execution" section").

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

"Yuriy Zubarev" <yu***********@yahoo.ca> wrote in message
news:3f***************@shawnews.vc.shawcable.net.. .

Hello everyone,

I've been Java developer for a long time and one of the thing I learnt
is an importance of stringent build process. Java has de facto
standards on directories structure, package names, build routines
(ANT, for example) for test and release versions of a product and so
on.

I was wondering if there are standards/suggestions for .NET
development using either internal facilities of Visual Studio or
external tools or both. It would be interesting to read articles on
this topic if such exist.

Thank you,
Yuriy Zubarev

[Mark Hoffman]

You've probably seen Nant, which is loosely based on the Ant tool. We use
that in conjuction with NUnit and NDoc for our unit testing and our
documentation and are quite pleased with it.

http://nant.sourceforge.net/
http://sourceforge.net/projects/nunit
http://ndoc.sourceforge.net/

I've tried getting CruiseControl.NET up and running, but just haven't had
time yet. It looks pretty promising.


"Yuriy Zubarev" <yu***********@yahoo.ca> wrote in message
news:3f***************@shawnews.vc.shawcable.net.. .

Hello everyone,

I've been Java developer for a long time and one of the thing I learnt
is an importance of stringent build process. Java has de facto
standards on directories structure, package names, build routines
(ANT, for example) for test and release versions of a product and so
on.

I was wondering if there are standards/suggestions for .NET
development using either internal facilities of Visual Studio or
external tools or both. It would be interesting to read articles on
this topic if such exist.

Thank you,
Yuriy Zubarev