IT Shikshalaya

Building a Local AI Agent with .NET and Ollama — Getting Started

2026-09-06T22:08:03.116-07:00

AI is everywhere these days, but most of the examples we see involve sending our data to a cloud-based AI service.

I wanted to try something a little different:

Can we build an AI agent that runs locally and can be integrated with a .NET application?

The answer is yes.

In this series, I’ll walk through how I’m building a local AI agent using .NET, C# and Ollama, and gradually give the agent more capabilities.

The goal isn’t just to create another chatbot. We will eventually make the agent capable of working with files, databases, APIs and other tools.

What Are We Building?

The basic idea is fairly simple. We will have a .NET application that communicates with a locally running AI model.

User Request

↓

AI Agent

↓

Agent Decision & Execution

Decide what needs to be done

Call a tool

Read the result

Think about the result

Continue if necessary

↓

Final Answer

Everything runs on our own machine.

That means we don’t need to send every prompt to an external AI API just to experiment with the technology.

Of course, whether a particular local model is powerful enough depends on your computer’s hardware and the model you choose.

Why Use a Local AI Model?

1. Privacy

If you’re experimenting with internal documents or development data, keeping the AI processing locally can be useful.

2. No API Key

For local experimentation, you don’t need to create an account with an AI provider just to start testing.

3. Learning

This is probably the biggest reason.

When everything runs locally, you get a much better understanding of what is actually happening between your application and the AI model.

4. Development Freedom

You can experiment with prompts, models, tools and agent workflows without worrying about API usage costs during every test.

What Is Ollama?

For this project, we’ll use Ollama to run the AI model locally.

Ollama makes it relatively easy to download and run different language models on your own computer.

Once Ollama is installed, you can download a model and run it from the command line.

ollama pull llama3.2

Then:

ollama run llama3.2

Now you have a local AI model running on your machine.

The exact model you choose can change as new models become available, so don’t consider the model name above a permanent requirement for the project.

Creating the .NET Project

I’m going to use ASP.NET Core for the application.

Create a new Web API project:

dotnet new webapi -n LocalAIAgent

Move into the project:

cd LocalAIAgent

And run it:

dotnet run

At this point, we have a normal ASP.NET Core application.

Nothing particularly exciting yet.

The interesting part comes when we connect it to our local AI model.

Calling Ollama from C#

Ollama exposes an HTTP API, which means we can communicate with it from our .NET application using the standard HttpClient.

For example:

using System.Net.Http.Json; public class OllamaService { private readonly HttpClient _httpClient; public OllamaService(HttpClient httpClient) { _httpClient = httpClient; } public async Task<string?> AskAsync(string prompt) { var request = new { model = "llama3.2", prompt = prompt, stream = false }; var response = await _httpClient.PostAsJsonAsync( "http://localhost:11434/api/generate", request); response.EnsureSuccessStatusCode(); var result = await response.Content .ReadFromJsonAsync<OllamaResponse>(); return result?.Response; } } public class OllamaResponse { public string? Response { get; set; } }

The important thing here is that we’re not calling a cloud AI service.

We’re simply making an HTTP request to a service running on our own computer.

Registering the Service

In Program.cs:

builder.Services.AddHttpClient<OllamaService>();

Now ASP.NET Core can inject our service wherever we need it.

We can then create a simple controller:

[ApiController] [Route("api/[controller]")] public class AIController : ControllerBase { private readonly OllamaService _ollama; public AIController(OllamaService ollama) { _ollama = ollama; } [HttpPost("ask")] public async Task<IActionResult> Ask(string prompt) { var response = await _ollama.AskAsync(prompt); return Ok(new { response }); } }

Now our .NET application can send a question to the local model and return the response.

But This Isn’t Really an AI Agent Yet

And this is an important distinction.

At this stage, we have something closer to a local AI chatbot.

An agent is more interesting.

Instead of simply doing this:

 Question → AI → Answer

