Bachelor s Project Report Final

7/23/2019 Bachelor s Project Report Final

1/65

Intranet Website SolutionBased on Microsoft SharePoint Server

Foundation 2010

December 14, 2012

Authors:Wilmer Entena128809

Rimon Nassori131311

Supervisor: Henrik Kronborg Pedersen

VIA University College, Horsens DenmarkICT Engineering Department


2/65

Wilmer Entena128809Rimon Nassori131311

Intranet Website SolutionBased on Microsoft SharePoint ServerFoundation 2010

2

Table of Contents

List of Figures and Tables .................................................................................................................... 3

Abstract ................................................................................................................................................ 5

1. Introduction ...................................................................................................................................... 6

2. SharePoint Foundation 2010 Architecture ....................................................................................... 7

3. Intranet Solution Site ....................................................................................................................... 8

4. System Specification ...................................................................................................................... 10

4.1 Use Case Model ....................................................................................................................... 10

4.2 Activity Diagram...................................................................................................................... 11

5. Site Planning .................................................................................................................................. 13

6. Web Parts ....................................................................................................................................... 14

6.1 Departments Web Part ............................................................................................................. 14

6.2 Company News Web Part ........................................................................................................ 16

6.3 Announcements Web Part ........................................................................................................ 17

6.4 Discussion Board Web Part ..................................................................................................... 19

6.5 Information Web Part............................................................................................................... 22

6.6 Quick Links Web Part .............................................................................................................. 23

7. Login Page and Authentication ...................................................................................................... 25

8. Main Site ........................................................................................................................................ 27

8.1 Masterpage ............................................................................................................................... 28

8.2 Main Site Default Page ............................................................................................................ 29

9. Department Sub Sites ..................................................................................................................... 30

10. Shared Documents ....................................................................................................................... 31

11. Calendar ....................................................................................................................................... 31

12. Contact List .................................................................................................................................. 32

13. Company Blog ............................................................................................................................. 32

15. Testing .......................................................................................................................................... 33

16. Results .......................................................................................................................................... 33

17. Discussion .................................................................................................................................... 34

18. Conclusion ................................................................................................................................... 35

References .......................................................................................................................................... 36


3/65



3

Appendices ......................................................................................................................................... 38

APPENDIX A ................................................................................................................................ 38

APPENDIX B ................................................................................................................................ 52

APPENDIX C ................................................................................................................................ 55

List of Figures and Tables

Figure 2.1SharePoint Foundation 2010 Architecture Diagram ....................................................... 7

Figure 4.1.1 Use Case Diagram ......................................................................................................... 10

Figure 4.1.2 Activity Diagram for User Login .................................................................................. 11

Figure 4.1.3 Activity Diagram for Adding Discussion ...................................................................... 12

Figure 5.1 Rootsite and Subsites ........................................................................................................ 13

Figure 6.1.1Code location for Departments web part in Project Solution..................................... 14

Figure 6.1.2Departments Web Part View ...................................................................................... 15

Figure 6.1.3The code for Departments Web Part ......................................................................... 15

Figure 6.2.1Code location for Company News web part in Project Solution ................................ 16

Figure 6.2.2Company News Web Part View ................................................................................. 16

Figure 6.2.3The code for Companys Web Part............................................................................ 17

Figure 6.3.1Code location for Announcements web part in Project Solution ............................... 18

Figure 6.3.2Announcements Web Part View ................................................................................. 18

Figure 6.3.3The code for Announcements Web Part ..................................................................... 19

Figure 6.4.1Code location for Discussion Board web part in Project Solution ............................. 20

Figure 6.4.2Discussion Board Web Part View .............................................................................. 20

Figure 6.4.3The code for Discussion Board Web Part .................................................................. 21

Figure 6.5.1Code location for Information web part in Project Solution ...................................... 22

Figure 6.5.2Information Web Part View ....................................................................................... 22

Figure 6.5.3The code for Information Web Part ............................................................................ 23

Figure 6.6.1Code location for Quick Links web part in Project Solution ..................................... 24

Figure 6.6.2Quick Links Web Part View ....................................................................................... 24

Figure 6.6.3The code Quick Links Web Part ................................................................................. 25

Figure 7.1 Login and Authentication Flow Diagram ......................................................................... 25

Figure 7.2 Token and Claims ............................................................................................................. 26


4/65



4

Figure 8.1Main Site Default Page View ........................................................................................ 27

Figure 8.1.1Location of the Masterpage in Project Solution ......................................................... 28

Figure 8.1.2 Masterpage Layout ........................................................................................................ 29

Figure 8.1 Main Site Default Page WebPartZone with codes ........................................................... 29

Figure 9.1 Department Sites Homepage Interface ............................................................................ 30

Figure 9.2 Departments Site Location in Project Solution ............................................................... 30

Figure 10.1 Dialog box for Uploading Files and Documents ............................................................ 31

Figure 11.1 Sites Calendar View ...................................................................................................... 31

Figure 12.1 Contact List View ........................................................................................................... 32

Figure 13.1 Company Blog Interface ................................................................................................. 32

Table 8.1Functional Area of SharePoint Main Site ....................................................................... 27


5/65



5

Abstract

Background: The objective of this study is to provide a company and organization an intranetsolution site based on SharePoint Foundation 2010 that will help their team members to work

together efficiently. The study was done in close consultation with companies and organization that

requires challenging ideas on how to meet their requirements on information sharing and by

investigating and learning on how Microsoft SharePoint technology can achieve these goals.

Results: SharePoint site can deliver a solution for business collaboration with its features and

applications. We have created an effective Intranet Website Solution system based on SharePoint

Foundation 2010 Server.

Significance: The significance of the studygave us the opportunity to demonstrate and provide the

company a solution for their intranet site and gave their team members a useful tool for working

together.


6/65



6

1. Introduction

Companies and organizations are finding ways and great solution for their team members to be able

to share significant and vital information throughout the company or organization, and the goal of

this project is to deliver the solution that they needed.

LN Pro ApS is a small IT company in rhus Denmark specializing in development of Commerce

Express an IBM Lotus Notes based CRM system for its clients. The company is in need of an

intranet collaboration website to be presented to its perspective clients. The intranet website will be

based on Microsofts SharePoint Foundation Server 2010 technology. The company asked us to

create an intranet websitebased on the clients requirement and will run on a Microsoft SharePoint

Foundation Server 2010 system. The clients intranet site is requiring us to program all thefunctionalities of a SharePoint website.

The aim of this project was to create an Intranet Solution Site based on SharePoint Server

Foundation 2010. The system will create an environment for the employees and team members of

the organization where they can share information quickly and efficiently.

The intranet system that we created will be the basis for the company to take advantage of the

SharePoint technology and the significant role it will provide to their business. The system was

carefully planned and executed through thorough investigation, learning process, and teamwork.

The following chapters of this report will provide the reader a deep understanding about the Intranet

SharePoint Site system that we created and the methodologies that we used. Thus this project will

