Stone Coast Web Design's Weblog

Imports System
Imports System.Data
Imports System.Data.SqlClient
Imports System.Web.Configuration
Imports System.Collections.Generic

Public Class AwesomeDataLayer
    Private Shared ReadOnly _connectionString As String

Private Sub Page_Load()
        lblMovieTitle.Text = GetMovieTitle().ToString()
End Sub

       Public Shared Function GetMovieTitle() As String
        Dim result As String = String.Empty
        Dim con As New SqlConnection(_connectionString)
        Dim cmd As New SqlCommand("GetMovieTitle", con)
        cmd.CommandType = CommandType.StoredProcedure
        Using con
            con.Open()
            Dim reader As SqlDataReader = cmd.ExecuteReader()
            If reader.Read() Then
                result = CType(reader("Title"), String)
            End If
        End Using
        Return result
    End Function

    Shared Sub New()
        _connectionString = WebConfigurationManager.ConnectionStrings("MyDatabase").ConnectionString
    End Sub

End Class

I frequently create User Controls in our WSS 3.0 environment use SmartPart to deploy them. 

Below is an example of a user control not using code-behind.

LastBAUserLogin.ascx

<%@ Control Language="VB" ClassName="LastBAUserLogin" %>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.Data.SqlClient" %>
<%@ Import Namespace="System.Web.Configuration" %>
<%@ Import Namespace="System.Web.UI.UserControl" %>

<script runat="server">
</script>

<asp:UpdatePanel ID="MyUpdatePanel" runat="server">
       <ContentTemplate>
       </ContentTemplate>
 </asp:UpdatePanel>

This is an example utilizing code-behind

staff.directory.ascx

<%@ Control Language="VB" AutoEventWireup="false" codeFile="staff.directory.ascx.vb" Inherits="StaffDirectory" %>

<asp:UpdatePanel ID="MyUpdatePanel" runat="server">
      <ContentTemplate>
      </ContentTemplate>
</asp:UpdatePanel>

staff.directory.ascx.vb

Partial Class StaffDirectory
Inherits System.Web.UI.UserControl

End Class

You may see this error - more than once - when working with your Microsoft Office SharePoint Server (MOSS) 2007 or WSS 3.0 deployment. This often happens after you have applied an upgrade to an existing deployment. You may begin to see a lot of these errors pop up in the SYSTEM event log a:

Event Type:    Error
Event Source:    DCOM
Event Category:    None
Event ID:    10016
Date:        7/1/2008
Time:        9:49:50 AM
User:        NT AUTHORITY\NETWORK SERVICE
Computer:    TCLPRODAPP1
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20).  This security permission can be modified using the Component Services administrative tool

The error CLSID is followed by a class ID for the DCOM+ application that the service account trying to activate that application does not have permission to activate it.

This is the fix that worked for us.

Copy the GUID following the CLSID above, and Start-->Run-->regedit

Edit-->Find and paste in the GUID. It'll stop at the application entry - and you will want to note the application name on the right side pane. In this example, it was the IIS WAMREG admin service that popped up.

Now, open Component Services (typically, from the server - Start-->Administrative Tools-->Component Services), expand Component Services, Computers, My Computer, DCOM Config. Scroll down and find the application (IIS WAMREG in this case). Right-Click-->Properties and select the Security tab. You'll have some options here - the first block Launch and Activation Permissions - ensure that the Customize radio button is selected, and click Edit. Now, add your service account - giving it launch and activate - and in some requirements - remote launch / activate permission.

Restart IIS.

This site from Microsoft has some great T-SQL examples: http://code.msdn.microsoft.com/SQLExamples

I've been having trouble getting WSS to index certain documents and working correctly and this article was helpful.

http://www.wrox.com/WileyCDA/Section/id-305250.html

How do I move WSS 3.0 for "Windows Internal Database" (the embedded version of SQL Server 2005 Express) to the full SQL Server 2005?

Description:

This text was written by Jim Sykora in a public newsgroup and he has very kindly allowed me to re-produce it here.
Many thanks, Jim.
-------
This scenario involves moving your WSS 3.0 sites from Windows Internal Database to Microsoft SQL 2005 (doesn't really matter whether it's local or remote to the main WSS server instance).

1. First Fully backup your current WSS Content databases. I've found no way to move config databases, and from my testing there seems to be little reason to do so.
a. Utilize stsadm.exe from a cmd prompt to back up your entire Sharepoint farm:
stsadm.exe -o backup -url http:// -filename C:\SPBackups\FullFarmBackup.dat
(you may want to change the path the backup file is stored depending on your situation)

