Machine Syntax

LINQ to SQL is a powerful technology that can do as much harm as good if it is mis-used. Here is how to get more out of your LINQ to SQL efforts. Tip 1: Ditch the Extra Baggage with ObjectTrackingEnabled  LINQ to SQL, by default, behaves like it's going on a every possibility. It carries every provision it thinks it'll ever need, and your application carries that extra weight. If you know you're only going for a short hike, why not tell it to leave the pack at home? That's where the ObjectTrackingEnabled property of the DataContext comes in. By default this property is true , which causes LINQ to SQL to keep track of every change you make to your data in case you want to save those changes later. If you know you're only reading data and won't be changing it, I suggest setting this property to false. Then all of that change-tracking overhead goes away. The performance boost does come at a small price, however. Deferred loading will no longer work. You'll have

When the ViewState in your page becomes very large it can be a problem since some firewalls and proxies will prevent access to pages containing huge ViewState sizes. For this purpose ASP.NET introduces the ViewState Chunking mechanism. So ASP.NET enables splitting of the ViewState's single hidden field into several using the MaxPageStateFieldLength property in the web.config section. When the MaxPageStateFieldLength property is set to a positive number, the view state sent to the client browser is broken into multiple hidden fields. Setting the MaxPageStateFieldLength property to a negative number (the default) indicates that the view-state field should not be separated into chunks. Setting the MaxPageStateFieldLength to a small number may result in poor performance. Sample ViewState before: <input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE"value="/wEPDwUKLTk2Njk3OTQxNg9kFgICAw9kFgICCQ88KwANAGQYAQUJR3Jp ZFZpZXcxD2dk4sjERFfnDXV/hMFGAL10HQU

Scenario: We identified that the target web server is disclosing the ASP.NET version in its HTTP response. This information might help an attacker gain a greater understanding of the systems in use and potentially develop further attacks targeted at the specific version of ASP.NET. Impact: An attacker might use the disclosed information to harvest specific security vulnerabilities for the version identified. Solution Disable the asp.net version and server information on http headers. Open the web.config file and add this code in the web.config file : <system.webServer>     <httpProtocol>         <customHeaders>             <remove name="Server" />             <remove name="X-AspNet-Version" />             <remove name="X-AspNetMvc-Version" />             <remove name="X-Powered-By" />                                </customHeaders>            </httpProtocol>   </system.webServer> You al

Scenario HTTP only cookies cannot be read by client-side script therefore marking a cookie as HTTP only can provide an additional layer of protection against cross-site script attack. Impact: During Cross-Site scripting attack and attacker might easily access cookies and hijack the victim’s session. Solution You can disable the httpOnlyCookies on the web.config file. Open the web.config file and add the configuration on the httpCookies element like example below : <system.web> : : <httpCookies httpOnlyCookies="false" requireSSL="false" domain="" /> : :  </system.web> By Mohd Zulkamal NOTE : – If You have Found this post Helpful, I will appreciate if you can Share it on Facebook, Twitter and Other Social Media Sites. Thanks =)

This is a example to upload image and store into database. The example also show how to retrieve image from database. Note : Assume the web page have their own master page SQL Create Table SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[imageTest](     [ID] [int] IDENTITY(1,1) NOT NULL,     [Image] [image] NULL,  CONSTRAINT [PK_imageTest] PRIMARY KEY CLUSTERED (     [ID] ASC )WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY] ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY] GO ASPX page Code     <asp:Label ID="Label1" runat="server" Text="Image Upload :"></asp:Label>     <asp:FileUpload ID="FileUpload1" runat="server" />     <br />     <asp:Button ID="Button1" runat="server" Text="Save" OnClick="Button1_Click" />     <br />     <br />     <asp:Panel ID="

In this tutorial, we will move our ListView onto one tab and our form onto a separate tab of a TabView . Along the way, we will also arrange to update our form based on a ListView selections or clicks, even though the Save button will still only add new restaurants to our list. Note : Please follow the Android Tutorial Post Here Before You Step On This Post. Rework the Layout First, we need to change our layout around, to introduce the tabs and split our UI between a list tab and a details tab. This involves: Removing the RelativeLayout and the layout attributes leveraging it,as that was how we had the list and form on a single screen Add in a TabHost , TabWidget , and FrameLayout , the latter of which is parent to the list and details To accomplish this, replace your current LunchList/res/layout/main.xml with the following: <TabHost xmlns:android="http://schemas.android.com/apk/res/android" android:id="@android:id/tabhost" android:layout_width="fill_parent

This is example of upload file using asp.net. Html   <fieldset style="width: 804px" align="center">         <legend><em>Using the FileUpload Control</em>&nbsp;</legend>         <div align="left" style="text-align: center">             <form id="form1" runat="server">                 <div>                     <table style="width: 90%">                         <tr>                             <td colspan="2">                                 <br />                                 <asp:Label ID="LSuccessMssg" runat="server"></asp:Label>                                 <asp:FileUpload ID="FileUpload1" runat="server" /><asp:Button ID="buttonUpload" runat="server"                                     Text="Upload" OnClick="buttonUpload_Click1&quo