build database applications for sharepoint!

Copyright © 2006-2008. Iron Speed Inc. All rights reserved

Designer 301 – Advanced Iron Speed Designer

Moderator: Jill Giampedraglia

Presenter: Razi Mohiuddin

We will start momentarily…

Audio: Dial-in or use Voice over IP

2

Copyright © 2006-2008. Iron Speed® Inc. All rights reserved

Etiquette

Select Audio Mode

Use Telephone: Dial local phone number

Use Speakers: Enable VOIP on your computer

Ask questions at any time via online Q & A facility

Moderator will answer directly, or

We will read aloud and answer

3


Agenda

Iron Speed Designer

Build data-centric SharePoint applications

Q&A

Copyright © 2006-2008. Iron Speed Inc. All rights reserved

Build data-centric SharePoint applications

5


SharePoint Application Why use Iron Speed Designer

Features

Security

Requirements

Deployment

6


Why use Iron Speed Designer?

Speed application development Cut software development costs Reduce testing time Simplify maintenance

Application generation = acceleration

7


What does Iron Speed Designer do?

Business process automation Reporting and tracking applications Workflow and scheduling applications Rapid prototyping

Use Iron Speed Designer for

"I can honestly say that Iron Speed Designer does cut your development time by more than half. … That's how productive I think the tool makes our developers."

— Robert Rivera, Development Manager, Los Angeles County Health Department

8


What does Iron Speed Designer Generate?

ASPX pages C# and Visual Basic code-behind files Data access layer Stored procedures

Iron Speed Designer generates Web applications…

… straight from your database.

9


Features All features work in SharePoint

All page types – Show/Edit Table, Show/Edit/Add

Record, etc.

Multi-level menus

Export & Import

Ajax: Popups, Update Panels, Auto-typeahead

Formulas

Inline or Stored Procedures

Security

Same code model

Everything!

10


Security Can use

SharePoint Groups

Database

SharePoint Groups

Use Web Services or Database

Web Services

No Administrative access to Database required

Requires URLs for all site collections

Database

Direct connection

Can see all web applications at once

11


Security Uses SharePoint Groups as roles

Groups are specific to Site Collection

User role is a pairing of site collection and group

Can be specific to

Web Application / Site Collection / Group

Common to all web applications

Site Collection / Group

12


Web Application 1 ID={1B24-… -1111}

Site Collection 1 (Site)URL:spserver:80/sc1

Webs:Site1Site2

Groups:group1group2group3

Site Collection 2 (Site)URL:spserver:80/sc2

Webs:Site1Site2a


Web Application 2 ID={AD34-… -2222}

Site Collection 1 (Site)URL:WA2/sc1

Webs:Site1Site2


Site Collection 3 (Site)URL:WA2/sc3

Webs:Site1Site2a


Web Application Specific roles examples: {AD34-… -2222}/sc1/group2 {1B24-… -1111}/sc1/group2

Web Application Invariant roles examples:/sc1/group1/sc2/group2

13


Requirements SharePoint 2007, 2010, WSS 3.0 or WSS 4.0

Uses SharePoint theme

Development Machine

Must NOT be a SharePoint / WSS site

Must have Microsoft.SharePoint.DLL in GAC

(can be copied from any SharePoint server)

Drag and drop DLL into C:\Windows\Assembly folder in

Windows Explorer. Automatically registers.

Deployment Server

SharePoint or WSS

No need for Iron Speed Designer

14


Requirements – Application .NET 3.5; VB.NET or C#

SharePoint Inherited Page Style

Microsoft Access not recommended

Have to enable File Operations and OLEDB

Microsoft Access does not work on 64-bit servers

ASP.NET Development Server preferred

Using IIS has image problems

During development, application simulates

SharePoint environment

Simulates SharePoint Master Page

SharePoint security configured, not enabled

15


Deployment Use Deployment Wizard to create WSP

Copying folder does not work

Deployment Wizard

Changes application from simulator to SharePoint

enabled

Creates WSP for installation

16


Deployment Hierarchy Farm

Server

Web Application Site Collection

Site

17


Server 1

ContentDB 1

ContentDB 2

Server 2

ContentDB 3

ServicesDB1

Server 3

AppsDB 1

ContentDB 4

SharePoint Farm (SPFarm_admin)

Web Application1 (wa1_admin)

Site collection1-Group1-Group2-Group3--Group4


Site collection2-Group1-Group2

Site collection-Group1-Group2-Group3--Group4

Site collection3-Group1-Group2-Group3

Web Application3(wa3_admin)







Site collection-Group1-Group2-Group3--Group4


18


IIS

Application Pools:

WA1_AppPool(wa1_admin)

WA2_AppPool wa2_admin

WA3_AppPoolwa3_admin

Central_Admin_AppPool(SpFarm_admin)

C:\Inetpub\wwwroot\wss\VirtualDirectories\

2133

80 \App_GlobalResources \ App_Themes \bin web.config

WA2 \App_GlobalResources \ App_Themes \bin web.config

23713 \App_GlobalResources \ App_Themes \bin web.config

C:\Program Files\Common Files\ Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\

MyApp1MyApp2MyApp3

IIS

C:\Inetpub\wwwroot\wss\VirtualDirectories\ C:\Program Files\Common Files\ Microsoft

Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\

MyApp4MyApp5MyApp6

_layouts

_layouts

_layouts

19


Deployment Steps Create WSP

Copy WSP and Batch files to SharePoint server

Add solution to solution store – by running Batch file

Deploy solution via Central Admin

Activate feature

Updates web.config on the Farm

Activates for whole web application, not just

particular site collection

Navigate to default page to access application

20


Deployment Steps - Updating Updating requires uninstalling and then reinstalling

Uninstall:

Run Remove Solutions Batch file

Uninstalls feature

Retracts the solution

Deletes the solution

Delete the Features folder

Delete the Application folder

Removed shared DLL’s is no longer needed

21


Future Plans Lists

Web Parts

22


Questions?

build database applications for sharepoint!

Technology

sharepoint wss site

site url

sharepoint server

pairing of site collection

deployment server sharepoint

requirements sharepoint

site collection user

sharepoint environment