not only open a new and challenging idea but can also achieve the companys goal of an effective

channel of communication in information technology.


7/65



7

2. SharePoint Foundation 2010 Architecture

The main part of the report discussed about the detailed information of the planning, designing andprogramming the intranet website. In this section includes the structure and architecture of the site.A brief description of the SharePoint technology that was used as the core basis for this project wasalso introduced. The main components and functionalities of the site are also covered in thissection. The diagram below illustrates the architectural structure our SharePoint site project.

*Please see Appendix C for setting up and configuration of SharePoint 2010 Foundation sever.

Figure 2.1SharePoint Foundation 2010 Architecture Diagram


8/65



8

3. Intranet Solution Site

This is a brief overview of the SharePoint architecture implemented in this project. Thedevelopment environment was done on Windows 7 Professional (64 bit) operating system as part ofthe SharePoint Foundation 2010 server requirements. Internet browser, Visual Studio 2010,SharePoint Designer 2010 are the users interface for the use and development of the SharePoint

site.

SharePoint Foundation Server 2010 is the core foundation in building the intranet website thatincludes the following features and applications:

1. List, Libraries, Content Types, Field Types this service allows the users to store,manage, and share all types of files and data that the team members need for collaborationwithin the company or organization.

2. Web Parts this is the structure of a SharePoint site within the page where the differentdata and applications are easily accessible by the user.

3. Web Pages consists of a Master page and other web pages built on top of ASP.NET,these pages is the users interface to access data and applications that runs in the

SharePoint site.

4. Site Definitionis the definition of what a site is in SharePoint, it consists of .aspx pages

and xml files with Collaborative Application Mark-up Language (CAML).

5. Service Application the application services available to SharePoint site that includesweb content management, search service, email integration, Business Connectivityservices, that can be shared across the site and can be access by the user through a hostingweb application.

6. Security and Authentication the permission and roles assigned to the groups and teammembers that restrict different users to control the access specific SharePoint site and

pages.


9/65



9

1Microsoft SQL Server is a relational database management system developed by Microsoft. As a

database, it is a software product whose primary function is to store and retrieve data as requestedby other software applications, be it those on the same computer or those running on anothercomputer across a network (including the Internet). There are at least a dozen different editions ofMicrosoft SQL Server aimed at different audiences and for different workloads (ranging from smallapplications that store and retrieve data on the same computer, to millions of users and computersthat access huge amounts of data from the Internet at the same time).

2IIS (Internet Information Server) is one of the most powerful web servers from Microsoft that isused to host your ASP.NET Web application. IIS has its own ASP.NET Process Engine to handlethe ASP.NET request. So, when a request comes from client to server, IIS takes that

request and process it and send response back to clients.

3The ADO.NET Data Services framework is Microsofts technology for creating and consumingdata services. These data services use the Entity Data Model (EDM) to model data in terms ofentities. These entities are exposed as URI-addressable resources that can be accessed usingstandard HTTP requests. ADO.NET Data Services also establishes uniform patterns that UI widgetframeworks and libraries can leverage to provide additional services on top of the data services.

1http://en.wikipedia.org/wiki/Microsoft_SQL_Server2Article posted by Abhijit Jana on 3/14/2010 - http://www.dotnetfunda.com/articles/article821-beginners-guide-how-iis-process-aspnet-request.aspx3Mike Flasko - Microsoft Corporation Published: August 2008- http://msdn.microsoft.com/en-

us/library/cc956153.aspx


10/65



10

4. System Specification

4.1 Use Case Model

Use case model is a tool used for defining system specifications. It describes the goals of the

users, the interaction between the users and the system.

Figure 4.1.1 Use Case Diagram

The use case diagram shows the functionalities for the system. There are to actors Admin and

User. The association between user/admin and use cases, shows the functionalities which the

user/admin can use. The inheritance between the admin and the user means, that the admin have the

same functionalities as the user has.

*Please see Use Case Specification on Appendix A


11/65



11

4.2 Activity Diagram

Figure 4.1.2 Activity Diagram for User Login


12/65



12

Figure 4.1.3 Activity Diagram for Adding Discussion


13/65



13

5. Site Planning

The requirements of the intranet site were carefully planned and various consultation and referenceswas made before the beginning of the project. The intranet website project is composed of a toplevel site and below is the sub site collection that includes the following departments:

1. Human Resources2. Marketing3. Sales4. Finance5. I.T.

The applications and features of the site include the following:

1. Departments Link Members can go to home page of their designated department2. Shared Documentsmembers can share files and documents3. Calendarmembers are able to view events and schedules within the company4. Contact Lista useful tool to find contacts in the organization5. Company Newsmembers are able to view, read, and post latest news of the company6. Announcementsmembers are able to view, read, and post announcements7. Informationmembers are able to view, read, and post related information8. Discussion Boardmembers can participate in teams discussions9. Quick Linkslink to related websites10. Company Blogmembers are able to view, read, and post blogs11.

Social Mediaa useful tool for integrating social media to the SharePoint site

Each sub site will also implement the required functionalities. Each users and members will beassigned a specific authorization and permissions within the site.

Figure 5.1 Rootsite and Subsites


14/65



14

6. Web Parts

Web parts provide the users the access to different applications and data on the same page. This is auseful tool for a dynamic and collaboration site such as SharePoint. Web part is a list in SharePointsite and a reusable item that can be implemented in different sites in the site collection. This sectionwill explain the functional description of the web parts and code.

6.1 Departments Web Part

The Department Web Part includes five different links. The links are the sub sites, HumanResources, Marketing, Finance, Sales, IT Department. The link will send the user to the

designated home page of the department. The departments web part is a list designed andcreated in Visual Studio 2010 and uploaded on the server.

File Name: DepartmentsUserControl.ascx

Location: http://rootsite/Lists/Departments/AllItems.aspx

Figure 6.1.1Code location for Departments web part in Project Solution


15/65



15

Figure 6.1.2Departments Web Part View

Figure 6.1.2 shows the actual layout and design of the departments web part. Consist of five

different links to each departments home page.

Figure 6.1.3The code for Departments Web Part

Figure 6.1.3 shows the code for the departments link web part. Each department is enclosed on ahyperlink markup that will eventually send the user to the departments homepage. The link for the

CSS is also included in the code for the web parts format that point out to the url of the CSS file.


16/65



16

6.2 Company News Web Part

The company news web part is a where a member or user can post a news on the companysweb part area. The user can view, add, edit, and delete items on the web part. The companynews web part is a list designed and created in xml code using Visual Studio 2010 anduploaded on the server.

File Name: Schema.xml

Location: http://rootsite/Lists/Company News/AllItems.aspx

Figure 6.2.1Code location for Company News web part in Project Solution

Figure 6.2.2Company News Web Part View

Figure 6.2.2 shows the actual layout and design of the company news web part. The heading,the content part, the add new item button can be use by the member to add a new item on thenews area. The user can view recent posted news, add a new item to the news, delete or editthe news that the member posted.


17/65



17