we want to eventually build something like:

User Request

↓

AI Agent

↓

Agent Decision & Execution

Decide what needs to be done

Call a tool

Read the result

Think about the result

Continue if necessary

↓

Final Answer

For example, imagine asking:

“Find the sales report for August and tell me which product had the highest sales.”

A normal chatbot may simply tell you that it doesn’t have access to your files.

Our agent could eventually:

Search a folder.
Find the relevant report.
Read the file.
Analyze the data.
Determine the highest-selling product.
Return the result.

That’s where things start getting interesting.

Where We Are Going Next

In the next parts of this series, I’ll extend this basic application step by step.

Conversation memory
System prompts
Agent tools
Reading local files
Working with PDFs
Connecting to SQL Server
Calling external APIs
RAG (Retrieval-Augmented Generation)
Angular frontend
Multi-step agent workflows
Authentication and security

The final goal is to have a useful local AI assistant built around .NET, rather than just another chat window.

Why I’m Building This

AI development doesn’t have to mean abandoning the technologies we already use.

If you’re a .NET developer, you can bring AI into the applications you’re already comfortable building with C#, ASP.NET Core, SQL Server and Angular.

That’s what I want to explore through this series.

I’ll keep the examples practical and build the project incrementally so that we can see not only what works, but also why it works.

In the next article, we’ll connect our .NET application to Ollama properly and build our first working local AI chat endpoint.

Stay tuned.

Dinesh Wadhwa
IT Solutions
Full Stack Developer

Free Online Calculators | SWP, BMI & Random Number Generator

2025-02-10T22:25:00.000-08:00

Free Online Calculators

SWP Calculator - Systematic Withdrawal Plan

Calculate how long your investments will last with systematic withdrawals. This tool helps you plan your finances by estimating the duration of your funds based on monthly withdrawals.

Total Investment Monthly Withdrawal Annual Interest Rate (%) Time (Years)

BMI Calculator - Body Mass Index

Check your BMI to determine if you are underweight, normal, overweight, or obese. This calculator helps you assess your body mass index based on your weight and height.

Weight (kg) Height Unit

Height (m)

Random Number Generator

Generate a random number between the specified range. This tool is great for picking random numbers for games, decisions, or experiments.

Min Max

2018-08-17T21:02:00.001-07:00

AngularJS Introduction

2018-01-27T20:41:00.000-08:00

Introduction to AngularJs

Components of AngularJs & Core Features

Export Grid View of .Net to Excel

2015-05-13T22:39:00.000-07:00

Dear All,

Here is a new article for exporting your Grid View to Excel. Feel Free to ask your queries. Following are the steps for this:

1. Create a Grid View on Web Page.
2. Bind grid view with data. For binding of gridview you can refer to the previous article "Dynamic Gridview Bind" Url: http://dinesh-itsolutions.blogspot.in/2010/09/dynamic-gridview-bind.html.

3. After binding the grid view put a button on the web page named "Export to Excel". On Clicking of that button you can copy and paste the following code.

protected void btnExport(object sender, EventArgs e)

{

    Response.Clear();

    Response.Buffer = true;

    Response.AddHeader("content-disposition",                                            "attachment;filename=ExportedFile.xls");

    Response.Charset = "";

    Response.ContentType = "application/vnd.ms-excel";

    using (StringWriter sw = new StringWriter())

    {

        HtmlTextWriter hw = new HtmlTextWriter(sw);

        //To Export all pages

        GridView1.AllowPaging = false;

        this.gridbind();

        GridView1.HeaderRow.BackColor = Color.White;

        foreach (TableCell cell in GridView1.HeaderRow.Cells)

        {

            cell.BackColor = GridView1.HeaderStyle.BackColor;

        }

        foreach (GridViewRow row in GridView1.Rows)

        {

            row.BackColor = Color.White;

            foreach (TableCell cell in row.Cells)

            {

                if (row.RowIndex % 2 == 0)

                {

                    cell.BackColor = GridView1.AlternatingRowStyle.BackColor;

                }

                else

                {

                    cell.BackColor = GridView1.RowStyle.BackColor;

                }

                cell.CssClass = "textmode";

            }

        }

        GridView1.RenderControl(hw);

        string style = @"<style> .textmode { } </style>";

        Response.Write(style);

        Response.Output.Write(sw.ToString());

        Response.Flush();

        Response.End();

    }

}

   //This is necessary event.So do copy/paste this also.

