Thursday, 8 November 2012

Steps by Step for XBAP Application Deployment

Introduction

In this article, I have describe, how to deploy the XBAP Application. Here I have given every steps screen shot and detail of the necessary parameters.

The following are the steps for deploying the XBAP samples.

Step 1. VIRTUAL DIRECTORY CREATION IN IIS

Create a Virtual Directory in local machine with local path. Please use the following steps to do this.

I. Open Internet Information Services (IIS) Manager. (Start -> Run -> inetmgr.exe).
II. Navigate to (Machine name -> Sites -> Default Web Sites).
III. Right click on “Default Web Sites” and select “Add Application option”.

IV. It will open “Add Application” dialog box. From this dialog box, please enter the “Alias” and “Physical Path”. Then Click OK button.

V. It will create a “Virtual directory” with the name of “Sample” to the physical path of “E:\Work\SourceCode\Version\Project\Control”.

Step 2. WORKING SAMPLE APPLICATION WITH VS IDE

We should always work with Admin mode for deploying the XBAP application since we don’t have rights to access IIS in non-admin mode. Open VS IDE in Admin mode.

Step 3. DEPLOYING SAMPLE APPLICATION

I. Open the solution file.

II. Do necessary changes in the application and build it.

III. Once the build get succeeded then open the properties of “Sample” application.

IV. From the properties window, go to Signing tab and make sure that “Sign the ClickOnce manifests” check box is checked. If not, select the certificate key from the Certificate storage.

V. Then navigate to “Security” tab and make sure that “This is a full trust application” radio button is in checked condition. Normally XBAP applications are run within a security sandbox to prevent untrusted applications from controlling local system resources. (E.g. deleting local files). In order to access local file system, port access, bitmap effects, etc., you need to run your application in “Full trust” mode.

VI. After that, select “Publish” tab and enter the publish location (Both local path and internet path where we would like to Run the application) and publish version information.

VII. Before that, make sure that the files needed to include with the application along with the published folder. This can be achieved with help of “Application Files” dialog by clicking the “Application Files” button.

VIII. We need to mention the “Prerequisites” to run our application. This will be provided by using “Prerequisites” dialog.

IX. Then provide the publishing details which will be shown in the main “index.htm” page.

X. Once you complete all above steps, please use publish wizard and publish the sample application.

Step 4. DEPLOYING AN APPLICATION TO THE REMOTE SERVER

I. Since we already given the internet URL while publishing the project application, we need to create a sample virtual directory in “Remote server’s IIS”. It will make URL available over the internet.

II. Then place the sample application’s (XBAP application) files and folder from local machine to the remote server.

Wednesday, 31 October 2012

‘System.Net.WebPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed

In WPF browser application follow given steps to give full trust permission

1. Select project

2. Right click and select properties.

3. Select security tab from left panel.

4. Now select/ check the radio button that says " This is full trust application"

5. Save and run application.

This will solve ur problem of permission on System.Net.WebPermission.

Tuesday, 30 October 2012

WCF Service Hosting :: How to Use Dataset Across

WCF Service

Some times you need to return a set of data from a WCF service and When you are working with ado.net, dataset is the obvious reason you wish at your client side. But passing dataset can make service less interoportable because in that case you are forced to use dataset on your client code. Second point is that dataset might become very bulky as per size of the data grows. Instead, passing dataset we can pass compressed byte array of dataset from WCF service and consume it like a byte array on client end. After Uncompression, either you can convert it into dataset or you can use this XML in any other form you want.

For this, lets first create a WCF service:

[OperationContract]
public byte[] GetEmployee(string BranchId)
{
string sQ = "Select EmpId, EmployeeName from EmployeeMaster";

SqlConnection objConn = new SqlConnection("Data Source=[YourServer];Initial Catalog=[Database];User ID=[UserName];Password=[Password];MultipleActiveResultSets=True");
SqlCommand objCom = new SqlCommand(sQ, objConn);
SqlDataAdapter objDa = new SqlDataAdapter(objCom);
DataSet objDs = new DataSet();
objDa.Fill(objDs);
//Now we'll convert dataset into byte array and compress it using gzStream.
byte[] binaryDataResult = null;
MemoryStream memStream = new MemoryStream();
GZipStream gzStream = new GZipStream(memStream, CompressionMode.Compress);
objDs.WriteXml(gzStream);
binaryDataResult = memStream.ToArray();
gzStream.Close();
memStream.Close();
return binaryDataResult;
}