Figure 6.2.3The code for Companys Web Part

Figure 6.2.3 shows the partial xml code of company news web part which creates the fieldstitle and body forms. The view of the forms is also coded in xml that will display thecompany news items of the web part. The data of the company web part list are stored on theSharePoints SQL database server.

6.3 Announcements Web Part

The Announcement Web Part has a add button, if you click on the add button it will show youa new window where you can create an announcement. It includes a Title its a required

field, so you have to write something inside it. A Description describing what you are aboutto announce. Then we have Department just to tell what kind of department you from. A

Date Expire so you can choose when you want your announcement to expire, its also a

required field. And last My Job Title so they others can see if you are a manager, memberetc. After done that click on save and we can see the new announcement under the Web PartAnnouncements. The announcements web part is a list designed and created in xml codesusing Visual Studio 2010 and uploaded on the server.


Location: http://rootsite/Lists/Announcements/AllItems.aspx


18/65



18

Figure 6.3.1Code location for Announcements web part in Project Solution

Figure 6.3.2Announcements Web Part View

Figure 6.3.2 shows the actual layout and design of the Announcement web part. The heading,the content part, the add new announcement button can be use by the member to add a newitem on the announcement area. The user can view recent posted announcement, add a new

item to the announcement, delete or edit the announcement that the member posted.


19/65



19

Figure 6.3.3The code for Announcements Web Part

Figure 6.3.3 shows the partial xml code which creates the fields title, body, and expiry date.The view of the forms is also coded in xml that will display the announcements items of theweb part. The data of the announcement web part list are stored on the SharePoints SQLdatabase server.

6.4 Discussion Board Web Part

The discussion board web part is a tool for members and user within the company where theuser can post a topic and be able to reply to the topics that was posted by the member. Thesubject is being displayed together with the user who created the subject or topic. The usercan add an item by clicking on the add item button on the web part. The discussion board web

part is a list designed and created in xml codes using Visual Studio 2010 and uploaded on theserver.


Location: http://rootsite/Lists/Discussion Board/AllItems.aspx


20/65



20

Figure 6.4.1Code location for Discussion Board web part in Project Solution

Figure 6.4.2Discussion Board Web Part View

Figure 6.4.2 shows the actual layout and design of the Discussion Board web part. Theheading, the content part, the add new discussion button can be use by the member to add a

new subject on the discussion area. The user can view recent posted discussion, add a newitem to the discussion, delete or edit the discussion that the member posted.


21/65



21

Figure 6.4.3The code for Discussion Board Web Part

Figure 6.4.3 shows the partial xml code which creates the fields subject andbody. The viewof the forms is also coded in xml that will display the discussions subject, author, replies, andthe date when the subject was last updated from the web part. The data of the discussion

board web part list are stored on the SharePoints SQL database server.


22/65



22

6.5 Information Web Part

The information web part is the area on the page where a member or user can post usefulinformation on the companys information area. The user can view, add, edit, and delete items

on the web part. The information web part is a list designed and created in xml code usingVisual Studio 2010 and uploaded on the server.


Location: http://rootsite/Lists/Information/AllItems.aspx

Figure 6.5.1Code location for Information web part in Project Solution

Figure 6.5.2Information Web Part View

Figure 6.5.2 shows the actual layout and design of the Information web part. The heading, thecontent part, the add new item button can be use by the member to add a new information onthe information area. The user can view recent posted information, add a new item to theinformation, delete or edit the information that the member posted.


23/65



23

Figure 6.5.3The code for Information Web Part

Figure 6.5.3 shows the partial xml code for the information web part which creates the fieldstitle and body. The view of the forms is also coded in xml that will display the title and the

body of the web part. The data of the information web part list are stored on the SharePointsSQL database server.

6.6 Quick Links Web Part

The Quick Links Web Part is a link to other related website that a member can use. A separatewindow will appear on the screen when the user clicks on the link. The information web partis a list. The quick links web part is a list designed and created in Visual Studio 2010 anduploaded on the server.

File Name: Quick LinksUserControl.ascx

Location: http://rootsite/Lists/Quick Links/AllItems.aspx


24/65



24

Figure 6.6.1Code location for Quick Links web part in Project Solution

Figure 6.6.2Quick Links Web Part View

Figure 6.6.2 shows the actual layout and design of the quick links web part. The links will

send the user to another window that points to the sites url.


25/65



25

Figure 6.6.3The code Quick Links Web Part

Figure 6.6.3 shows the code for the quick link web part. Each link is enclosed on a hyperlinkmarkup that will eventually send the user to the external site s homepage that will opens to a new

window.

7. Login Page and Authentication

In our web site we have one user credentials, with username and password. By using claimbased authentication thats actually enough to access the web site. When a user is logging in

an Identity is assigned to that session, and that Identity is maintained until the user logs out orit expires.

Figure 7.1 Login and Authentication Flow Diagram


26/65



26

If we look at the figure, we can see that when a user is trying to log in, the application wellcheck if the users is authenticated, and if the user is authenticated, then it gives an Identity andthe user gets the right to access the application. If the user is not authenticated, then the user isdenied access.

The Claim based Authentication lets us set whether Windows authentication is enabled andwhether Forms Based Authentication via ASP.NET. By using Forms Based Authentication itlets us use either a default Sign in page provided by SharePoint or our own customized Signin page.

In the above figure there are some basic things involved. There are Identity, Tokens, Claims,etc.

Identity can identify anything its like a group of information that identifies a user. When

Identity is passed as a stream of bytes, then its called Token. Token contains information

about the user in the Claim format, and the token contains specific information.

Figure 7.2 Token and Claims

Token can be XML based Security Assertion Makeup Language (SAML) format. But an

application can also use a simpler token called Simple web Token (SWT). Benefit is that we do not

pass user credential but, but other information about the user to the application.

Identity provider authenticates the user and creates the token with claims, and also known as

Security token services (STS)


27/65



27

8. Main Site

This is the first page that will be displayed to the user after logging in to his/her account. The mainsite consists of a masterpage, a default page, the links, and the web part features and functionality.The area is divided into four parts, 1. the header part where the company logo, login menu, 2. thetop menu links, 3. quick launch menu area where the other site menus are located, and the 4.content area of the main page where the content and web parts of the site and pages will be placed.

Figure 8.1Main Site Default Page View

*Please refer toTable 8.1 for the detailed description of the Main Site default page.

Table 8.1Functional Area of SharePoint Main Site

FigureLabel

Functions Description of Functionality

A Logo Display the company logo, can also be use as a link to return tosites home page.

B Site Title Display the specific title of the page that will guide the users whenexploring the site.

C Accounts Menu This is where the user can Login or Logout from their account.

D Top Menu The horizontal navigation menu that links to sites other pages andfunctionalities.

E Search Bar The user can search the page using this tool.


28/65



28

F Help Button Link to Microsoft SharePoint help site.

G Launch Menu The vertical navigation menu that links to the sites other pagesand functionalities.

