Koncept for Netværket Kloge Hoveder Dialog Copyright Kloge Hoveder 2007 Koncept for Netværket Kloge Hoveder Dialog Ragnhild Brox Domæneejer Valdemar Thomsen Webmaster ragnhild.brox@gmail.com & valdemar.thomsen@gmail.com Blogs: http://ragnbrox.blogspot.com & http://valdthom.blogspot.com Redaktion Ragnhild Brox & Valdemar Thomsen

Engagement for dialog Vedvarende dialog med virksomheder Permanent engagement for videndeling Tekniske og sociale kompetencer er vigtige Synlighed via hjemmesider og weblogs Vedvarende dialog-netværk Medlemmerne har lært hinanden at kende, så man bliver god til at give feed-back. Troværdigheden er høj Værktøjer anvendes til gruppe-møder Google-Gruppen er et fælles kalender og aktivitetssted http://groups.google.com/group/Klogehoveder/ Hjemmesider i http://www.klogehoveder.net Weblog (fælles) via http://netvaerketklogehoveder.blogspot.com

Medlemmerne bruger hinanden Copyright Kloge Hoveder 2007 Medlemmerne bruger hinanden Netværket Klogehoveder er et karriere netværk Idéer til markedsføring af kompetencer Web-præsenteret profilliste CV-fil hentning på webside Virksomheds Dialog Gruppen er et særligt netværk som holder kontakt til virksomheder, som ofte mangler dygtige nye medarbejdere. Netnørderne er et netværk af personer som også er aktive i Senior Erhverv Hovedstaden. Her afholdes i ulige uger et fredags fysisk netværkmøde kl 13-15 fra Maj af hver anden Torsdag kl. 17-20 i SEH`s lokaler. KHN afholder virksomhedsdialog-kurser for medlemmer. Redaktion Ragnhild Brox & Valdemar Thomsen

Værktøjer til kompetence-analyse og -præsentation Copyright Kloge Hoveder 2007 Værktøjer til kompetence-analyse og -præsentation Jobdialog-proces Medlemmerne hjælper hinanden med profiler Kompetenceprofilen præsenteres via en webside Sparring omkring innovative idéer. Netværksmøder månedlig med fagligt indhold Coaching omkring særlige iværksætnings tiltag Provider-modellen Personlig coaching via en mentor 70 % less code for common senarios Provider-model: A Contract, interface or abstract class. Example: The Membership-service can be used to store usernames, passwords and so on. It has methods sucj lik CreateUser, ValidateUser, DeleteUser and som on, and these can be extended to use an exiting database, a database not support by our providers and so so. Can also be extended to add new features, such as a required strong password after your taste. Better administration and management, more features, more integrated. Two tools: Admin-tools for administrators, addon to the iis-admin-tool Developers: Managament-API, tool or Web.Config Redaktion Ragnhild Brox & Valdemar Thomsen

Medlemsskab af Netværket Kloge Hoveder Copyright Kloge Hoveder 2007 Medlemsskab af Netværket Kloge Hoveder Medlemsskab 50 kr årligt betalt Februar Mentor- møder Kompetence analytiker Hjemmesiden + 5 egne hjemmesider Personlig Caching Klubaftener hver måned I Nørrebro Bryghus Aktivt Weblog miljø http://netvaerketklogehoveder.blogspot.com Innovations netværk Årligt Strategimøde sammen Med andre Netværk Redaktion Ragnhild Brox & Valdemar Thomsen

Samarbejde på tværs af netværk Copyright Kloge Hoveder 2007 Samarbejde på tværs af netværk Netværket samarbejder med andre Netværk Virksomheds Dialog Gruppen Role Manager Kloge Hoveder Årligt Strategimøde fælles Netværket Østeuropa Database Caching Netnørderne Vi samarbejder med andre aktører m.h.t. fælles faglige møder Providers Nørrebro Bryghus Senior Erhverv Hovedstaden Danske Iværksættere Ejer-leder Forening Redaktion Ragnhild Brox & Valdemar Thomsen

Ragnhild`s hjemmeside Valdemar`s hjemmeside Copyright Kloge Hoveder 2007 Faglige emner til debat på hjemmesider Medlemmerne har egne hjemmesider Ragnhild`s hjemmeside Valdemar`s hjemmeside Klaus`s hjememside Ole`s hjememside Steen`s hjememside Lis`s Hjememside Redaktion Ragnhild Brox & Valdemar Thomsen

Valdemar`s Karriereblog Valdemar`s generationsskifte blog Copyright Kloge Hoveder 2007 Weblogs giver direkte dialog-trafik! Besøg Kloge Hoveders Blog http://netvaerketklogehoveder.blogspot.com/ Ragnhild`s Blog Valdemar Blogger Valdemar`s Karriereblog Valdemar`s generationsskifte blog Tilknyttede netværk blogger også! Microsoft Think About IT Cronberg`s blog SHE Bloggere Technorati Watchlist Børsens Gazeller Redaktion Ragnhild Brox & Valdemar Thomsen

Før demoen… Lidt om værktøjet Copyright Kloge Hoveder 2007 Før demoen… Lidt om værktøjet Indbygget Web Server Kræver ikke IIS Tillader kun requests fra samme maskine Lukkes automatisk med Visual Studio Intellisense overalt HTML, XML… HTML Source Preservation Visual Studio ændrer ikke en linje eller karakter i din kode! Og meget, meget mere 70 % less code for common senarios Provider-model: A Contract, interface or abstract class. Example: The Membership-service can be used to store usernames, passwords and so on. It has methods sucj lik CreateUser, ValidateUser, DeleteUser and som on, and these can be extended to use an exiting database, a database not support by our providers and so so. Can also be extended to add new features, such as a required strong password after your taste. Better administration and management, more features, more integrated. Two tools: Admin-tools for administrators, addon to the iis-admin-tool Developers: Managament-API, tool or Web.Config Redaktion Ragnhild Brox & Valdemar Thomsen

Master Pages Copyright Kloge Hoveder 2007 This demo provides a first look at master pages. Step 1: Open the WhatsNew project in Visual Studio 2005 Step 2: Open Davinci.master in the designer and switch to Design view. Show the audience the layout of the page, including the Image control in the upper left corner and the LinkButtons on the left, and point out the two ContentPlaceHolder controls. Inform the audience that these controls represent areas where content pages--pages that use masters--can plug in content of their own Step 3: Switch to Source view and show the @ Master directive at the top of the page designating this page as a master page. Also show the <asp:ContentPlaceHolder> elements defining content place holders Step 4: Open Davinci.aspx in the designer and switch to Design view. Show that this page fills the top ContentPlaceHolder with text and the bottom ContentPlaceHolder with an image. Point out that the content inherited from the master page is shown in half-color Step 4: Switch to Source view and show the MasterPageFile attribute in the @ Page directive that designates Davinci.master as Davinci.aspx's master page. Also show the <asp:Content> elements encapsulating the page's content Step 6: Run Davinci.aspx so the audience can see how the content from the master page and the content page is merged Step 7: Inform the audience that all the demos you'll be showing in this course use master pages to provide a common look and feel Redaktion Ragnhild Brox & Valdemar Thomsen

Mobility and Localization ASP.NET 2.0 Developer Stack Copyright Kloge Hoveder 2007 ASP.NET Whidbey “Control Buckets” (50+) Security Web Parts Data Navigation ASP.NET Whidbey “Page Framework” Features Master Pages Themes/Skins Compilation Mobility and Localization ASP.NET Whidbey “Building Block” APIs Membership Role Manager Personalization Site maps Database Caching Management Redaktion Ragnhild Brox & Valdemar Thomsen

Navigering Copyright Kloge Hoveder 2007 The following demo demonstrates how to build and use custom providers. The specific example used here is a custom read-only membership provider named XmlMembershipProvider that uses a simple XML file as the membership store. While admittedly contrived (few real-world Web sites would want to use XML files to store membership data), this example is illustrative nonetheless because its simplicity makes it a valuable learning tool. Furthermore, XmlMembershipProvider might indeed be useful for simple Web sites that use forms authentication but have no more than 10 or 20 registered users. Step 1: Open the Providers project in Visual Studio 2005 Step 2: Inform the audience that you'll be demoing a simple Web site that's based on the login controls demo you showed earlier. Rather than use Access or SQL Server as the membership store, however, this one uses a custom provider named XmlMembershipProvider that stores membership data in XML files. XmlMembershipProvider is a read-only provider, meaning it's capable of validating users and retrieving information about them, but it doesn't support user creation, user deletion, password modification, or any actions that would result in modification of the XML membership store. Such tasks must be performed by manually editing the XML file Step 3: Run MembershipInfo.aspx. Note the provider name shown on the page: XmlMembershipProvider. Click the "View MembershipUser Info" link at the bottom of the page Step 4: Log in using the user name "Bob" and password "bob". MembershipUserInfo.aspx appears. Point out that the code in this application is identical to the code in the login control demo. All that changed is the underlying membership provider Step 5: Open Web.config. Show the audience the <membership> element that registers XmlMembershipProvider and makes it the default membership provider. Call attention to the xmlFileName attribute in the <add> element; it identifies the XML file--Users.xml--from which XmlMembershipProvider retrieves membership data Step 6: Open Users.xml to show the site's registered users Step 7: Open Code\XmlMembershipProvider.cs. Explain that this source code file, which is autocompiled by ASP.NET, contains the implementation of the XmlMembershipProvider class Step 8: Walk the audience through the source code for the XmlMembershipProvider class. Key points to highlight include: XmlMembershipProvider derives from System.Web.Security.MembershipProvider, which defines the core features of a membership provider XmlMembershipProvider.Initialize opens the XML file identified by the xmlFileName attribute, parses it, and builds a hash table containing a collection of MembershipUser objects, each representing a registered user. MembershipUser objects stored in the hash table are keyed by user names XmlMembershipProvider.ValidateUser validates a user name and password by extracting from the hash table the MembershipUser object, if any, keyed by the specified user name and comparing the specified password to the MembershipUser object's Comment property. Because the MembershipUser class doesn't provide storage for passwords, XmlMembershipProvider stores passwords in MembershipUser.Comment. If XmlMembershipProvider were used in a real application, you'd want to modify it to read and store encrypted passwords or password hashes (anything other than plaintext) XmlMembershipProvider.GetAllUsers iterates through the hash table and creates a MembershipUserCollection to return to the caller. Each MembershipUser object in the hash table is matched by a MembershipUser object in the MembershipUserCollection XmlMembershipProvider.GetUser uses the user name provided to it to perform a hash table lookup. It returns the MembershipUser object retrieved from the hash table, or null if no such user exists XmlMembershipProvider.GetNumberOfUsersOnline has a trivial implementation that always returns 1. XmlMembershipProvider does not attempt to keep a tally of users online All other XmlMembershipProvider methods throw a NotSupportedByProviderException. Obviously, a full-featured provider would need to implement most if not all of these methods Redaktion Ragnhild Brox & Valdemar Thomsen

Login og sikkerhed Copyright Kloge Hoveder 2007 The following demo demonstrates how to build and use custom providers. The specific example used here is a custom read-only membership provider named XmlMembershipProvider that uses a simple XML file as the membership store. While admittedly contrived (few real-world Web sites would want to use XML files to store membership data), this example is illustrative nonetheless because its simplicity makes it a valuable learning tool. Furthermore, XmlMembershipProvider might indeed be useful for simple Web sites that use forms authentication but have no more than 10 or 20 registered users. Step 1: Open the Providers project in Visual Studio 2005 Step 2: Inform the audience that you'll be demoing a simple Web site that's based on the login controls demo you showed earlier. Rather than use Access or SQL Server as the membership store, however, this one uses a custom provider named XmlMembershipProvider that stores membership data in XML files. XmlMembershipProvider is a read-only provider, meaning it's capable of validating users and retrieving information about them, but it doesn't support user creation, user deletion, password modification, or any actions that would result in modification of the XML membership store. Such tasks must be performed by manually editing the XML file Step 3: Run MembershipInfo.aspx. Note the provider name shown on the page: XmlMembershipProvider. Click the "View MembershipUser Info" link at the bottom of the page Step 4: Log in using the user name "Bob" and password "bob". MembershipUserInfo.aspx appears. Point out that the code in this application is identical to the code in the login control demo. All that changed is the underlying membership provider Step 5: Open Web.config. Show the audience the <membership> element that registers XmlMembershipProvider and makes it the default membership provider. Call attention to the xmlFileName attribute in the <add> element; it identifies the XML file--Users.xml--from which XmlMembershipProvider retrieves membership data Step 6: Open Users.xml to show the site's registered users Step 7: Open Code\XmlMembershipProvider.cs. Explain that this source code file, which is autocompiled by ASP.NET, contains the implementation of the XmlMembershipProvider class Step 8: Walk the audience through the source code for the XmlMembershipProvider class. Key points to highlight include: XmlMembershipProvider derives from System.Web.Security.MembershipProvider, which defines the core features of a membership provider XmlMembershipProvider.Initialize opens the XML file identified by the xmlFileName attribute, parses it, and builds a hash table containing a collection of MembershipUser objects, each representing a registered user. MembershipUser objects stored in the hash table are keyed by user names XmlMembershipProvider.ValidateUser validates a user name and password by extracting from the hash table the MembershipUser object, if any, keyed by the specified user name and comparing the specified password to the MembershipUser object's Comment property. Because the MembershipUser class doesn't provide storage for passwords, XmlMembershipProvider stores passwords in MembershipUser.Comment. If XmlMembershipProvider were used in a real application, you'd want to modify it to read and store encrypted passwords or password hashes (anything other than plaintext) XmlMembershipProvider.GetAllUsers iterates through the hash table and creates a MembershipUserCollection to return to the caller. Each MembershipUser object in the hash table is matched by a MembershipUser object in the MembershipUserCollection XmlMembershipProvider.GetUser uses the user name provided to it to perform a hash table lookup. It returns the MembershipUser object retrieved from the hash table, or null if no such user exists XmlMembershipProvider.GetNumberOfUsersOnline has a trivial implementation that always returns 1. XmlMembershipProvider does not attempt to keep a tally of users online All other XmlMembershipProvider methods throw a NotSupportedByProviderException. Obviously, a full-featured provider would need to implement most if not all of these methods Redaktion Ragnhild Brox & Valdemar Thomsen

Databinding Langt simplere Data source-kontroller Nye datakontroller GridView and DetailsView controls Editering med GridView and DetailsView Caching SQL cache dependencies

Copyright Kloge Hoveder 2007 ASP.NET 1.x Data Binding <asp:DataGrid ID="MyDataGrid" RunAt="server" /> ... <script language="C#" runat="server"> void Page_Load (Object sender, EventArgs e) { SqlConnection connection = new SqlConnection ("server=localhost;database=pubs;integrated security=true"); try { connection.Open (); SqlCommand command = new SqlCommand ("select title_id, titles, price from titles"); MyDataGrid.DataSource = command.ExecuteReader (); MyDataGrid.DataBind (); } finally { connection.Close (); </script> This code snippet demonstrates canonical ASP.NET 1.x data binding. The DataGrid does the rendering, but the developer does the querying of the data source and the binding of the query results to the DataGrid. Redaktion Ragnhild Brox & Valdemar Thomsen

ASP.NET 2.0 Data Binding Declarative data binding – ingen kode Copyright Kloge Hoveder 2007 ASP.NET 2.0 Data Binding Declarative data binding – ingen kode <asp:SqlDataSource ID="Titles" RunAt="server" ConnectionString="server=localhost;database=pubs;integrated security=true" SelectCommand="select title_id, title, price from titles" /> <asp:DataGrid DataSourceID="Titles" RunAt="server" /> This code snippet demonstrates canonical ASP.NET 2.0 data binding. Thanks to SqlDataSource's ability to query a data source and bind to a control, no code is required. In addition to querying databases, SqlDataSource can also update databases. It isn't restricted to SQL Server databases; it can talk to any database for which a managed provider is available. SqlDataSource is part of a new family of data source controls. Another notable member of that family is ObjectDataSource, which enables controls to declaratively data-bind to middle-tier data access components. In case anyone asks, yes, SqlDataSource can call stored procedures and use parameterized queries, and no, connection strings do NOT have to be stored in ASPX files or in plaintext. A new declarative syntax permits the control's ConnectionString property to reference a connection string in the new <connectionStrings> section of Web.config, and the entire <connectionStrings> section (as well as other sections of Web.config) can optionally be encrypted. All this and more will be covered in the data access course module. Redaktion Ragnhild Brox & Valdemar Thomsen

ASP.NET 2.0 Data Binding Declarative data binding – ingen kode Copyright Kloge Hoveder 2007 ASP.NET 2.0 Data Binding Declarative data binding – ingen kode <asp:SqlDataSource ID="Titles" RunAt="server" ConnectionString="server=localhost;database=pubs;integrated security=true" SelectCommand="select title_id, title, price from titles" /> <asp:DataGrid DataSourceID="Titles" RunAt="server" /> This code snippet demonstrates canonical ASP.NET 2.0 data binding. Thanks to SqlDataSource's ability to query a data source and bind to a control, no code is required. In addition to querying databases, SqlDataSource can also update databases. It isn't restricted to SQL Server databases; it can talk to any database for which a managed provider is available. SqlDataSource is part of a new family of data source controls. Another notable member of that family is ObjectDataSource, which enables controls to declaratively data-bind to middle-tier data access components. In case anyone asks, yes, SqlDataSource can call stored procedures and use parameterized queries, and no, connection strings do NOT have to be stored in ASPX files or in plaintext. A new declarative syntax permits the control's ConnectionString property to reference a connection string in the new <connectionStrings> section of Web.config, and the entire <connectionStrings> section (as well as other sections of Web.config) can optionally be encrypted. All this and more will be covered in the data access course module. Redaktion Ragnhild Brox & Valdemar Thomsen

DataSource-kontroller Copyright Kloge Hoveder 2007 DataSource-kontroller Declarative data binding – ingen kode Navn Beskrivelse SqlDataSource Forbinder databundne kontroller til SQL databaser AccessDataSource Forbinder databundne kontroller til Access-databaser XmlDataSource Forbinder databundne kontroller til XML data Data source controls reduce the amount of code you write by replacing code that queries data sources and binds the results to controls with <asp:> tags. In Visual Studio 2005, you can create these tags using drag-and-drop. You can also use the Visual Studio IDE to configure data sources. The first four data source controls listed in this table are introduced in this lecture; the final one (SiteMapDataSource) is introduced in the Site Navigation module since it's a special-purpose control that's specifically designed to interface with site maps. NOTE: Beta 1 contains an additional data source control named DataSetDataSource. That control will be dropped from beta 2 (too much overlap with XmlDataSource), so it isn't mentioned here. ObjectDataSource Forbinder databundne kontroller til objekter SiteMapDataSource Forbinder site navigation-kontroller til site map data Redaktion Ragnhild Brox & Valdemar Thomsen

ObjectDataSource Declarative binding til objekter To-vejs data binding Copyright Kloge Hoveder 2007 ObjectDataSource Declarative binding til objekter Brug data access-komponenter Separer data access kode fra UI-kode To-vejs data binding SelectMethod, InsertMethod, UpdateMethod, og DeleteMethod Mulighed for caching Next to SqlDataSource, ObjectDataSource is probably the data source control that will garner the most attention from developers. Many applications (especially multi-tier applications) isolate logic for talking to databases and other data sources in a data access layer, the goal being to isolate the UI layer from changes that occur to the data source on the back end. ObjectDataSource permits you to practice declarative data binding without sacrificing the ability to use middle-tier data access components to access data sources. The downside to SqlDataSource is that it creates an explicit connection between code in the UI layer and the data on the back end. ObjectDataSource provides a solution to that problem. Redaktion Ragnhild Brox & Valdemar Thomsen

Web-udvikling i Visual Studio Store forbedringer Copyright Kloge Hoveder 2007 Web-udvikling i Visual Studio Store forbedringer FrontPage Server Extensions kræves ikke længere File System, IIS, FTP og FPSE Web Sites Folder-baseret Project System Model Rediger hvor som helst (ingen projekt-filer krævet) Langt bedre ydelse med store web sites Man kan nu re-build’e enkelte sider Fleksible HTML Source Formatting Præcis kontrol over designer generatet HTML Re-formater HTML’en, så den ser ud som du vil Redaktion Ragnhild Brox & Valdemar Thomsen

Web-udvikling i Visual Studio Store forbedringer Copyright Kloge Hoveder 2007 Web-udvikling i Visual Studio Store forbedringer HTML Tag Navigator og Tag Outlining Langt lettere at få overblik over og navigere i komplekse sider XHTML Support Validation Engine kan udvides Real-time validering og HTML-intellisense mens du skriver! Section 508 + WCAG Accessibility Compliance-kontrol Redaktion Ragnhild Brox & Valdemar Thomsen

Desuden Provider-model Lokalisering Kompilerings-model Web parts Copyright Kloge Hoveder 2007 Desuden Provider-model Lokalisering Kompilerings-model Web parts SQL Server Express Opgradering uden problemer Målet er 100% kompatabilitet med ASP.NET 1.0 og 1.1 Kører på IIS5, IIS5.1 og IIS6.0 (ingen OS-opgradering) Redaktion Ragnhild Brox & Valdemar Thomsen

© 2004 Microsoft Corporation. All rights reserved. Copyright Kloge Hoveder 2007 © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Redaktion Ragnhild Brox & Valdemar Thomsen

Web Parts Weather Stocks Web Part Web Part Search Web Part News Copyright Kloge Hoveder 2007 Web Parts Weather Web Part Stocks Web Part Search Web Part News Web Part Calendar Web Part In this example, the page contains two Web Part zones. The zone on the left contains two Web Parts, and the zone on the right contains three. Redaktion Ragnhild Brox & Valdemar Thomsen