Here, We are first filling dataset from database then after compression using GZipStream, we are converting it to byte array. At client end we will get this byte array and we’ll again follow these steps in reverse order.

ServiceClient s = new ServiceClient();
byte[] btEmployee = (byte[])s.GetEmployee("0");
if (btEmployee != null)
{
MemoryStream mEmployee = new MemoryStream(btEmployee);
GZipStream gStreamEmployee = new GZipStream(mEmployee, CompressionMode.Decompress);
DataSet objDsEmployee = new DataSet();
objDsEmployee.ReadXml(gStreamEmployee);
gStreamEmployee.Close();
gvEmployee.DataSource = objDsEmployee;
gvEmployee.DataBind();
}

Wednesday, 26 September 2012

bulk data upload at single attempt.

SqlBulkCopy sqslbulksubt = new SqlBulkCopy(con);
sqslbulksubt.DestinationTableName = "advance";
sqslbulksubt.ColumnMappings.Add("policeid", "policeid");
sqslbulksubt.ColumnMappings.Add("Date1","Date1");
sqslbulksubt.ColumnMappings.Add("Date2","Date2");
sqslbulksubt.ColumnMappings.Add("Amount","Amount");
sqslbulksubt.ColumnMappings.Add("permonth","Roateamt");
sqslbulksubt.ColumnMappings.Add("period","period");
sqslbulksubt.ColumnMappings.Add( "iterations","iterations");
sqslbulksubt.ColumnMappings.Add("status", "status");
sqslbulksubt.ColumnMappings.Add("date", "date");
sqslbulksubt.WriteToServer(dt);

Update Trigger (Timestamp)

ALTER TRIGGER [dbo].[Trigger_tbl_Process_Constants] ON dbo.tbl_Process_Constants
FOR UPDATE
AS

begin
UPDATE dbo.tbl_Process_Constants
SET Date_Modified = GETDATE()

end

Result: Its update all rows of a table.

So basically something like:

CREATE TRIGGER [dbo].[Trigger_tbl_Process_Constants] ON dbo.tbl_Process_Constants
    FOR UPDATE
AS
    BEGIN
        UPDATE  dbo.tbl_Process_Constants
        SET     Date_Modified = GETDATE()
        WHERE   keycolumn IN ( SELECT   keycolumn
                               FROM     inserted )
    END