H All Site Content The user can view all the site content.

I Content Area This is the area where the content, web parts and functionalitiesare displayed.

8.1 Masterpage

File Name: mycustom.master

Location:http://rootsite/_catalogs/masterpage/mycustom.master

The master page was implemented and will serve as the template for all the sites and pages

within the site collections, the layout will be inherited by all the pages. The main parts of the

master page consist of header part where the company logo, site title, accounts menu, top

menu bar, search bar, and help menu button is placed. The quick launch menu and all site

content is at the left side part of the page. The body of the page is located in the content area

of the page. *Please refer to Figure 8.1 for the visual representation.

Figure 8.1.1Location of the Masterpage in Project Solution


29/65



29

Figure 8.1.2 Masterpage Layout

8.2 Main Site Default Page

http://rootsite/default.aspx

The default page of the website will inherit the default masterpage. When the user

successfully login he/she will then be directed to the default page of the site. The page isdesigned with a table inside with three columns and three webpart zones where all the web

parts that we created can be inserted in each webpart zone. Each WebPartZone has a unique id

and a title for each.

Figure 8.1 Main Site Default Page WebPartZone with codes


30/65



30

9. Department Sub Sites

The SharePoint site has five different sub sites for each department namely: Human Resources,

Marketing, Finance, Sales, IT Department. Each members of the site can utilize the features andfunctionality of the SharePoint site. The page will implement the following web parts:

Company News

Announcements

Information

Discussion Board

Quick Links

Every departments site will inherit the default masterpage that we created. Every department also

have individual default page, these default pages will have the container for the web parts. All the

pages, features, and functionality were deployed on the SharePoint server. Each member or groups

within the department has their own permission level which let them perform tasks.

Figure 9.1 Department Sites Homepage Interface

Figure 9.2 Departments Site Location in Project Solution


31/65



31

10. Shared Documents

Sharing documents is a great feature of SharePoint site. We utilize this feature for the groups and

members of the site to be able to share files and important and download documents across the

organization. People can easily access the file using the browser and save it to their local computer.

Figure 10.1 Dialog box for Uploading Files and Documents

11. Calendar

Calendar is another feature of SharePoint where a group or member can create and share their

schedule to the team members. You can add event to the calendar so that team members can view

that specific event when they log in.

Figure 11.1 Sites Calendar View


32/65



32

12. Contact List

The contact list is a great way to find members contact details and information across the

organization. The members can add their information and members can use this as a directory if

they want to contact the person in their organization.

Figure 12.1 Contact List View

13. Company Blog

Blog site is a useful tool for the company where all the members of the group can post their ideas

and share it throughout the organization.

Figure 13.1 Company Blog Interface


33/65



33

15. TestingTesting is an important part of the system, to keep errors and to make our system stable. There aremany kinds of testing. There are two testing parts White Box Testing and Black Box Testing.

In our case we are only using Black box testing. White box testing includes Unit-Test andintegration test, and these 2 are not part of our system, but what we are doing is Black box testing,where we use Performance testing and System testing.

With System testing we are making sure that everything in our system is working as we expected itto work. With performance testing, we are testing if the site and the URL and links acting withoutany errors.

* Please see Appendix B for all result for the System Test and Performance Test

16. Results

The outcome of this project is a working intranet system site that is running on SharePoint

Foundation 2010 server. Information sharing and collaboration with team members are just amongst

the benefits of the system. The usefulness, applications, and features of SharePoint site makes it

easier for the user to get engaged and get easy access to any important information they needed. Weare able to create a site for the company and for each department that needs the same functionality

that an intranet has to offer.

The member can participate and contribute to the content of the site which will be a valuable asset

to the company. Sharing files and documents makes it possible with the SharePoint sites

application. The project was able to achieve its goals and company requirements by implementing

all the necessary tools for an intranet site.


34/65



34

17. Discussion

This focus of this project is to deliver an intranet system based on SharePoint technology using

SharePoint Foundation server 2010 and its functionalities. How to build the system base on thecompanys requirements and what tools and methodologies we need to implement such.

It is critical in every business and its members to have easy access to important information, thus

our system accomplished these objectives in a way that the site performs the necessary tools

needed. Team members can contribute by means of posting news, announcements, information that

others may need. Sharing files and documents can be done and manage easily.

There are two available servers for the SharePoint one is the Foundation Server and the other is the

SharePoint Server. This maybe out of our scope but plays a significant role in creating SharePoint

site. The difficulties we encounter occurs by doing this project is the limitations of what a

SharePoint Foundation 2010 server can do, but without any further discussion about this subject we

recommend the use of SharePoint server for its advance features and functionality both for the user

and the developer.

The system is done in a way, so they dont need to navigate a lot in the system, but where they have

everything in front of them, and by one click the member can submit the valuable content to the

site. The best thing we have on our system is, members in the company can share information, so

when a member logs into the system they can see the information shared right away.

In future developments of the system we would take advantage of the integration of the social

media in SharePoint site, we want create a social environment for the members. And that also senda clear message to the members that its about communication and collaboration with each other.


35/65



35

18. Conclusion

The intranet system site has the functionality that meets the companys requirements.The tools and

methodologies that we used to create a working system were made possible by research,

consultation, learning, creating, and implementing SharePoint tools and technology. Based on the

discussion presented, there are more features and applications can be implemented in the project

and can be done with the continuous development of the intranet site. With this system the team

members of the company can now utilize and take advantage of its features and application to be

able to work together more efficiently and effectively. Information Technology on its own words is

the core of our system.


36/65



36

References

[1] http://shermanstechnicalblog.blogspot.dk/2012/10/adding-custom-css-file-to-your-visual.html

[2] http://www.codeproject.com/Articles/268236/Claim-based-Authentication-and-WIF

[3] http://fabiangwilliams.wordpress.com/2010/07/03/how-to-create-content-types-with-site-columns-in-code-visual-studio-2010-for-sharepoint-2010/

[4] http://rickhilferink.wordpress.com/2011/01/25/creating-a-sharepoint-2010-foundation-masterpage-solution-and-automatically-activate-it-for-all-sites-and-newly-created-subsites/

[5] http://pooyakhamooshi.blogspot.dk/2011/01/how-to-add-custom-css-and-js-files-to.html

[6] http://sharepointgeorge.com/2009/creating-web-application-site-collection-sharepoint-2010/

[7] http://blogs.msdn.com/b/kaevans/archive/2010/07/09/creating-a-custom-login-page-for-sharepoint-2010.aspx

[8] http://msdn.microsoft.com/en-us/library/hh537935.aspx#CustomizingSP2010WebPartUI_AdditionalResources

[9] http://www.sharepointbriefing.com/spcode/develop-sharepoint-2010-content-type-using-visual-studio-2010.html

[10] http://blogs.technet.com/b/mahesm/archive/2010/04/07/configure-forms-based-authentication-fba-with-sharepoint-2010.aspx

[11] http://aarebrot.net/blog/2010/06/frodes-awesome-list-of-sharepoint-column-field-ids-for-sharepoint-2010/

