Payne C Sams Teach Yourself ASP. NET in 21 Days / Workshop

Computers & Technology
Education & Reference
Business & Investing
Science & Math

Sams Teach Yourself ASP. NET in 21 Days
Authors: Payne C
Published year: 2003
Pages: 223-225/307

<< Previous page
Table of contents
Next page >>


IOTA^_^

	Sams Teach Yourself ASP.NET in 21 Days, Second Edition By Chris Payne
	Table of Contents

	Day 21. Securing Your ASP.NET Applications

Workshop

This workshop will help reinforce the concepts covered in today's lesson. The answers can be found in Appendix A.

Quiz

1:	What's the difference between authentication and authorization?
2:	What's the difference between basic and digest authentication?
3:	What's the anonymous user account's name in Windows?
4:	Write some code to set an authorization cookie and redirect to an originating URL.
5:	What does the second parameter in the `SetAuthCookie` method do?
6:	Will the following code work? <configuration> <authentication mode="Forms"> <forms name="AuthCookie" loginUrl="day21/login.aspx"> </forms> </authentication> </configuration>
7:	What do the wildcard characters `*` and `?` mean to ASP.NET within the authorization section of `web.config` ?
8:	True or False: When impersonation is enabled, ASP.NET can operate on behalf of the operating system.

Exercise

[click here]

Create a login page that validates user credentials against a database. Create a web.config file that uses forms authentication and directs all anonymous users to this login page.


IOTA^_^

Top


IOTA^_^

	Sams Teach Yourself ASP.NET in 21 Days, Second Edition By Chris Payne
	Table of Contents

	Week 3. At a Glance

Week 3. In Review

Congratulations on making it all the way through 21 days! You've covered the most important topics that make up ASP.NET. You learned about the Web forms framework and the basics of building ASP.NET Web pages in Week 1; all about data access and data binding in Week 2; and how to complete your application with business objects and Web services in Week 3. There shouldn't be much that you'll come across in your further journeys through ASP.NET that you haven't at least been exposed to here.

You'll come away from this book with a strong understanding of the way ASP.NET works, and an appreciation of the way it allows you to build powerful Web applications easily. If you are familiar with classic ASP, you've also learned how ASP.NET has been improved over its predecessor, making your life as a developer easier. For example, configuration and deployment are now simple to implement, while still increasing the power available to the developer.

So, where do you go from here? As always, be sure to practice, practice, practice! Feel free to return to earlier examples and build on them. Don't be afraid to delve into a previous topic that you've been curious about. The .NET Framework SDK Documentation provides a lot of technical details on all the concepts you've covered, so it should be an invaluable resource. Also, don't forget the bonus project in the next section, and the bonus days (Days 22 and 23) following this review. These lessons explore topics that will make you an even stronger ASP.NET developer!


IOTA^_^

Top


IOTA^_^

	Sams Teach Yourself ASP.NET in 21 Days, Second Edition By Chris Payne
	Table of Contents

	Week 3. In Review

Bonus Project 3

When you left your banking application last time (see "Week 2 in Review"), you had just added the database functionality. Users could now log in and have their credentials validated against the database, they could view their account information, and they could even pay bills online. As you might recall, there was a lot of code in the ASP.NET pages you built.

This time, you're going to move much of the functionality into business objects, and you've already done much of the hard work! This will decrease the sizes of your ASP.NET pages tremendously by reducing the amount of duplicated code, and making it easier for you to make changes later on.

You're also going to build a Web Service that allows retailers to post transactions to your application remotely—for example, when a customer makes ATM or debit purchases.