crusecontrol

[DBC User]

Hello,

I am starting a .Net project, I would like to know which are the tools
I can use to improve the development and delivery of a big project.

I was suggested to use, FIT, Nant, CruseControl and Nunit. Can someone
give me guidenace on which are the correct tools to use and what to
look out for?

My project is Window Form/Web Service project.

Thanks in advance for time and advise.

[Nicholas Paldino [.NET/C# MVP]]

DBC User,

There is no "correct" tools to use. In the end, it's whatever enables
you to develop secure, robust, maintainable code in the quickest time
possible which is the "right" tool. That's something that changes from
person to person, team to team.

For example, instead of using NANT, I would recommend using MSBUILD (in
..NET 2.0 and VS.NET 2005), and for Nunit, I would recommend using a team
edition of VS.NET, where you can generate unit tests for your classes.

But the thing is, that's what ^I^ would recommend. It might not be what
is right for you.

I recommend that you evaluate your needs (beyond the fact that you are
doing a Windows Forms/Web Service project) and then determine the tools that
would fit those needs.

For example, are you going to use source control? If so, then Team
Edition would be a great idea for you (considering that you can do things
like link checkins with unit tests, if the tests fail, you can't check it
in).

I would then post those needs back to the group, and then we can
recommend tools, as well as the pros and cons (based on experience) in using
those tools, which will give you more information to make your decision.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"DBC User" <db*****@gmail.comwrote in message
news:11*********************@v61g2000cwv.googlegro ups.com...

Hello,

I am starting a .Net project, I would like to know which are the tools
I can use to improve the development and delivery of a big project.

I was suggested to use, FIT, Nant, CruseControl and Nunit. Can someone
give me guidenace on which are the correct tools to use and what to
look out for?

My project is Window Form/Web Service project.

Thanks in advance for time and advise.

[DBC User]

Thanks for the input. I am using .Net but not the team edition. I am
also using Source Safe for version control.

I have couple of questions, Is there a way we can write test cases for
WinForms? I can not find anything that really help my GUI testing. I
would like as you said, to run my unit tests before checkin and if the
unit test fails, I do not want to check in instead send a mail out to a
group with the failed information to fix.

Please let me know if I am not clear with my questions.
Thanks again.
Nicholas Paldino [.NET/C# MVP] wrote:

DBC User,

There is no "correct" tools to use. In the end, it's whatever enables
you to develop secure, robust, maintainable code in the quickest time
possible which is the "right" tool. That's something that changes from
person to person, team to team.

For example, instead of using NANT, I would recommend using MSBUILD (in
.NET 2.0 and VS.NET 2005), and for Nunit, I would recommend using a team
edition of VS.NET, where you can generate unit tests for your classes.

But the thing is, that's what ^I^ would recommend. It might not be what
is right for you.

I recommend that you evaluate your needs (beyond the fact that you are
doing a Windows Forms/Web Service project) and then determine the tools that
would fit those needs.

For example, are you going to use source control? If so, then Team
Edition would be a great idea for you (considering that you can do things
like link checkins with unit tests, if the tests fail, you can't check it
in).

I would then post those needs back to the group, and then we can
recommend tools, as well as the pros and cons (based on experience) in using
those tools, which will give you more information to make your decision.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"DBC User" <db*****@gmail.comwrote in message
news:11*********************@v61g2000cwv.googlegro ups.com...

Hello,

I am starting a .Net project, I would like to know which are the tools
I can use to improve the development and delivery of a big project.

I was suggested to use, FIT, Nant, CruseControl and Nunit. Can someone
give me guidenace on which are the correct tools to use and what to
look out for?

My project is Window Form/Web Service project.

Thanks in advance for time and advise.

[Greg Young]

For unit testing winforms based stuff most people use seperation to enable
testing (i.e. using something along the lines of a MVS/MVP pattern
http://www.martinfowler.com/eaaDev/M...Presenter.html
http://codebetter.com/blogs/ben.reic...resenter.aspx).
These patterns allow for easy testing of your logic behind the contol/form.

You probably also want to take a look at nunitforms which can aid you in
unit testing winforms based code http://nunitforms.sourceforge.net/

Also Nicholas: I personally dislike that feature since it leads you away
from a test first mentatility and to a code first mentality.

Cheers,

Greg Young
MVP - C#
http://codebetter.com/blogs/gregyoung
"DBC User" <db*****@gmail.comwrote in message
news:11**********************@h44g2000cwa.googlegr oups.com...

Thanks for the input. I am using .Net but not the team edition. I am
also using Source Safe for version control.

I have couple of questions, Is there a way we can write test cases for
WinForms? I can not find anything that really help my GUI testing. I
would like as you said, to run my unit tests before checkin and if the
unit test fails, I do not want to check in instead send a mail out to a
group with the failed information to fix.

Please let me know if I am not clear with my questions.
Thanks again.
Nicholas Paldino [.NET/C# MVP] wrote:

>DBC User,

There is no "correct" tools to use. In the end, it's whatever
enables
you to develop secure, robust, maintainable code in the quickest time
possible which is the "right" tool. That's something that changes from
person to person, team to team.

For example, instead of using NANT, I would recommend using MSBUILD
(in
.NET 2.0 and VS.NET 2005), and for Nunit, I would recommend using a team
edition of VS.NET, where you can generate unit tests for your classes.

But the thing is, that's what ^I^ would recommend. It might not be
what
is right for you.

I recommend that you evaluate your needs (beyond the fact that you
are
doing a Windows Forms/Web Service project) and then determine the tools
that
would fit those needs.

For example, are you going to use source control? If so, then Team
Edition would be a great idea for you (considering that you can do things
like link checkins with unit tests, if the tests fail, you can't check it
in).

I would then post those needs back to the group, and then we can
recommend tools, as well as the pros and cons (based on experience) in
using
those tools, which will give you more information to make your decision.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"DBC User" <db*****@gmail.comwrote in message
news:11*********************@v61g2000cwv.googlegr oups.com...

Hello,

I am starting a .Net project, I would like to know which are the tools
I can use to improve the development and delivery of a big project.

I was suggested to use, FIT, Nant, CruseControl and Nunit. Can someone
give me guidenace on which are the correct tools to use and what to
look out for?

My project is Window Form/Web Service project.

Thanks in advance for time and advise.