[12] http://www.c-sharpcorner.com/Forums/Thread/182458/how-to-create-page-layout-in-sharepoint-2010-using-visual-st.aspx

[13] http://www.mssharepointtips.com/tip.asp?id=1093&page=2

[14] http://www.youtube.com/watch?v=mFHQYQIMVPk

[15] http://dotnet.dzone.com/articles/introduction-unit-testing-net

[16] http://www.youtube.com/watch?v=_2O5u9ZDzuM

[17] http://www.heathersolomon.com/blog/articles/controlling-single-web-parts-with-css.aspx

[18] http://social.technet.microsoft.com/wiki/contents/articles/8871.sharepoint-2010-how-to-set-up-a-development-environment-en-us.aspx


37/65



37

[19] http://blogs.msdn.com/b/kaevans/archive/2010/07/09/sql-server-provider-for-claims-based-authentication-in-sharepoint-2010.aspx

[20] http://blogs.msdn.com/b/bethmassi/archive/2011/02/18/step-by-step-installing-sql-server-management-studio-2008-express-after-visual-studio-2010.aspx

[21] http://msdn.microsoft.com/en-us/library/ff769953.aspx

[22] SharePoint 2010 Development with Visual Studio 2010, Eric Carter, Boris Scholl, PeterJausovec ISBN-13: 978-0-321-71831-0, ISBN-10: 0-321-71831-3

[23] http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx

[24] IT Department, VIA University College, Aarhus Denmark

[25] https://studienet.viauc.dk/


38/65



38

Appendices

APPENDIX A

Name: Create user AccountIntro: Creating an account for the new userActor: AdminPre-condition: The administrator has .NET administration tool runningPost-condition: The admin has created a new user account and assigned a new role for the userBasic Flow:

1.

The Admin logins into the .NET Administration Tool.2. The Admin clicks the Security Tab.3. The Admin clicks Create user.4. The Admin assigns a username for the User in the username field.5. The Admin assigns a password for the User in the password field.6. The Admin re-enters the previously typed password in the confirm password field.7. The Admin assigns an email for the User in the email field.8. The Admin assigns a role for the User.9. The Admin clicks on the Create User button.

Alternative flows:

A6.1: If the password typed the second time does not match the one entered first time, the

confirm password field displays error, when clicking on the Create button.

Name: Delete user accountIntro: Deletes an account from the systemActor: AdminPre-condition: The administrator has .NET administration tool runningPost-condition: The users account is deleted from the system Basic Flow:

1. The Admin logins into the .NET Administration Tool.2. The Admin clicks the Security Tab.3.

The Admin clicks Manage user.4. The Admin clicks on Delete user.5. The Admin chooses Yes to delete the User.

Alternative flows:A4.1: If the user clicks on the No button when asked if the Owner is sure about deleting the

account (step 4 of the basic flow), the account is not deleted.


39/65



39

Name: Log in on an accountIntro: Log the Admin/User on his accountActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged inBasic Flow:

1. The Admin/User enters his username in the username field2. The Admin/User enters his password in the password field3. The Admin/User clicks on the Log in button4. The Admin/User is logged in onto his account and the default site is displayed

Alternative flows:A4.1: If the password inserted is incorrect, the Wrong credentials message isdisplayed

Name: Log out of an accountIntro: Log the User out of the accountActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an logged inPost-condition: Admin/User is logged out of the accountBasic Flow:

1. The Admin/User clicks Log out field in the menu2.

The Admin/User is logged out of his account

Name: Add announcementIntro: The Admin/User adds an announcementActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the systemPost-condition: Admin/User is logged inBasic Flow:

1.

The Admin/User clicks Add new Item buttona. A dialog box appears2. The Admin/User enters the Title in the title field3. The Admin/User enters the Description in the description field 4. The Admin/User enters the Expire Date in the expire date field 5. The Admin/User choses the Department in the department box6. The Admin/User enters the Job Title in the job title field 7. The Admin/User clicks the Save Button and the announcement is added.

a. Dialog box disappearAlternative flows:A2.1: If the Title is not entered the You must specif y a value for thi srequi red field is displayed


40/65



40

Name: Add Company NewsIntro: The Admin/User adds newsActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged inBasic Flow:

1. The Admin/User clicks Add new Item buttona. A dialog box appears.

2. The Admin/User enters the Tile in the title field 3. The Admin/User enters the Body in the body field

4.

The Admin/User clicks the Save Button and the news is added.a. Dialog box disappear

Alternative flows:A2.1: If the Title is not entered the You must specif y a value for thi srequi red field is displayed

Name: Add InformationIntro: The Admin/User adds informationActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registered

on the systemPost-condition: Admin/User is logged inBasic Flow:

1. The Admin/User clicks Add new Itembuttona. A dialog box appears

2. The Admin/User enters the Tile in the title field 3. The Admin/User enters the Body in the body field4. The Admin/User clicks the Save Button and the news is added.

a. Dialog box disappearAlternative flows:A2.1: If the Titleis not entered the You must specif y a value for thi srequi red field is displayed.


41/65



41

Name: Add DiscussionIntro: The Admin/User adds discussionActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User clicks Add new Item button.a. A dialog box appears.

2. The Admin/User enters the Subject in the title field3. The Admin/User enters the Body in the bodyfield

4.

The Admin/User clicks the Save Button and the news is added.a. Dialog box disappear

Alternative flows:A2.1: If the Subject is not entered the You must specif y a value for thi srequi red field is displayed.

Name: View Quick LinksIntro: The Admin/User View the linkActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User clicks Quick Link linka. New Window appears

Name: View DepartmentIntro: The Admin/User enters a new departmentActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registered

on the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User choses one departmenta. New site appears


42/65



42

Name: Delete AnnouncementIntro: The Admin/User deletes announcementActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User chooses an announcement in the check box.2. The Admin/User selects from the drop down menu delete.3. The announcement is deleted.

Name: Delete Company NewsIntro: The Admin/User deletes a newsActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User chooses news in the check box.2. The Admin/User selects from the drop down box menu delete.3. The news is deleted.

Name: Delete InformationIntro: The Admin/User deletes informationActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User chooses information in the check box.

2.

The Admin/User selects from the drop box down menu delete.3. The information is deleted.


43/65



43

Name: Delete DiscussionIntro: The Admin/User deletes discussionActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User chooses discussion in the check box.2. The Admin/User selects from the drop down box menu delete.

3.

The discussion is deleted.

Name: Edit AnnouncementIntro: The Admin/User Edits announcementActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User chooses discussion in the check box.

2.

The Admin/User clicks selects from the drop down box edit.a. A dialog box appears.

3. The Admin/User enters makes an edit in the announcement.4. The User clicks save button.

a. Dialog box disappear

Name: Edit Company NewsIntro: The Admin/User Edit newsActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User chooses news in the check box.2. The Admin/User clicks selects from the drop down box edit.