Also - just to avoid recursive trigger calls - (stealing Andras' code)

CREATE TRIGGER [dbo].[Trigger_tbl_Process_Constants] ON dbo.tbl_Process_Constants
    FOR UPDATE
AS
    BEGIN
    IF not(update(Date_Modified))
        BEGIN
            UPDATE  dbo.tbl_Process_Constants
            SET     Date_Modified = GETDATE()
            WHERE   keycolumn IN ( SELECT   keycolumn
                               FROM     inserted )
       END
    END

Sending a mail using Trigger:

update anu_items set items_Amount=400 where items_id=1
exec master..xp_sendmail
@recipients='abc@gmail.com',
@message='Body',
@subject='subject Text'

Tuesday, 25 September 2012

Steps to set Form based authentication (FBA) for SharePoint 2010

1. DOWNLOAD FBA User Management Tool

Go to “C:\Windows\Microsoft.NET\Framework\v2.0.50727”.

2. Open file “aspnet_regsql.exe” (with Run as Administrator).

I. You will get an installation form. Hit “Next” button.

II. Click on “Configure SQL Server for application services” then hit “Next” button.

III. Now provide server name to connect & install new database for Membership. Now hit “Next” button.

IV. Now you get a summary page on which you will get server name & its new database name called “aspnetdb”. Click on “Next” button.

V. Now database has been created. Click on “Finish” button.

3. Install FBA tool.

4. Create a new Site collection (suppose we called it “A”).

5. Extend this site (Suppose we called it “B”).

I. Open Central Administration.

II. Click on Application Management.

III. Click on Manage Web application.

IV. Click on “Site A” & then hit Extend button on ribbon.

1. Click on Create a new IIS web site.

2. Provide name & port number (optional).

3. Provide host header (optional)

4. Select Anonymous Access to –No

5. Use Secured Socket layer – No

6. Check on Enable Windows Authentication. Check On Integrated windows authentication & select “NTLM”.

7. Check Enable Forms Based Authentication. In “ASP.NET Membership provider name” put “SqlMember” & in ASP.NET Role manager name put “SqlRole”.

8. Select – Default Sign in Page.

9. Select Zone.

10. Click OK.

11. After creating this site, Test this site.

6. Make changes in web.config files.

I. Open inetmgr.

II. Explore Site A & take back up of web.config file.

1. Open web.config file.

2. Put this connection string just after configSections>

connectionStrings>

3. Search for entry <PeoplePickerWildcards> & put this entry within this tag.

4.       Search for entry <membership> & < roleManager> replace whole entry with :

<membership defaultProvider="i" userIsOnlineTimeWindow="15" hashAlgorithmType="">
      <providers>
        <clear />
        <add connectionStringName="AspNetSqlMemberShipProvider" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" passwordAttemptWindow="10" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" name="SqlMember" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, 
    Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
        <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, 
Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      </providers>
    </membership>
    <roleManager enabled="true" cacheRolesInCookie="false" cookieName=".ASPXROLES" cookieTimeout="30" cookiePath="/" cookieRequireSSL="false" cookieSlidingExpiration="true" cookieProtection="All" defaultProvider="c" createPersistentCookie="false" maxCachedResults="25">
      <providers>
        <clear />
        <add connectionStringName="AspNetSqlMemberShipProvider" applicationName="/" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, 
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
        <add applicationName="/" name="SqlRole" type="System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=2.0.0.0, 
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
        <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, 
Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      </providers>
    </roleManager>

5. Now save & close this web.config file.

III. Explore Site B (Extended new site) & take back up of web.config file.

1. Open web.config file.

2. Put this connection string just after configSections>

connectionStrings>

3. Search for entry <PeoplePickerWildcards> & put this entry within this tag.

4.       Search for entry <membership> & < roleManager> replace whole entry with :
<membership defaultProvider="i" userIsOnlineTimeWindow="15" hashAlgorithmType="">
      <providers>
        <clear />
        <add connectionStringName="AspNetSqlMemberShipProvider" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" passwordAttemptWindow="10" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" name="SqlMember" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, 
    Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
        <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, 
Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      </providers>
    </membership>
    <roleManager enabled="true" cacheRolesInCookie="false" cookieName=".ASPXROLES" cookieTimeout="30" cookiePath="/" cookieRequireSSL="false" cookieSlidingExpiration="true" cookieProtection="All" defaultProvider="c" createPersistentCookie="false" maxCachedResults="25">
      <providers>
        <clear />
        <add connectionStringName="AspNetSqlMemberShipProvider" applicationName="/" name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, 
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
        <add applicationName="/" name="SqlRole" type="System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=2.0.0.0, 
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
        <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, 
Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      </providers>
    </roleManager>

5. Now save & close this web.config file.

IV. Explore Central Administration Site & take back up of web.config file.

1. Open web.config file.

2. Put this connection string just after configSections>

connectionStrings>

3. Search for entry <PeoplePickerWildcards> & put this entry within this tag.

4. Search for entry <membership> & < roleManager> replace whole entry with :

5. Now save & close this web.config file.

V. Now click on “SharePoint web services” & then click on “SecurityTokenServiceApplication” and explore it.

1. Search for tag system.net> & paste this just after system.net> tag

connectionStrings>

<system.web>

providers>

membership>

providers>

roleManager>

system.web>

2. Now Save & Close this. Web.config file.

7. Go to Center Administration, Click on Manage Web Application.

8. Select Site “A” & Click on User Policy.

I. You will get a dialog box

II. Click on “Add Users”, you will see the below dialog box, which will ask you to select the zone for which you want to add the users. Select zone and click next

III. In the next window, “Choose Users” then “Choose Permission” for those users and click Finish.

Important Note: Don’t forget to grant “dbOwner” access to NT/AUTHORITY user on aspnetdb database.

-----------------------------------------------------------------------------------
DOWNLOAD FBA User Management Tool
-----------------------------------------------------------------------------------