Very basic Java Script which require once in awhile in the world of ASP.NET.

I came across the situation where requirement was to post form to basic ASP page from asp.net page. That can be done by using PostBackUrl property available in Button control. Now that is simple but PostBackUrl will post entire ASP.NET form and extra data will be posted.

Complexity in requirement was that form should be posted to asp page to new window. I tried to find a lot to post data to new window using asp.net button control and PostBackUrl property. If you find please let me know. Then I had to write Java Script.

Ok. Now here is code after lots of text and description.

//Create form

function createForm(formName, actionURL, target, method)

{

    var oForm = document.createElement("form");

    oForm.name = formName; //Form name

    oForm.id = formName; // Form ID

    oForm.action = actionURL; // URL to post back

    oForm.target = target; // This is important. Use “_blank” if you wish to post back to new window

    oForm.method = method; // Method GET or POST

    return oForm;

}

//Create input fields

function createInputField(name, value, type)

{

    var oField = document.createElement("input");

    oField.name = name;

    oField.id = name;

    oField.value = value;

    oField.type = type; // Type normally “hidden”

    return oField;

}

//Append Field to form

function appendField(oForm, oField)

{

    oForm.appendChild(oField);

}

//Here is code to create form, field and submit the form

function submitEligibilityForm(sNewFormAction, Field1Value, Field2Value)

{

    var oForm = createForm("FormName", sNewFormAction,"_blank","POST");

    var oField = createInputField("Field1", Field1Value,"hidden");

    appendField(oForm,oField);

    oField = createInputField("Field2", Field2Value,"hidden");

    appendField(oForm,oField);

    document.appendChild(oForm); //This is required to add form to document

    oForm.submit();

}

Here is HTML code to create and submit the form

<input tyep=”button” text=”click me” onlick=”submitToEligibilityHandoff('submitpage.asp',' Field2Value ', 'Field2Value'); return false;">

Classes and Object used…

·         SPWebApplicationBuilder: Creates an SPWebApplication object, providing default settings for all the required values and allowing the caller to change only those properties that need values different from the default

·         SPFarm: Represents a Windows SharePoint Services farm. To access the current server farm object, you can use members on SPFarm.Local.

·         SPWebApplication: Represents an Internet Information Services (IIS) load-balanced Web application that is installed on the server farm.

·         SPSiteCollection : Represents a collection of SPSite objects, or site collections.

·         SPSite : Represents a collection of sites on a virtual server, including a top-level site and all its subsites. Each SPSite object, or site collection, is represented within an SPSiteCollection object that consists of the collection of all site collections.

·         System.Security.SecureString: Represents text that should be kept confidential. The text is encrypted for privacy when being used, and deleted from computer memory when no longer needed. A SecureString object is similar to a String object in that it has a text value. However, the value of a SecureString object is automatically encrypted, can be modified until your application marks it as read-only, and can be deleted from computer memory by either your application or the .NET Framework garbage collector

Let’s start...

Creating web Application at Port no 2007 ( Assuming user spuser with password Password is present in system administrator group)

SPWebApplicationBuilder webAppBuilder = new SPWebApplicationBuilder(SPFarm.Local);

SPWebApplication newApplication;
int myPort = 2007;

webAppBuilder.Port = myPort;

webAppBuilder.ApplicationPoolId = "site-appol"; // application pool

webAppBuilder.ApplicationPoolUsername = webAppBuilder.DefaultZoneUri.Host + \\spuser;

System.Security.SecureString password = new System.Security.SecureString();               

string strName = "Password";               

char[] pass = strName.ToCharArray();               

foreach (char c in pass)               

    password.AppendChar(c);              

webAppBuilder.ApplicationPoolPassword = password;

webAppBuilder.CreateNewDatabase = true; // Create new database           

webAppBuilder.DatabaseName = "wss_site2007_content";    // database name           

webAppBuilder.DatabaseServer = webAppBuilder.DefaultZoneUri.Host;  //Host name/computer name          

webAppBuilder.UseNTLMExclusively = true;  // Use NTLM authentication

newApplication = webAppBuilder.Create(); // Create new web application
newApplication.Provision();           //Provision it into web farm    

Creating site Collection at root level with Blank site template

SPSite mySiteCollection = newApplication.Sites.Add("/",                       //Root

"Cgosite",              // site title

 "Conchango.com",             //description

1033,                         //language

"STS#1",                //Blank site template  

webAppBuilder.ApplicationPoolUsername, // Site owner

"Name",                 // Name

"name@name.com"); //Email

Creating web

mySiteCollection.AllWebs.Add("/webname");

Activating publishing feature at site collection
mySiteCollection.Features.Add(SPFarm.Local.FeatureDefinitions["PublishingSite"].Id);

SPFarm.Local.FeatureDefinitions["PublishingSite"].Provision()

Close Site Collection
mySiteCollection.Close();

You can reuse ASP.NET Web Parts in your MOSS Web Site by exporting them to create .webpart files, which are XML files that contain details about your Web Part. To enable export functinality you need to do some modifications to your Web Part code and your configuration settings.

After you have a .webpart file, you can import it into any MOSS Web Site.

Step 1: To export an ASP.NET Web Part

1.    In your Web Part code, set the ExportMode property to allow properties to be exported. In the following code, we set the value to All, which allows sensitive properties to be exported.
this.ExportMode = WebPartExportMode.All;

2.    Modify the <system.web> section of the web.config file as follows:
<system.web> <webParts enableExport ="true"/> </system.web>

3.    From the Web Part menu, choose Export to create a .webpart file you can import into a Windows SharePoint Services Web Part Page.
Save file on Disk. Let’s say file name is mywebpart.webpart Please not you may get some security warning about properties set for the Web Part. Reset properties if you do not want this values to be exported.

Step 2: To import a mywebpart.webpart file into Windows SharePoint Services

1.    Place the assembly for your Web Part in the bin or the global assembly cache.

If you place your assembly in the global assembly cache, your assembly must be strong named and run with full trust code permissions by default. The Web Part is available to all Web applications.

If you place your assembly in the bin, you do not have full trust code permissions when your Web Part executes. Because the permissions for the bin directory are very low by default, for this add following code into AssemblyInfo.cs file of your web part project.
[assembly: System.Security.AllowPartiallyTrustedCallers]

2.    Add the Web Part to the Safe Controls list in your web.config file, for example:
<SafeControl   Assembly="MyWebPart"   Namespace="MyWebParts"   TypeName="*"    Safe="True"/>

3.    In Design mode, select Add a web part. At the bottom of the Add Web Parts dialog box, click Advanced Web Part gallery and options.

4.    On the Add Web Parts pane, select Browse ->Import menu and then navigate to the .webpart file you created in the preceding procedure.

5.    Click Upload and your Web Part appears in the list of Uploaded Web Parts.

6.    Drag it into a Web Part zone on the page and you should see the same Web Part as on your ASP.NET page.