Your SlideShare is downloading. ×
Build Database Applications for SharePoint!
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Build Database Applications for SharePoint!

651

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
651
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • These days, with everyone under pressure to do more with less and to make shorter and shorter schedules, application generation offers a new option.
  • These days, with everyone under pressure to do more with less and to make shorter and shorter schedules, application generation offers a new option.
  • These days, with everyone under pressure to do more with less and to make shorter and shorter schedules, application generation offers a new option.
  • Transcript

    • 1. 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. 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
    • 4. 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: Site1 Site2 Groups: group1 group2 group3 Site Collection 2 (Site) URL: spserver:80/sc2 Webs: Site1 Site2a Groups: group1 group2 group5 Web Application 2 ID={AD34-… -2222} Site Collection 1 (Site) URL: WA2/sc1 Webs: Site1 Site2 Groups: group1 group2 group3 Site Collection 3 (Site) URL: WA2/sc3 Webs: Site1 Site2a Groups: group1 group2 group5 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:WindowsAssembly 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 Content DB 1 Content DB 2 Server 2 Content DB 3 Services DB1 Server 3 Apps DB 1 Content DB 4 SharePoint Farm (SPFarm_admin) Web Application1 (wa1_admin)
      • Site collection1
      • Group1
      • Group2
      • Group3
      • -Group4
      Web Application2 (wa2_admin)
      • Site collection2
      • Group1
      • Group2
      • Site collection
      • Group1
      • Group2
      • Group3
      • -Group4
      • Site collection3
      • Group1
      • Group2
      • Group3
      Web Application3 (wa3_admin)
      • Site collection1
      • Group1
      • Group2
      • Group3
      • -Group4
      • Site collection3
      • Group1
      • Group2
      • Group3
      • -Group4
      • Site collection2
      • Group1
      • Group2
      • Group3
      • -Group4
      Web Application4 (wa4_admin) Web Application5 (wa5_admin)
      • Site collection1
      • Group1
      • Group2
      • Group3
      • -Group4
      • Site collection
      • Group1
      • Group2
      • Group3
      • -Group4
      • Site collection2
      • Group1
      • Group2
      • Group3
      • -Group4
    • 18. IIS Application Pools: WA1_AppPool (wa1_admin) WA2_AppPool wa2_admin WA3_AppPool wa3_admin Central_Admin_AppPool (SpFarm_admin) C:InetpubwwwrootwssVirtualDirectories 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 FilesCommon Files Microsoft SharedWeb Server Extensions12TEMPLATE LAYOUTS MyApp1 MyApp2 MyApp3 IIS C:InetpubwwwrootwssVirtualDirectories C:Program FilesCommon Files Microsoft SharedWeb Server Extensions12TEMPLATE LAYOUTS MyApp4 MyApp5 MyApp6 _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?

    ×