a. A dialog box appears.3. The Admin/User enters makes an edit in the news.4. The User clicks save button.



44/65



44

Name: Edit InformationIntro: The Admin/User Edit informationActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User chooses information in the check box.2. The Admin/User clicks selects from the drop down box edit.

a.

A dialog box appears.3. The Admin/User enters makes an edit in the information.4. The User clicks save button.


Name: Edit DiscussionIntro: The Admin/User Edit discussionActor: Admin/UserPre-condition: The SharePoint Site has been started and the Admin/User has an account registeredon the system.Post-condition: Admin/User is logged in.Basic Flow:

1. The Admin/User chooses discussion in the check box.2. The Admin/User clicks selects from the drop down box edit.

a. A dialog box appears.3. The Admin/User enters makes an edit in the discussion.4. The User clicks save button.



45/65



45

Name: Add PostIntro: The user adds post

Actor: Admin/UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User clicks Add new Item buttona. A dialog box appears

2. The User enters the Title in the text field3. The User enters the Body in the text field 4. The User adds Category5. The User choses when published

6.

The User clicks the Publish and the post is added.a. Dialog box disappear

Alternative flows:A2.1: If the Title is not entered the You must specif y a value for thi s required fi eld is

displayedA5.1: If the Published is not entered the You must specif y a value for this requir ed fi eld isdisplayed

Name: Edit PostIntro: The user edit postActor: UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User choses a post2. The user choses from the drop down menu Edit

a. A dialog box appears3. The User edit the post4. The User clicks the Publish and the post is edited.

a.

Dialog box disappear


46/65



46

Name: Delete PostIntro: The user deletes post

Actor: UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User choses a post2. The user choses from the drop down menu Delete

a. A dialog box appears3. The User clicks the Ok button and the post is deleted.


Name: Add CategoryIntro: The user adds categoryActor: Admin/UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User clicks Add new Item buttona. A dialog box appears

2.

The User enters the Title in the text field3.

The User clicks the Save button and thecategory is added.a. Dialog box disappear

Name: Edit CategoryIntro: The user edit categoryActor: UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged in

Basic Flow:1. The User choses a Category2. The user choses from the drop down menu Edit

a. A dialog box appears3. The User edit the category4. The User clicks the Save button and the category is edited.



47/65



47

Name: Delete CategoryIntro: The user deletes category


1. The User choses a category2. The user choses from the drop down menu Delete

a. A dialog box appears3. The User clicks the Ok button and the category is deleted.


Name: Add CommentIntro: The user adds a comment to the a blogActor: UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User clicks Comment buttona. A new page appears

2.

The User enters the Title in the text field3.

The User enters the Body in the text field 4. The User clicks the Submit Comment button and the comment is submitted.

Alternative flows:A3.1: If the Body is not entered the You must specify a value for this required fi eld is

displayed


48/65



48

Name: Edit CommentIntro: The user edit comment


1. The User choses a comment2. The user choses from the drop down menu Edit

a. A dialog box appears3. The User edits the comment4. The User clicks the Submit Comment button and the comment is edited.


Name: Delete CommentIntro: The user deletes commentActor: UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User choses a comment

2.

The user choses from the drop down menu Deletea.

A dialog box appears3. The User clicks the Ok button and the comment is deleted.


Name: Add DocumentIntro: The user adds documentActor: User

Pre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User clicks the Add new item.a. A dialog box appears

2. The User clicks Browse to browse for a document.3. The User clicks the Ok and the document is added.



49/65



49

Name: Delete DocumentIntro: The user deletes document


1. The User choses a document2. The user choses from the drop down menu Delete

a. A dialog box appears3. The User clicks Ok and document deleted


Name: Add ContactIntro: The user adds contactActor: UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User clicks the Add new item.a. A dialog box appears

2.

The User enters Last Name in the text field.3.

The User enters First Name in the text field.4. The User enters Full Name in the text field. 5. The User enters E-mail Address in the textfield.6. The User enters Company in the text field.7. The User enters Job Title in the text field.8. The User enters Business Phone in the text field. 9. The User enters Home Phone in the text field.10.The User enters Mobile Number in the text field.11.The User enters Fax Number in the text field.12.The User enters Address in the text field.

13.

The User enters City in the text field.14.The User enters State/Province in the text field.15.The User enters ZIP/Postal Code in the text field. 16.The User enters Country/Region in the text field.17.The User enters Web Page in the text field. 18.The User enters Notes in the text field.19.The User clicks the Save button and the contact is added.

a. Dialog box disappearAlternative flows:A2.1: If the Last Name is not entered the You must specif y a value for this required fi eld is

displayed


50/65



50

Name: Edit ContactIntro: The user edit contact


1. The User choses a contact2. The user choses from the drop down menu Edit

a. A dialog box appears3. The User edits the contact4. The User clicks the Save button and the contact is edited.


Name: Delete ContactIntro: The user deletes contactActor: UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User choses a contact

2.

The user choses from the drop down menu Deletea.

A dialog box appears3. The User clicks Ok and contact is deleted


Name: Add Event to CalendarIntro: The user adds an eventActor: UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystem

Post-condition: User is logged inBasic Flow:

1. The User clicks the Add button.a. A dialog box appears

2. The User enters Title in the text field.3. The User enters Location in the text field.4. The User choses Start Time.5. The User choses End Time.6. The User enters Description in the text field.7. The User choses Category.8. The User checks the All Day Event box if needed.


51/65



51

9. The User checks Recurrence box if needed.10.The User checks Workspace box if needed.11.The User clicks the Save button and the event is added.


Alternative flows:A2.1: If the Title is not entered the You must specif y a value for thi s required fi eld is

displayedA4.1: If the Start Time is not entered the You must specif y a value for this required fi eld is

displayedA5.1: If the End Time is not entered the You must specif y a value for thi s requir ed fi eld is

displayed

Name: Edit EventIntro: The user edit the eventActor: UserPre-condition: The SharePoint Site has been started and the user has an account registered on thesystemPost-condition: User is logged inBasic Flow:

1. The User choses an event2. The user double clicks the event

a. A dialog box appears3. The User clicks the Edit button4.

The user edit the event5. The User clicks the Save button and the event is edited.



52/65



52

APPENDIX B

Web performance test of the Main Site.

This is the result of our Performance test in URL of the Main Site.

System testing

Case Description Expectedresult T/FC1 Log in to the system Main site will appear. TC2 Sign out from the system Log in page will appear TC3 Clicking one of the

departments in the main siteNew site will appear for thechosen department.

T

C4 Add Announcement Dialog box will appear; whereuser can fell the fields andclick save, dialog boxdisappear.

T

C5 Edit Announcement Dialog box will appear; whereuser can edit the fields andclick save, dialog boxdisappear.

T

C6 Delete Announcement Dialog box will appear; whereuser can click Ok, dialog boxdisappear.

T

C7 Add Company News Dialog box will appear; where T


53/65



53

user can fell the fields andclick save, dialog boxdisappear.