public override void VerifyRenderingInServerForm(Control control)

{

}

On Clicking of the button. You can successfully export your grid view to the excel.
Hope you like the article. :-)

Delete data from Gridview using Command Field

2011-09-07T03:09:00.000-07:00

In this article, I am going to explain how to delete a record from Gridview.This is very easy process and steps for this is as follows:

1. Add New Webpage in your Webapplication.

2. Drag Gridview from toolbox and bind it to database.

Note:If you need any help in binding the gridview to the database you can view my article which is:

http://dinesh-itsolutions.blogspot.com/2010/09/dynamic-gridview-bind.html

3. Now we proceed further after successfully binding of data.The Steps for Deleting records from gridview are:

a: Select Edit columns from properties of Gridview.

b:You will see dialog box appears for Field:

c:You have to select the Command Fields option from the available field.In Command Fields you will find 3 events which are:

Edit,Update and Cancel.
Select
Delete

From the above Points select Delete Button.

d: Now fire the event RowDeleteing from Gridview Properties

Coding to delete the data from gridview on Event Row Deleting is:

protected void GridView1_RowDeleting(object sender,

GridViewDeleteEventArgs e)

{

con.Open();

Label id =(Label)GridView1.

Rows[e.RowIndex].FindControl("Label5");

SqlCommand save = new SqlCommand();

save.Connection = con;

save.CommandText="delete from tbtablename where id='"+

id.Text+"'";

save.ExecuteNonQuery();

save.Dispose();

con.Close();

luck(); //bind function name

}

If you any query in this article do ask me.

Thank You

Introduction to .NET and .NET Architecture

2011-04-25T18:37:00.000-07:00

What is .NET?

Microsoft .NET (pronounced “dot net”) is a software component that runs on the Windows operating system. .NET provides tools and libraries that enable developers to create Windows software much faster and easier. .NET benefits end-users by providing applications of higher capability, quality and security. The .NET Framework must be installed on a user’s PC to run .NET applications.

This is how Microsoft describes it: “.NET is the Microsoft Web services strategy to connect information, people, systems, and devices through software. Integrated across the Microsoft platform, .NET technology provides the ability to quickly build, deploy, manage, and use connected, security-enhanced solutions with Web services.

What is the .NET architecture?

Microsoft .NET consists of four major components:

Common Language Specification (CLS) – blue in the diagram below
Framework Class Library (FCL) – red
Common Language Runtime (CLR) – green
.NET Tools – yellow

At the base of the diagram in gray is the operating system, which technically can be any platform but typically is Microsoft Windows 2000 or greater, accessed through the Win32 API (Application Programming Interface).

Common Language Specification (CLS)

The CLS is a common platform that integrates code and components from multiple .NET programming languages. In other words, a .NET application can be written in multiple programming languages with no extra work by the developer (though converting code between languages can be tricky).

.NET includes new object-oriented programming languages such as C#, Visual Basic .NET, J# (a Java clone) and Managed C++.

Framework Class Library (FCL)

The FCL is a collection of over 7000 classes and data types that enable .NET applications to read and write files, access databases, process XML, display a graphical user interface, draw graphics, use Web services, etc. The FCL wraps much of the massive, complex Win32 API into more simple .NET objects that can be used by C# and other .NET programming languages.

Common Language Runtime (CLR)

