Building an ASP.NET Intranet

By: Kourosh Ardestani

Write A Review

eText | 9 November 2013

At a Glance

Format
PDF

eText

$64.99

or 4 interest-free payments of $16.25 with

Instant online reading in your Booktopia eTextbook Library *

Why choose an eTextbook?

Instant Access *

Purchase and read your book immediately

Read Aloud

Listen and follow along as Bookshelf reads to you

Study Tools

Built-in study tools like highlights and more

* eTextbooks are not downloadable to your eReader or an app and can be accessed via web browsers only. You must be connected to the internet and have no technical issues with your device or browser that could prevent the eTextbook from operating.

Do you want to know how you can use ASP.NET to build a modular Intranet? An intranet that could be used to share information within a small or medium sized organization? Well, congratulations, you've come to the right place! Microsoft provides sample architecture for this sort of 'portal' application, available at www.IBuySpy.com. Since they encourage developers to use this as a starting point for their own applications, we decided to take advantage ofthe functionality it offers. We will be taking this example and extending it to suit our needs, learning some valuable lessons in code reuse along the way. Just as we used the IBuySpy example as the starting point for our Intranet, readers are encouraged to use the code in this book in their own applications - the modules we have created will slot into any implementation of the IBuySpy architecture, and let's be honest - no-one wants to re-invent the wheel, right? What This Book Covers The book starts by discussing general issues of Intranet development: o Chapter 1 looks at why developing Intranet sites is different from building sites for the Internet. There are some considerations that need to be addressed in order for Intranet projects to be successful. The next three chapters look at the IBuySpy Architecture. o Chapter 2 provides a thorough explanation of the architecture and what it provides. It also explains why we decided to use the existing architecture rather than starting from scratch.