C8 Edit Company News Dialog box will appear; where

user can edit the fields andclick save, dialog boxdisappear.

T

C9 Delete Company News Dialog box will appear; whereuser can click Ok, dialog boxdisappear.

T

C10 Add Information Dialog box will appear; whereuser can fell the fields andclick save, dialog boxdisappear.

T

C11 Edit Information Dialog box will appear; whereuser can edit the fields andclick save, dialog boxdisappear.

T

C12 Delete Information Dialog box will appear; whereuser can click Ok, dialog boxdisappear.

T

C13 Add Discussion Dialog box will appear; whereuser can fell the fields andclick save, dialog boxdisappear.

T

C14 Edit Discussion Dialog box will appear; whereuser can edit the fields andclick save, dialog boxdisappear.

T

C15 Delete Discussion Dialog box will appear; whereuser can click Ok, dialog boxdisappear.

T

C16 View links New site will appear TC17 Add Post to the Company

BlogDialog box will appear; whereuser can fell the fields andclick publish, dialog box

disappear.

T

C18 Edit Post Dialog box will appear; whereuser can edit the fields andclick save, dialog boxdisappear.

T

C19 Delete Post Dialog box will appear; whereuser can click Ok, dialog boxdisappear.

T

C20 Add Category Adds category to the companyBlog

T

C21 Edit Category Dialog box will appear; where T


54/65



54

user can edit the fields andclick save, dialog boxdisappear.

C22 Delete Category Dialog box will appear; where

user can click Ok, dialog boxdisappear.

T

C23 Add Comment Adding comment to theselected Post

T

C24 Edit Comment Dialog box will appear; whereuser can edit the fields andclick save, dialog boxdisappear.

T

C25 Delete Comment Dialog box will appear; whereuser can click Ok, dialog boxdisappear.

T

C26 Share a document Uploading a document to theShared document site

T

C27 Delete Document Deletes the document TC28 Add Contact Dialog box will appear; where

user can fell the fields andclick save, dialog boxdisappear.

T

C29 Edit Contact Dialog box will appear; whereuser can edit the fields andclick save, dialog box

disappear.

T

C30 Delete Contact Dialog box will appear; whereuser can click Ok, dialog boxdisappear.

T

C31 Add Event to Calendar Dialog box will appear; whereuser can fell the fields andclick save, dialog boxdisappear.

T

C32 Edit Event Dialog box will appear; whereuser can edit the fields andclick save, dialog box

disappear.

T

C33 Human Resources Link Site will appear TC34 Sales Link Site will appear TC35 Finance Link Site will appear TC36 Marketing Link Site will appear TC37 I.T Department Link Site will appear T


55/65



55

APPENDIX C

4Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows

7, and Windows Server 2008

Published: May 2010

When you create or customize SharePoint solutions, it is usually best to develop the solution on alocal computer where Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010is installed. This article describes how to install a development environment with MicrosoftSharePoint 2010 and Microsoft Visual Studio 2010. The development environment that you create

by using these instructions will not support SharePoint farm installations, and you should not hostactive production sites with this configuration. These instructions enable you to get started with anenvironment that is specifically suited to developing SharePoint custom solutions.

Step 1: Choose and Preconfigure the Operating System

The requirements for a development environment are less stringent and costly than the requirementsfor a production environment, and the guidelines in this topic do not support a productionenvironment installation. You have several options for preconfiguring the operating system of alocal computer on which you will install SharePoint 2010 for development purposes. The choicethat you make will be determined by factors specific to your organization and environment (such as

budget, the size of your development team, and the operating systems that you and yourorganization are already using).

In any development environment, you should use a computer with an x64-capable CPU, and at least2 gigabytes (GB) of RAM to install and run SharePoint Foundation; 4 GB of RAM is preferable.You should use a computer with 4 GB of RAM to install and run SharePoint Server; 6 GB to 8 GBof RAM is preferable.

Following are the options:

Install SharePoint on Windows Server 2008 Service Pack 2 x64 (or Windows Server 2008R2 x64).

4http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx
http://void%280%29/http://void%280%29/http://void%280%29/


56/65



56

Use Microsoft Hyper-V and install SharePoint on a virtual machine running a WindowsServer 2008 Service Pack 2 x64 (or Windows Server 2008 R2 x64) guest operating system.

Install SharePoint on Windows 7 x64, Windows Vista Service Pack 1 x64, or Windows

Vista Service Pack 2 x64. Use Microsoft Hyper-V and install SharePoint on a virtual machine running a Windows 7

x64, Windows Vista Service Pack 1 x64, or Windows Vista Service Pack 2 x64 guestoperating system.

You must install the WCF Hotfix for Microsoft Windows. The hotfix is available forWindowsServer 2008 Service Pack 2, Windows Vista Service Pack 1, and Windows Vista Service Pack2 and forWindows Server 2008 R2 and Windows 7.

If you are using Windows Vista Service Pack 1 or Windows Vista Service Pack 2, install the hotfix

for ASP.NET on IIS 7.0 (KB967535).This hotfix, which has already been installed on Windows 7,Windows Server 2008 Service Pack 2, and Windows Server 2008 R2, updates the ASP.NETcommon language runtime (CLR) to recognize a new option of optimizing compilations. To takeadvantage of this option, set the optimizeCompilationsproperty of the tag in yourweb.config file to true:

XML

This change significantly improves the initial page load time after you have installed a solution tothe bin directory.

You must install the ADO.NET Data Services Update for .NET Framework 3.5 SP1 to enableREST-based data services. This update is available for Windows Server 2008 Service Pack 2,Windows Vista Service Pack 1, and Windows Vista Service Pack 2 and forWindows Server 2008R2 and Windows 7.

Windows 7 and Windows Vista cannot be used for production deployments of SharePoint 2010. Ifyou use Windows 7 or Windows Vista for your development environment, you should have accessto a test environment that has the same operating system installed as your production environment.

Windows 7 and Windows Vista are recommended only for developer workstations and should beused only for stand-alone installations. You can use a separate Microsoft SQL Server instance, butyou should not configure your installation as a SharePoint farm and you should not host active siteson this configuration.
http://go.microsoft.com/fwlink/?linkID=160770http://go.microsoft.com/fwlink/?linkID=160770http://go.microsoft.com/fwlink/?linkID=160770http://go.microsoft.com/fwlink/?LinkID=166231http://code.msdn.microsoft.com/KB967535http://code.msdn.microsoft.com/KB967535http://go.microsoft.com/fwlink/?LinkID=163519http://go.microsoft.com/fwlink/?LinkID=163519http://go.microsoft.com/fwlink/?LinkId=163524http://go.microsoft.com/fwlink/?LinkId=163524http://go.microsoft.com/fwlink/?LinkId=163524http://go.microsoft.com/fwlink/?LinkId=163524http://go.microsoft.com/fwlink/?LinkID=163519http://go.microsoft.com/fwlink/?LinkID=163519http://code.msdn.microsoft.com/KB967535http://code.msdn.microsoft.com/KB967535http://go.microsoft.com/fwlink/?LinkID=166231http://go.microsoft.com/fwlink/?linkID=160770http://go.microsoft.com/fwlink/?linkID=160770http://go.microsoft.com/fwlink/?linkID=160770