b. Verify the backup is complete and browse to the location the backup file is stored to verify it exists and is of a reasonable size.

2. Uninstall WSS 3.0 from Add/Remote Programs Control Panel

3. *IMPORTANT* Remove Windows Internal Database -
http://support.microsoft.com/kb/920277
If you were utilizing a single-server, basic WSS 3.0 installation and uninstall it, it will leave behind the Windows Internal Database, which will cause any new installations of WSS 3.0 to have issues.

4. Reboot the server to finish up any uninstall scripts.

5. Make sure your SQL 2005 database is prepped per the instructions for installing a WSS 3.0 Server Farm and then install using the steps for a server farm (even if you'll only be installing on a single server).
a.
http://technet2.microsoft.com/WindowsServer/WSS/en/library/89e4c579-5720-45e
0-917e-abeb95266c3e1033.mspx

b.
http://technet2.microsoft.com/windowsserver/WSS/en/library/1f505e96-60e2-41a
c-bf5d-9739105f047c1033.mspx?mfr=true

6. Once everything is installed and you're using the SharePoint Products and Technologies Configuration Wizard to configure sharepoint make sure to point it to your existing SQL server as you go through the steps.

7. Upon completion of the wizard use WSS 3.0 Central Administration page to configure your basic settings such as Incoming and outgoing email settings, logging, search server, etc.

8. In Central Administration->Application Management choose "Create or Extend Web Application" to create your IIS instance. Follow the standard steps here.

9. In Central Administration->Content Databases choose "Add a content database" and use your SQL server. Don't forget to select your search server that you set up earlier. This will create an empty content
database which we will restore our site from step 1 to.

10. Open a command prompt again. Use stsadm.exe to restore your site farm:
ststadm.exe -o restore -url http:// -filename C:\SPBackups\FullFarmBackup.dat
This step will take a little bit, but should say Operation Completed Successfully at the end. You should now be able to access your sharepoint site again using the new SQL server database location.

This should also work as a disaster recovery process starting at step 2 being that you should have daily or weekly scheduled sharepoint backups using stsadm (and at least monthly SQL database backups to help with SQL performance and log management).

Later: Boris Gomiunik has a blog item on the way he did this here -

http://webborg.blogspot.com/2007/06/reinstalling-sharepoint-wss3-to-run.html

My design skills are terrible so I often look for templates or "borrow" other people's design ideas. One of the better sites I've found for templates is http://www.opendesigns.org/

This is based on Matt Beserth's article, Modifying Data with the ListView's EditItemTemplate. 

Here is my own example.

This is a simple login user control used to demonstrate how to expose (get and set) the properties associated with the control. Here is a working demo.

** LoginUserControl.ascx **

<script language="VB" runat="server">

  Public BackColor As String = "white"

  Public Property Login As String
    Get
      Return txtLogin.Text
    End Get
    Set
      txtLogin.Text = Value
    End Set
  End Property

  Public Property Password As String
    Get
      Return txtPassword.Text
    End Get
    Set
      txtPassword.Text = Value
    End Set
  End Property
  
  Public Property Status As String
  Get
      Return lblStatus.Text
  End Get
  Set
      lblStatus.Text = Value
  End Set
  End Property

</script>

<table style="background-color:<%=BackColor%>;font: 10pt verdana;border-width:1;border-style:solid;border-color:black;" cellspacing=15>
  <tr>
    <td><b>Login: </b></td>
    <td><ASP:TextBox id="txtLogin" runat="server"/></td>
  </tr>
  <tr>
    <td><b>Password: </b></td>
    <td><ASP:TextBox id="txtPassword" TextMode="Password" runat="server"/></td>
  </tr>
  <tr>
    <td></td>
    <td><ASP:Button Text="Submit" runat="server"/></td>
  </tr>
  <tr>
    <td></td>
    <td><asp:Label id="lblStatus" runat="server"/></td>
  </tr>  
</table>

** LoginControl.aspx **

<%@ Register TagPrefix="MyUserControl" TagName="Login" Src="LoginUserControl.ascx" %>

<html>

<script language="VB" runat="server">
    Sub Page_Load(ByVal Sender As Object, ByVal E As EventArgs)
        If (Page.IsPostBack) Then
            MyLabel.Text &= "The UserId is " & MyLogin.Login & "<br>"
            MyLabel.Text &= "The Password is " & MyLogin.Password & "<br>"
            MyLogin.Status = "Hello world"
        End If
    End Sub
</script>

<body style="font: 10pt verdana">
  <h3>A Login User Control</h3>

  <form runat="server">
    <MyUserControl:Login id="MyLogin" UserId="John Doe" Password="Secret" BackColor="beige" runat="server"/>
  </form>
  <asp:Label id="MyLabel" runat="server"/>
</body>
</html>

You can expose events from a user control.  After you expose the event, you can handle the event in the page that contains the user control. Exposing events is useful when you need to pass information up to the containing page.  In this example, we create a custom tab strip with a user control. When a user clicks a tab, the content is changed. 

The TabStrip control exposes an event named TabClick. This event is raised in the dlstTabStrip_SelectedIndexChanged() event handler when a tab is clicked.

Here is a working demo.

** TabStripUserControl.ascx **

<%@ Control Language="VB" ClassName="TabStrip" %>
<%@ Import Namespace="System.Collections.Generic" %>
<script runat="server">
 
    Public Event TabClick As EventHandler
 
    ''' <summary>
    ''' The index of the selected tab
    ''' </summary>
    Public ReadOnly Property SelectedIndex() As Integer
        Get
            Return dlstTabStrip.SelectedIndex
        End Get
    End Property
 
    ''' <summary>
    ''' Create the tabs
    ''' </summary>
    Private Sub Page_Load()
        If Not Page.IsPostBack Then
            ' Create the tabs
            Dim tabs As New List(Of String)()
            tabs.Add("Products")
            tabs.Add("Services")
            tabs.Add("About")
 
            ' Bind tabs to the DataList
            dlstTabStrip.DataSource = tabs
            dlstTabStrip.DataBind()
 
            ' Select first tab
            dlstTabStrip.SelectedIndex = 0
        End If
    End Sub
 
    ''' <summary>
    ''' This method executes when a user clicks a tab
    ''' </summary>
    Protected Sub dlstTabStrip_SelectedIndexChanged(ByVal sender As Object, ByVal e As EventArgs)
        RaiseEvent TabClick(Me, EventArgs.Empty)
    End Sub

</script>

<asp:DataList   
    id="dlstTabStrip"
    RepeatDirection="Horizontal"
    OnSelectedIndexChanged="dlstTabStrip_SelectedIndexChanged"
    CssClass="tabs"
    ItemStyle-CssClass="tab"
    SelectedItemStyle-CssClass="selectedTab"
    Runat="server">
    <ItemTemplate>
    <asp:LinkButton
        id="lnkTab"
        Text='<%# Container.DataItem %>'
        CommandName="Select"
        Runat="server" />
    </ItemTemplate>
</asp:DataList> 

** TabStrip.aspx **

<%@ Page Language="VB" %>
<%@ Register TagPrefix="user" TagName="TabStrip" Src="TabStripUserControl.ascx" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<script runat="server">
 
    Protected Sub TabStrip1_TabClick(ByVal sender As Object, ByVal e As EventArgs)
        MultiView1.ActiveViewIndex = TabStrip1.SelectedIndex
    End Sub
</script>
<html xmlns="http://www.w3.org/1999/xhtml" >
<head id="Head1" runat="server">
    <style type="text/css">
        html
        {
            background-color:silver;
            font:14px Georgia,Serif;
        }
        .tabs a
        {
            color:blue;
            text-decoration:none;
            font:14px Arial,Sans-Serif;            
        }
        .tab
        {
            background-color:#eeeeee;
            padding:5px;
            border:Solid 1px black;
            border-bottom:none;
        }
        .selectedTab
        {
            background-color:white;
            padding:5px;
            border:Solid 1px black;
            border-bottom:none;
        }
        .views
        {
            background-color:white;
            width:400px;
            border:Solid 1px black;
            padding:10px;
        }
    </style>
    <title>Show TabStrip</title>
</head>
<body>
    <form id="form1" runat="server">
    <div>
    
    <user:TabStrip
        ID="TabStrip1"
        OnTabClick="TabStrip1_TabClick" 
        Runat="Server" />
        
    <div class="views">
    <asp:MultiView
        id="MultiView1"
        ActiveViewIndex="0"
        Runat="server">
        <asp:View ID="Products" runat="server">
            <h1>Products</h1>
            We sell a variety of useful products...
        </asp:View>
        <asp:View ID="Services" runat="server">
            <h1>Services</h1>
            We offer a number of services...
        </asp:View>
        <asp:View ID="About" runat="server">
            <h1>About</h1>
            We were the first company to offer products and services...
        </asp:View>
    </asp:MultiView>
    </div>
        
    </div>
    </form>
</body>
</html>