The CLR is the execution engine for .NET applications and serves as the interface between .NET applications and the operating system. The CLR provides many services such as:

Loads and executes code
Converts intermediate language to native machine code
Separates processes and memory
Manages memory and objects
Enforces code and access security
Handles exceptions
Interfaces between managed code, COM objects, and DLLs
Provides type-checking
Provides code meta data (Reflection)
Provides profiling, debugging, etc.

.NET Tools

Visual Studio .NET is Microsoft’s flagship tool for developing Windows software. Visual Studio provides an integrated development environment (IDE) for developers to create standalone Windows applications, interactive Web sites, Web applications, and Web services running on any platform that supports .NET.

In addition, there are many .NET Framework tools designed to help developers create, configure, deploy, manage and secure .NET applications and components.

Thank You:

Dinesh Wadhwa

Difference Between ASP.NET & ASP

2011-03-15T01:25:00.001-07:00

What Are Active Server Pages (Classic ASP)?

Active Server Pages or Classic ASP, as it is more commonly known, is a technology that enables you to make dynamic and interactive web pages.

Classic ASP uses server-side scripting to dynamically produce web pages that are not affected by the type of browser the website visitor is using.

The default scripting language used for writing ASP is VBScript, although you can use other scripting languages like JScript (Microsoft's version of JavaScript).

Classic ASP pages have the extension .asp instead of .htm, when a page with the extension .asp is requested by a browser the web server knows to interpret any ASP contained within the web page before sending the HTML produced to the browser. This way all the ASP is run on the web server and no ASP will ever be passed to the web browser.

Any web pages containing ASP cannot be run by just simply opening the page in a web browser. The page must be requested through a web server that supports ASP, this is why ASP stands for Active Server Pages, no server, no active pages.

As Classic ASP was first introduced by Microsoft on it's web server, Internet Information Services (IIS), that runs on all versions of Windows from NT4, including Windows 7, Vista, XP Pro, and Windows Server OS's like Windows 2000, 2003, 2008, it is this web server that ASP pages usually run best on.

What Is ASP.NET ?

ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages.

ASP.NET web pages or webpage, known officially as "web forms", are the main building block for application development. Web forms are contained in files with an ".aspx" extension; these files typically contain static (X)HTML markup, as well as mark up defining server-side Web Controls and User Controls where the developers place all the required static and dynamic content for the web page. Additionally, dynamic code which runs on the server can be placed in a page within a block <% -- dynamic code -- %>, which is similar to other web development technologies such as PHP, JSP, and ASP. With ASP.NET Framework 2.0, Microsoft introduced a new code-behind model which allows static text to remain on the .aspx page, while dynamic code remains in an .aspx.vb or .aspx.cs file (depending on the programming language used).

ASP.NET compared with ASP classic

ASP.NET simplifies developers' transition from Windows application development to web development by offering the ability to build pages composed of controls similar to a Windows user interface. A web control, such as a button or label, functions in very much the same way as its Windows counterpart: code can assign its properties and respond to its events. Controls know how to render themselves: whereas Windows controls draw themselves to the screen, web controls produce segments of HTML and JavaScript which form parts of the resulting page sent to the end-user's browser.

ASP.NET encourages the programmer to develop applications using an event-driven GUI model, rather than in conventional web-scripting environments like ASP and PHP. The framework combines existing technologies such as JavaScript with internal components like "ViewState" to bring persistent (inter-request) state to the inherently stateless web environment.

Other differences compared to ASP classic are:

Compiled code means applications run faster with more design-time errors trapped at the development stage.
Significantly improved run-time error handling, making use of exception handling using try-catch blocks.
Similar metaphors to Microsoft Windows applications such as controls and events.
An extensive set of controls and class libraries allows the rapid building of applications, plus user-defined controls allow commonly-used web template, such as menus. Layout of these controls on a page is easier because most of it can be done visually in most editors.
ASP.NET uses the multi-language abilities of the .NET Common Language Runtime, allowing web pages to be coded in VB.NET, C#, J#, Delphi.NET, Chrome, etc.
Ability to cache the whole page or just parts of it to improve performance.
Ability to use the code-behind development model to separate business logic from presentation.
Ability to use true object-oriented design for programming pages and controls
If an ASP.NET application leaks memory, the ASP.NET runtime unloads the AppDomain hosting the erring application and reloads the application in a new AppDomain.
Session state in ASP.NET can be saved in a Microsoft SQL Server database or in a separate process running on the same machine as the web server or on a different machine. That way session values are not lost when the web server is reset or the ASP.NET worker process is recycled.
Versions of ASP.NET prior to 2.0 were criticized for their lack of standards compliance. The generated HTML and JavaScript sent to the client browser would not always validate against W3C/ECMA standards. In addition, the framework's browser detection feature sometimes incorrectly identified web browsers other than Microsoft's own Internet Explorer as "downlevel" and returned HTML/JavaScript to these clients with some of the features removed, or sometimes crippled or broken. However, in version 2.0, all controls generate valid HTML 4.0, XHTML 1.0 (the default) or XHTML 1.1 output, depending on the site configuration. Detection of standards-compliant web browsers is more robust and support for Cascading Style Sheets is more extensive.
Web Server Controls: these are controls introduced by ASP.NET for providing the UI for the web form. These controls are state managed controls and are WYSIWYG controls.

Embed Tiny Editor in Your Web Application:

2011-01-24T20:27:00.000-08:00

1. First of all open your Web page in your application in which you want to embed the

Editor.

2. This editor is know as Tiny Editor which has nice features by which the user can enter his/her text in stylish way by embedding smileyes, embed photos.

3. We can set font family, Font Size, Cut, Copy, Paste and many other functions are there by which the text can be represented in a better way.

4. Now Steps to embed the Tiny Editor in you web page are:

a: Drag and Drop Textbox and give id to id name RichTextBox.

b: Set the Property of Textbox:-TextMode Property to Multiline.

c: Drop one Label to page, we transfer the text from RichText Box to Label when we store the text to database.

d: Put this Code in your Head Tag:

tinyMCE.init(

{

mode : "textareas",

theme : "advanced",

plugins : safari,spellchecker,pagebreak,style,layer,table,save,advhr,advimage,advlink,emotions,iespell,inlinepopups,insertdatetime,preview,media,searchreplace,print,contextmenu,paste,directionality,fullscreen,noneditable,visualchars,nonbreaking,xhtmlxtras,template,imagemanager,filemanager",

theme_advanced_statusbar_location : "bottom",

theme_advanced_resizing : false,

template_external_list_url : "js/template_list.js",

external_link_list_url : "js/link_list.js",

external_image_list_url : "js/image_list.js",

media_external_list_url : "js/media_list.js"

});

</script>

This code include the path of Java Script File of tiny editor.

5. Download the Tiny Editor from the path which I am giving you below:

Link: http://tinymce.moxiecode.com/download/download.php

6. Put the Downloaded Folder into you Website. This Folder contains all editor files including JS File.

We have given the link of the Editor JS File in 4(d) Point.

7. Now Run your Webpage and see Tiny Editor Placed there.

Enjoy Your Coding:

IF any Query then you can ask me here only.

The Page Life Cycle of an ASP.NET and its controls.

2010-11-18T22:42:00.000-08:00

The life cycle starts when a user requests a web page through his/her browser. The Web server than process the page through a sequence of steps before response is sent back to the user's browser. The steps are as:

Page Request

Start

Page Initialization

Load

Validation

PostBack Event Handling

Render

Unload

Page Request
The page request occurs before the page life cycle begins. When a user requests the page, ASP.NET determines whether the page needs to be parsed and compiled (therefore beginning the life of a page), or whether a cached version of the page can be sent in response without running the page.
Start
In the start step, page properties such as Request and Response are set. At this stage, the page also determines whether the request is a postback or a new request and sets the IsPostBack property. Additionally, during the start step, the page's UICulture property is set.

Page Initialization

During page initialization, controls on the page are available and each control's UniqueID are generated but not their properties. Any themes are also applied to the page.

Developers have access to the Init, InitComplete and PreLoad methods in this stage. The methods are as follows:

Init: This event is raised after all controls have been initialized and any skin settings have been applied. This event is used to read or initialize control properties.

InitComplete: The Page object raises this event. This event is used for processing tasks that require completion of all initialization.

PreLoad: Use this event if you need to perform processing on your page or control before the Load event. After the Page raises this event, it loads view state for itself and all controls, and then processes any postback data included with the Request instance.

Load

During load, if the current request is a postback, control properties are loaded with information recovered from view state and control state. The OnLoad event method is fired during this stage.
This is where you will want to set properties for all of the server controls on your page, request query strings, and establish database connections.

Validation

During validation, the Validate method of all validator controls is called, which sets the IsValid property of individual validator controls and of the page.

PostBack Event Handling

If the request is a postback, any event handlers are called. The event handling for server controls occurs during this stage.

Render

During rendering, view state is saved to the page and then the page calls on each control to contribute its rendered output to the OutputStream of the page's Response property. Render is not really an event. The HTML of the page and all controls are sent to the browser for rendering.

Unload

Unload is called when the page has been fully rendered, sent to the client, and is ready to be discarded. At this point, page properties such as Response and Request are unloaded and any cleanup is performed. The cleanup includes routines such as closing database connections and file streams, or, event logging and other tasks.

Conclusion

When a Web page is requested, the server creates objects associated with the page and all of its child controls objects and uses these to render the page to the browser. Once the final stage is complete, the web server destroys these objects, to free up resource to handle additional request.

I hope that this article would have helped you in understanding the Page Life Cycle in ASP.NET and its controls. Your feedback and constructive contributions are welcome.

Thanx:

Dinesh Wadhwa.

Registration and Email Verification for New Accounts

2010-11-10T02:30:00.000-08:00

In This Code i am Providing the code by which the user can easily registered to the Website and the E-Mail is sent to the user for the Verification. If the user will not verify his/her email,the account is not activated and that person cannot login.

Here are the Following Steps to achieve that:-

1.Create new Web application and make one form in which the user can register and add the following code to the source code:

      //Send email to user for verifying account
        CreateUserWizard cuw = (CreateUserWizard)sender;
        MembershipUser user = Membership.GetUser(cuw.UserName);
        Guid userId = (Guid)user.ProviderUserKey;
        System.Net.Mail.MailMessage EmailMsg = new          System.Net.Mail.MailMessage("info@ask.com",
CreateUserWizard1.Email);
        EmailMsg.Subject = "Email Verification fromhttp:dinesh-itsolutions.blogspot.com/";
        EmailMsg.IsBodyHtml = true;
        EmailMsg.Body = "Thanks for registering with www.http://dinesh-itsolutions.blogspot.com/!<br /><br />Your activation link : <a href=http://http://dinesh-itsolutions.blogspot.com/?ID=" + userId.ToString() + ">Link</a>.";
        System.Net.Mail.SmtpClient mailClient = new System.Net.Mail.SmtpClient();
        //This object stores the authentication values
        System.Net.NetworkCredential basicAuthenticationInfo = new System.Net.NetworkCredential("smtpserverinfo", "smtpserverpassword");

        mailClient.Host = "mail.ask.com";
        mailClient.UseDefaultCredentials = false;
        mailClient.Credentials = basicAuthenticationInfo;
        mailClient.Send(EmailMsg);

2.By the code the email is sent to the user with the unique link.

3.When the user check his/her mail and click on the activate link then it will redirected to the new webpage

now retrieve that unique id from the URL.

4.After Retrieving the Id'...just set the stutus of the Client from 0 to 1 in the database so that the person can login.

Thank You:

Enjoy ....................n in case if any query then ask me......

Adding Template Fields to a GridView Control.

2010-09-12T11:01:00.000-07:00

A TemplateField is used in cases where authors need complete control over the

contents of a GridView column. The TemplateField is declared with an

<ItemTemplate> element, which in turn is used to define the content that will be

rendered for each row in the column. The ItemTemplate can include any valid HTML.

To add a template column:-

1.Set the GridView control's AutoGenerateColumns property to false.

<asp:GridView id="myGrid" runat="server"
   autogeneratecolumns=false
   ...
>

2. Within the GridView declaration, declare a <Columns> element.

3.Within the Columns element, define the <asp:TemplateField>

control, along with the required <ItemTemplate> element.

4.Within the ItemTemplate, define the HTML or server control that

will contain the field value.

To display the value of a field in an item template,

use DataBinding 
Expression Syntax.

5.Optionally set the <asp:TemplateField> control's

other properties.

For syntax, see GridView Control Syntax.

<columns>
 <asp:templatefield>

   <itemtemplate>
     <img width=60 align="top"

src='<%# Eval ("title_id", "../images/title-{0}.gif" )%>'>
   </itemtemplate>

  </asp:templatefield>
   ...
</columns>

Dynamic Gridview Bind

2010-09-03T22:29:00.000-07:00

First You have to Drag Gridview Tool From your Toolbox
and place it to your design .aspx Page:-

Then at the Code behind page in .cs file like Gridview.aspx.cs file
call the following function to your button_click event:-

void BindData()

{
try

SqlConnection con = new SqlConnection(@"server=.\sqlexpress;

database=TestDB;Integrated Security=SSPI;");

DataSet ds = new DataSet();
con.Open();
SqlDataAdapter da = new SqlDataAdapter("select id,name,flag

from EmpData", con);

da.Fill(ds);
BoundField BC1 = new BoundField();

BC1.HeaderText = "ID";

BC1.DataField = "id";
GridView1.Columns.Add(BC1);
BoundField BC2 = new BoundField();

BC2.HeaderText = "Name";
BC2.DataField = "name";
GridView1.Columns.Add(BC2);

GridView1.DataSource = ds;
GridView1.DataBind();
con.Close();
}
catch (Exception e)

{
Response.Write(e.Message.ToString());
con.Close();
}

Enjoy :-)

Create File Uploader (Visual Studio)

2010-09-03T01:56:00.000-07:00

By this Coding you can create File Uploader

and the is file will uploaded into Foder:-

 Design Source Code:-

<form id="form1" runat="server">
    <asp:FileUpload id="FileUploadControl" runat="server" />
    <asp:Button runat="server" id="UploadButton" text="Upload"

     onclick="UploadButton_Click" />
    <br /><br />
    <asp:Label runat="server" id="StatusLabel" text="Upload

     status: " />
</form>

Coding C#:
protected void UploadButton_Click(object sender, EventArgs e)
{
if(FileUploadControl.HasFile)
{
try
{
string filename = Path.GetFileName(FileUploadControl.FileName);
FileUploadControl.SaveAs(Server.MapPath("~/Folderpath") + filename);
StatusLabel.Text = "Upload status: File uploaded!";
}
catch(Exception ex)

{
StatusLabel.Text = "Upload status: The file could not be uploaded.

The following error occured: " + ex.Message;
}
}
}

Creating New Web Page in Asp.net

2010-09-03T01:44:00.000-07:00

Creating New Web Page in Asp.net

1.Open your Visual Studio 2.0 or 3.5 version
2.Go to File Menu---->New------>Website
3.On the Templates,Select ASP.NET Website.
4.In this diolog box set ur Language as C#.
5.Click Ok and your Website gets open.
6.Start working with web pages...