57/65



57

Step 2: Install the Prerequisites for SharePoint 2010

SharePoint requires your operating system to have certain prerequisites installed before installationbegins. For this reason, SharePoint includes a PrerequisiteInstalle.exe tool that installs all of theseprerequisites for you. If your developer workstation is set up with the Windows Server 2008 ServicePack 2 or Windows Server 2008 R2 operating system, you can install SharePoint 2010 by runningthe PrerequisiteInstaller.exe tool (which is included with SharePoint 2010) to install the

prerequisites that SharePoint needs, and then run Setup.exe. However, you cannot usePrerequisiteInstaller.exe on Windows 7 or Windows Vista. For those operating systems, you must

follow the additional instructions in this section.

Because the default installation works only for Windows Server 2008, you must edit oneconfiguration file and install many of the prerequisites manually. You must perform each of thefollowing steps while logged on with an account that has administrator access on the localcomputer. These steps assume that you received the SharePoint 2010 distribution as a singlecompressed executable file namedSharePointFoundation.exefor SharePoint Foundation 2010and setup.exefor SharePoint Server 2010.

To set up a developer workstation

1.

Copy the SharePointFoundation.exe (or setup.exe) installation file to a folder on thecomputer where you are installing SharePoint and doing your development, such as in thefollowing path:

c:\SharePointFiles

2. Extract the installation files by opening a Command Prompt window, and then typing thefollowing command at the directory location of the folder where you copied the installationfiles in the previous step.

For SharePoint Foundation 2010:c:\SharePointFiles\SharePoint /extract:c:\SharePointFiles

For SharePoint Server 2010:

c:\SharePointFiles\OfficeServer /extract:c:\SharePointFiles

3. Using a text editor such as Notepad, open the installation configuration file, config.xml,located in the following


58/65



58

path:c:\SharePointFiles\files\Setup\config.xml

Add this line inside the tag:

XML

4. Save the configuration file.5. Review the complete configuration file. It now looks similar to the following for SharePoint

Foundation 2010. The complete configuration file will be longer for SharePoint Server 2010(and therefore the text below cannot replace the contents of that file), but should use the

same setting for the AllowWindowsClientInstallattribute.

XML

All of the text in this configuration file is case-sensitive. If you do not edit the configurationfile as described in the previous step or if you do not save the configuration file, when youtry to run the installation you see the error message shown in Figure 1.


59/65



59

Figure 1. Setup is unable to proceed error message

6. If you are using Windows Vista Service Pack 1 or Windows Vista Service Pack 2, you mustinstall the following prerequisites:

.NET Framework 3.5 SP1 Windows PowerShell 2.0 Windows Installer 4.5 Redistributable

7. If you are using Windows Vista Service Pack 1, Windows Vista Service Pack 2, orWindows 7, install the following additional prerequisites:

Microsoft FilterPack 2.0. At a command prompt, type the following:

c:\SharePointFiles\PrerequisiteInstallerFiles\FilterPack\Filte

rPack.msi Microsoft Sync Framework SQL Server Native Client Windows Identity Foundation (Windows6.1-KB974405-x64.msu) Chart Controls (this is not required if you are going to install SharePoint Foundation

2010). SQL Server Analysis Services - ADOMD.Net (this is not required if you are going to

install SharePoint Foundation 2010).8. Manually enable each of the required Windows Features. You can do this quickly by

copying and running the following command in a Command Prompt window.
http://www.microsoft.com/downloads/details.aspx?FamilyID=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=enhttp://support.microsoft.com/kb/968929http://www.microsoft.com/downloads/details.aspx?FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4http://go.microsoft.com/fwlink/?LinkID=141237http://go.microsoft.com/fwlink/?LinkId=123718http://support.microsoft.com/kb/974405http://go.microsoft.com/fwlink/?LinkID=122517http://download.microsoft.com/download/A/D/0/AD021EF1-9CBC-4D11-AB51-6A65019D4706/SQLSERVER2008_ASADOMD10.msihttp://download.microsoft.com/download/A/D/0/AD021EF1-9CBC-4D11-AB51-6A65019D4706/SQLSERVER2008_ASADOMD10.msihttp://go.microsoft.com/fwlink/?LinkID=122517http://support.microsoft.com/kb/974405http://go.microsoft.com/fwlink/?LinkId=123718http://go.microsoft.com/fwlink/?LinkID=141237http://www.microsoft.com/downloads/details.aspx?FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4http://support.microsoft.com/kb/968929http://www.microsoft.com/downloads/details.aspx?FamilyID=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en


60/65



60

9.start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServer;IIS-

CommonHttpFeatures;^

10.

IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-

HttpErrors;^

11.

IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility;^

12. IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-HealthAndDiagnostics;^

13.

IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-

HttpTracing;IIS-CustomLogging;IIS-ManagementScriptingTools;^

14.

IIS-Security;IIS-BasicAuthentication;IIS-WindowsAuthentication;IIS-DigestAuthentication;^

15. IIS-RequestFiltering;IIS-Performance;IIS-

HttpCompressionStatic;IIS-HttpCompressionDynamic;^

16.

IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-

IIS6ManagementCompatibility;^

17. IIS-Metabase;IIS-WMICompatibility;WAS-

WindowsActivationService;WAS-ProcessModel;^

18. WAS-NetFxEnvironment;WAS-ConfigurationAPI;WCF-HTTP-Activation;^

19. WCF-NonHTTP-Activation

20.

Verify that the required Windows Features are enabled. The command in the previous stepenables all of the required features in the Internet Information Servicessection ofthe Windows Features dialog box (which you can access through the Programssectionin Control Panel). Use Figure 2 and Figure 3 to check that you have enabled all of therequired Windows Features. If any features are missing in your operating system, return tothe Internet Information Servicessection of the Windows Featuresdialog box and enablethem.


61/65



61

21.Figure 2. First part of Windows Features list from Windows 7


62/65



62

22.Figure 3. Second part of Windows Features list from Windows 7

23.Restart your computer to complete the changes that you made to Windows Features.

Step 3: Install SharePoint 2010

1. To install SharePoint Server 2010 or SharePoint Foundation 2010, open a Command Promptwindow, and then type the following at the command prompt:

2.

c:\SharePointFiles\Setup.exe3. Accept the Microsoft Software License Terms.4. On the Choose the installation you wantpage, click Standaloneto install everything on

one developer workstation.


63/65



63

Figure 4. Installation type choice

5.

If any errors occur in the installation, review the log file. To find the log file, open aCommand Prompt window, and then type the following commands at the command prompt.The log file is displayed at the end of the directory listing.

6.cd %temp%

7.

dir /od *.log

7/23/2019 Bachelor s Project Report Fi