IMHO Yes they are and yes you should.

1. They give you confidence in the changes you make (everything else is still working) this confidence is what you need to mold the code, otherwise you might be afraid to change things.
2. They make your code better, most simple mistakes are caught early with the unit tests, catching bugs early and fixing them is always cheaper than fixing them later e.g. when the application is in production.
3. they serve as documentation for other developers on how your code works and how to use it.

The first problem you face is that ASP.Net in itself does not help you to write unit tests, actually it works against you. If you have any choice start using ASP.Net MVC that was created with unit testing in mind. If you can't use ASP.Net MVC you should use the MVP pattern in asp.net so at least you can unit test your logic easily.

Besides that you just need to get proficient in writing unit tests. If you practice TDD, your code is created testable in other words nice and clean.

I would advise you to practice, and pair program. While reading  :

• Agile Software Development, Principles, Patterns, and Practices [Hardcover]
• Head First design Patterns
• GOF Design pattern bible
• Roy osherove's first introduction to unit testing
• unit test patterns bible

or for a first overview  :

• SOLID
• Xunit test patterns

In my opinion: yes they are, and yes you should.

1. They give you confidence in the changes you make (everything else is still working). This confidence is what you need to mold the code, otherwise you might be afraid to change things.

2. They make your code better; most simple mistakes are caught early with the unit tests. Catching bugs early and fixing them is always cheaper than fixing them later, e.g., when the application is in production.

3. They serve as documentation for other developers on how your code works and how to use it.

The first problem you face is that ASP.NET in itself does not help you to write unit tests—actually it works against you. If you have any choice, start using ASP.NET MVC, which was created with unit testing in mind. If you can't use ASP.NET MVC, you should use the MVP pattern in ASP.NET so at least you can unit test your logic easily.

Besides that you just need to get proficient in writing unit tests. If you practice TDD, your code is created testable—in other words, nice and clean.

I would advise you to practice, and pair program. While reading:

• Agile Software Development, Principles, Patterns, and Practices [Hardcover]
• Head First design Patterns
• GOF Design pattern bible
• Roy osherove's first introduction to unit testing
• unit test patterns bible

Or, for a first overview:

• SOLID
• Xunit test patterns

IMHO Yes they are and yes you should.

1. They give you confidence in the changes you make (everything else is still working) this confidence is what you need to mold the code, otherwise you might be afraid to change things.
2. They make your code better, most simple mistakes are caught early with the unit tests, catching bugs early and fixing them is always cheaper than fixing them later e.g. when the application is in production.
3. they serve as documentation for other developers on how your code works and how to use it.

The first problem you face is that ASP.Net in itself does not help you to write unit tests, actually it works against you. If you have any choice star using ASP.Net MVC that was created with unit testing in mind. If you can't use ASP.Net MVC you should use the MVP pattern in asp.net so at least you can unit test your logic easily.

Besides that you just need to get proficient in writing unit tests. If you practice TDD, your code is created testable in other words nice and clean.

I would advise you to practice, and pair program. While reading :

• Agile Software Development, Principles, Patterns, and Practices [Hardcover]
• Head First design Patterns
• GOF Design pattern bible
• Roy osherove's first introduction to unit testing
• unit test patterns bible

or for a first overview :

• SOLID
• Xunit test patterns

IMHO Yes they are and yes you should.

1. They give you confidence in the changes you make (everything else is still working) this confidence is what you need to mold the code, otherwise you might be afraid to change things.
2. They make your code better, most simple mistakes are caught early with the unit tests, catching bugs early and fixing them is always cheaper than fixing them later e.g. when the application is in production.
3. they serve as documentation for other developers on how your code works and how to use it.

The first problem you face is that ASP.Net in itself does not help you to write unit tests, actually it works against you. If you have any choice start using ASP.Net MVC that was created with unit testing in mind. If you can't use ASP.Net MVC you should use the MVP pattern in asp.net so at least you can unit test your logic easily.

Besides that you just need to get proficient in writing unit tests. If you practice TDD, your code is created testable in other words nice and clean.

I would advise you to practice, and pair program. While reading :

• Agile Software Development, Principles, Patterns, and Practices [Hardcover]
• Head First design Patterns
• GOF Design pattern bible
• Roy osherove's first introduction to unit testing
• unit test patterns bible

or for a first overview :

• SOLID
• Xunit test patterns