Program Solution

Precompilation In ASP.Net

noreply@blogger.com (Bishar.B.N) — Mon, 17 May 2010 13:19:00 +0000

In this article we will explore the benefits and caveats around pre-compilation and the new aspnet_compiler tool.

When the first request arrives at your web application there is a mind-numbing amount of work to do. The worker process starts, the runtime initializes, ASPX pages are parsed and compiled to intermediate language, methods are just-in-time compiled to native code - and the list goes on and on. If you want to cut out some of the overhead and improve the startup time of your application, then you’ll want to look at the precompile features in ASP.NET 2.0.

Although pre-compilation will give our site a performance boost, the difference in speed will only be noticeable during the first request to each folder. Perhaps a more important benefit is the new deployment option made available by the precompile - the option to deploy a site without copying any of the original source code to the server. This includes the code and markup in aspx, ascx, and master files.

In this article we will explore the benefits and caveats around pre-compilation and the new aspnet_compiler tool. There are two modes for pre-compilation: in place pre-compilation and pre-compilation for deployment. We will take a look at in place pre-compilation first.

In Place Pre-compilation

By default, ASP.NET dynamically parses and compiles all the ASPX pages in a folder when the first request arrives for a page inside that folder. ASP.NET also needs to compile applicable files in the special folders, like App_Code, on the first request, and any code-behind files associated with ASPX and ASCX files. The runtime caches all the compilation results in order to quickly process later requests, and does not need to recompile again unless someone edits a file. This behavior gives us a great deal of flexibility, including the flexibility to change code and markup and instantly have the changes reflected in the next browser request.

The price for this flexibility is the performance hit on the first request. Some people have found their ASP.NET applications to be slow starters. These people usually work in the sales department and perform software demos in front of customers. In place pre-compilation makes the “first hit” to a web application and forces all pages and code in the application to compile.

The tool to use for pre-compilation is the aspnet_compiler executable, which you can find in the %WINDIR%\Microsoft.NET\Framework\v2.x.xxxx directory. If we have a web application in the WebSite1 virtual directory under IIS, we could use the following command line to compile the application.

The –v parameter specifies that we are passing a virtual path to our web site. On servers with multiple websites you may need to use the –m parameter and specify the full IIS metabase path to the application (-m /LM/W3SVC/1/Root/WebSite1).

The pre-compiled code will end up inside of the Temporary ASP.NET File directory, just as it would when the runtime compiles files for a browser request. Inside of the bin directory for the compiled site, you’ll find the assemblies (dll files). The compiler generates special filenames to avoid naming collisions. In the shot below, the dll starting with App_Code contains the code from the App_Code directory – not too surprising. Each folder containing aspx, or ascx files will compile into a dll prefixed with App_Web. The files with a .compiled extension contain XML with information about which original source code file maps to which assembly.

With the compiled files in place your web application should have a slightly better startup time, but a primary benefit to in place pre-compilation will be the ability to ensure the web application is error free. If you happen to modify a class or web form and leave an error in the file, the aspnet_compiler will fail and display the compiler error. The tool will also display any warnings, but warning will not stop compilation.

Pre-compilation For Deployment

Pre-compilation for deployment creates an ‘executable’ (no source code) version of your web application. With pre-compilation for deployment you give the aspnet_compiler the path to your source code, and the path to a target directory for the compilation results, like below.

aspnet_compiler -p "C:\MyDevelopment\WebSite1" -v / C:\Staging

This command will compile the site and place the result in C:\Staging. You must still specify –v as a parameter, even though we are not using a virtual path as either a source or a destination. Instead, the compiler will use this parameter to resolve application root references (~).

The pre-compilation for deployment step will recreate your web site’s folder structure in the destination directory. All of the static files (HTML files, image files, configuration files) are copied into the folder structure exactly as they appear in the source folder hierarchy. A bin directory will appear in the target directory with all of the assemblies and .compiled files.

The target directory will contain no source code. All of the classes in the App_Code folder are now compiled into one or more assemblies in the bin directory, and no .cs or .vb files will exist in the target directory. Master page files will also compile to the bin directory and not exist. All the code and markup in ASPX, ASCX, and ASHX files, along with any associated code-behind files, will live inside of one or more assemblies in the bin directory, although these files will still exist in the target directory, they exist as nearly empty ‘marker’ files. If you open an ASPX file in a pre-compiled target directory you’ll see the following content:

This is a marker file generated by the precompilation tool, and should not be deleted!

Note: this behavior is as of beta 2 and may change. The IIS script map for the ASPX file extension leaves the “Verify that file exists” checkbox unchecked, and the site will work without any of the ASPX files present. There is, however, a problem getting IIS to serve a default document for a directory request unless the file is present.

Once the application finishes compiling you can FTP or XCOPY the target directory to a web server (or map a virtual directory to the target directory), and the application will be ready to run. A benefit to pre-compilation for deployment is that no one can make changes to the web application by tweaking the source code – no source code exists! In fact, you can’t even place a new ASPX file into the existing application directory structure without causing an error.

Making a change to your site will require you to make a change in the original source code, pre-compile the application again, and redeploy all files to the server. There is one caveat in this scenario, in that pre-compilation generates unique filenames for some assemblies in the bin folder, and these filenames will change each time the pre-compiler executes. The first time you run aspnet_compiler you might see App_Web_lufhs9vn.dll in the bin directory, the next time you might see App_Web_hviqdkt.dll with the same compiled code, even though no source file has changed. This means you might have unneeded dlls in your bin directory if you keep repeatedly copy files to the server without cleanup.

Update: use the -fixednames switch to generate repeatable assembly names.

For some people, the ability to update content on the web server by modifying aspx and ascx files is a needed feature. To support this scenario, the aspnet_compiler has the –u switch for an “updateable” pre-compilation. With updateable pre-compilation the ASPX, ASCX, ASHX, and MASTER files are copied to the target directory in tact - they do not become ‘marker’ files. You can deploy these files to the server and modify them without causing an error, because the ASP.NET runtime will dynamically parse and compile these files. All of the source code for code-behind files and in the App_Code folder will still be compiled into assemblies and will not need to be deployed.

Miscellany

A few other features of the aspnet_compiler include the –d switch, which tells the compiler to generate debugging symbols for the application. Debugging symbols are required if you need line numbers in the stack traces of exceptions. The –f switch will force the compiler to overwrite a target directory, even if a precompiled application already exists there. There are also options to give compiled assemblies a strong name, and allow partially trusted callers.

In addition, you can pre-compile an application directly from Visual Studio 2005 using the Build -> Publish menu item. The Publish Web Site dialog will let you select an http, ftp, or local file system destination as the target.

The precompiler also supports strong naming with the -keyfile, -keycontainer, and -delaysign switches. To allow partially trusted callers, use the -aptca switch.

Wrap Up

Although performance is often touted as a benefit of pre-compilation, I tend to think of pre-compilation as a safety feature. Safety in knowing all of the code in a web application compiles without an error, and safety in keeping your source code out of a shared host environment.

Sample Project using MS Access Connection with ADO.Net

noreply@blogger.com (Bishar.B.N) — Sat, 08 May 2010 07:22:00 +0000

This is Sample Project for Connecting the MS Access DataBase with the Vb.Net.I had included a Customer Master screen for saving Data.

Here there a Class ADO.Net to access the Database from the Application.This can be used as template for small utility programs.

Hope this could a Simple and very fast way to access the DB.if you have any queries regarding these please let me know that.

you can download the sample from here...

Download From Here

Get Password from SAM Files

noreply@blogger.com (Bishar.B.N) — Sat, 08 May 2010 05:41:00 +0000

Introduction

I know that this topic has been covered by others on more than one occasion, but I figured I'd go over it yet again and throw in an update or two. Let me start with what this is all about: SAM Files & NT Password Hashes.

NT Password Hashes - When you type your password into a Windows NT, 2000, or XP login Windows encrypts your password using an encryption scheme that turns your password into something that looks like this:

7524248b4d2c9a9eadd3b435c51404ee

This is a password Hash. This is what is actually being checked against when you type your password in. It encrypts what you typed and bounces it against what is stored in the Registry and/or SAM File.

SAM File - Holds the user names and password hashes for every account on the local machine, or domain if it is a domain controller. Simple enough wouldn't you say?

§ Where do I find the SAM/Hashes?

You can find what you're looking for in several locations on a given machine.

It can be found on the hard drive in the folder %systemroot%system32config. However this folder is locked to all accounts including Administrator while the machine is running. The only account that can access the SAM file during operation is the "System" account.

You may also be able to find the SAM file stored in %systemroot% epair if the NT Repair Disk Utility a.k.a. rdisk has been run and the Administrator has not removed the backed up SAM file.

The final location of the SAM or corresponding hashes can be found in the registry. It can be found under HKEY_LOCAL_MACHINESAM. This is also locked to all users, including Administrator, while the machine is in use.

So the three locations of the SAMHashes are:

- %systemroot%system32config

- %systemroot% epair (but only if rdisk has been run)

- In the registry under HKEY_LOCAL_MACHINESAM

§ Obtaining the SAMPassword Hashes

Wow, how wonderful. Now we know where the goods are, and the problem is this... "How do I get my hands on those hashes?" The answer is "One of four ways."

1) Probably the easiest way to do this is to boot your target machine to an alternate OS like NTFSDOS or Linux and just copy the SAM from the %systemroot%system32config folder. It's quick, it's easy, and it's effective. You can get a copy of NTFSDOS from Sysinternals(http://www.sysinternals.com) The regular version of NTFSDOS is freeware, which is always nice, but only allows for Read-Only access. This should be fine for what you want to do, however, if you're the kind of person that just has to have total control and has some money to burn. NTFSDOS Pro, which is also by Sysinternals has read/write access but it'll cost you $299.

2) Once again, you may be able to obtain the SAM from %systemroot% epair if rdisk has been run and you are lucky enough to have a sloppy admin.

3) You can also get password hashes by using pwdump2. pwdump uses .DLL injection in order to use the system account to view the password hashes stored in the registry. It then pulls the hashes from the registry and stores them in a handy little text file that you can then import into a password cracking utility like l0phtcrack.

4) The final way to obtain password hashes is to listen directly to the network traffic as it floats by your computer and grab hashes using the above mentioned l0phtcrack.

§ Cracking Password Hashes

With the hashes in hand and an eagerness to find out what passwords lie waiting. Let's get cracking. While there are numerous programs available for the use of password cracking I will quickly cover two of the most popular ones.

John the Ripper - John the Ripper is to many, the old standby password cracker. It is command line which makes it nice if you're doing some scripting, and best of all it's free. The only real thing that JtR is lacking is the ability to launch Brute Force attacks against your password file. But look at it this way, even though it is only a dictionary cracker, that will probably be all you need. I would say that in my experience I can find about 85-90% of the passwords in a given file by using just a dictionary attack. Not bad, not bad at all.

L0phtCrack - Probably the most wildly popular password cracker out there. L0phtCrack is sold by the folks at @Stake. And with a pricetag of $249 for a single user license it sure seems like every one owns it. Boy, @Stake must be making a killing. :) This is probably the nicest password cracker you will ever see. With the ability to import hashes directly from the registry ala pwdump and dictionary, hybrid, and brute-force capabilities. No password should last long. Well, I shouldn't say "no password". But almost all will fall to L0phtCrack given enough time.

§ Injecting Password Hashes into the SAM

Probably one of my favorite and easiest ways to gain Administrator privileges on a machine, is by injecting password hashes into the SAM file. In order to do this you will need physical access to the machine and a brain larger than a peanut. Using a utility called "chntpw" by Petter Nordhal-Hagen you can inject whatever password you wish into the SAM file of any NT, 2000, or XP machine thereby giving you total control. I would suggest backing up the SAM file first by using an alternate OS. Go in, inject the password of your choosing. Login using your new password. Do what you need to do. Then restore the original SAM so no one knows you were there.

§ Password Strength

By looking at the methods above, you can see the importance in keeping strong passwords. Someone may be able to get there hands on your hashes, but it's whether or not they can crack them that is the real test. Don't make it easy on them.

When I create a password I like to use the first letter of each word in a phrase. Like "Password Strength is important so I pick good passwords" would be "psiisipgp". Now you have a 9 character password that isn't in any dictionary I know of. Bye Bye John the Ripper.

Now I like to flank passwords in special characters like "@$%?", now your password is ?psiisipgp?. This will ensure L0phtCrack takes a long time cracking it, giving you time to change it if you discover a breach, or just change your passwords regularly.

If you want to get insane, like I do, you can add non-printable ascii characters to your passwords. Using the Alt key and the numbers on your number pad, hold Alt and key in 149. you should get a character like this "ò". Flank your password with this before your question marks and now you've got a secure password. ?òpsiisipgpò? can't be cracked by L0phtCrack since it doesn't allow for non-printable ascii characters. Bye Bye L0phtCrack.

I know this may seem like a lot to do, but let's face it, a weak password is a cracked password.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

NTFSDOS - (http://www.sysinternals.com)

pwdump2 - (http://www.webspan.net/~tas/pwdump2/)

John the Ripper - (http://www.openwall.com/john/)

L0phtCrack - (http://www.atstake.com/research/lc3/)

chntpw - (http://home.eunet.no/~pnordahl/ntpasswd/)

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Convert int to ascci using asp.net

noreply@blogger.com (Bishar.B.N) — Wed, 18 Jun 2008 09:54:00 +0000

Converting INTEGER into an ASCII char is very simple . In C# we dont need to do anything special, just type-cast the INT into a CHAR.

int i = 65;
char a = (char) i;
Console.WriteLine("Result : "+a.toString());

Result : A

Converting ASCII char into an INTEGER is also same way but vice versa.Type-casting CHAR into an INT.

char a = 'A';
int i = (int) a;
Console.WriteLine("Result : "+i.toString());

Result : 65

.Net Fundementals

noreply@blogger.com (Bishar.B.N) — Thu, 01 May 2008 11:39:00 +0000

Asp.net Documents

ASP.NET is one of the more powerful tools available for building Web applications. Learn to use Microsoft Visual Studio 2005 to build database-driven ASP.NET Web applications. We cover the fundamentals of Visual Studio 2005; the various server side controls; the page life cycle; databinding in ASP.NET; how to design a three-tiered application complete with a presentation layer, business layer, and data access layer; using ADO.NET to select, insert, update, and delete data; design user controls for component-based applications; optimize a Web application with caching; and other topics. Students may choose to work in either C# or VB.NET.

Prerequisites:
Prerequisites: Experience in object-oriented programming or proficiency in developing Web applications and client server technology.
Visual Basic .NET Programming

X52.9294 / Continuing Education / $1,095
SUMMER 2008
VB.Net
Programmers use Visual Basic.NET (VB.NET) for rapid development of browser-based Windows applications. In this course, students with Windows programming experience learn the basics of VB.NET. Understand the .NET framework, which implements Microsoft's support for Web services; the common language runtime, which allows programs to be run in any Windows environment; VB.NET syntax; object-oriented programming in VB.NET; error handling; and database access in VB.NET. Upon completion of the course, students can build database-driven VB.NET applications that use Web services.

Prerequisites:
Prerequisite: Prior experience in one of the following: C, C++, Visual Basic, Java, or PERL.
C# .NET Programming

X52.9295 / Continuing Education / $1,095
SUMMER 2008

Microsoft's newest object-oriented language, C#, allows programmers to rapidly build applications for the Microsoft .NET platform. Learn about C#'s support for constructors, methods, overloaded methods, and static methods. Topics include object cleanup and data, field method and property access, base classes, data access between classes, cloning, identity, equivalence, and inheritance, as well as other C# features.

Write TO Excel using vb.net

noreply@blogger.com (Bishar.B.N) — Thu, 01 May 2008 11:36:00 +0000

'Programmer :Bishar
'Date :26-03-08

Imports System.IO
Imports Microsoft.Office.Interop
Imports System.Text.RegularExpressions

Public Class Form1

Private Sub btnbrowse_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnbrowse.Click
If (FolderBrowserDialog1.ShowDialog = Windows.Forms.DialogResult.OK) Then
txtpath.Text = FolderBrowserDialog1.SelectedPath
End If
End Sub

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
FolderBrowserDialog1.ShowNewFolderButton = False
End Sub

Private Sub btnconvert_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnconvert.Click
Dim excelapp As New Excel.Application
Dim excelbook As Excel.Workbook
excelbook = excelapp.Workbooks.Add(Excel.XlWBATemplate.xlWBATWorksheet)
Dim excelWorksheet As Excel.Worksheet = CType(excelbook.Worksheets(1), Excel.Worksheet)
Dim filename As String = ""
Dim objrange As Excel.Range = Nothing
Dim m_objFont As Excel.Font = Nothing
Dim cellcount As Integer = 1
Dim testfile As String = ""
Dim progressmax As Integer = 100
Dim labelincr As Integer = 0
Dim NILLCHAR As String = "-"
Try

If (txtpath.Text <> "") Then
ProgressBar1.Maximum = Directory.GetFiles(txtpath.Text).Length
Dim progressincr As Integer = ProgressBar1.Maximum / progressmax

For Each file As String In Directory.GetFiles(txtpath.Text)

If (Path.GetExtension(file).ToUpper = ".HTML" Or Path.GetExtension(file).ToUpper = ".HTM") Then
testfile = file
Dim sr As StreamReader
filename = ""
sr = New StreamReader(file)
'Read from the html file
Dim content As String = sr.ReadToEnd
'To create the output folder
filename = Environment.CurrentDirectory + "\Output"
If (Not IO.Directory.Exists(filename)) Then
Directory.CreateDirectory(filename)
End If

filename = filename + "\" + "Ouput.xls"

excelapp.Cells(1, 1).value = "LicenseNumber"
excelapp.Cells(1, 2).value = "DateSubmitted"
excelapp.Cells(1, 3).value = "BusinessName"
excelapp.Cells(1, 4).value = "LocationAdddress"
excelapp.Cells(1, 5).value = "City"
excelapp.Cells(1, 6).value = "Zip"
excelapp.Cells(1, 7).value = "County"
excelapp.Cells(1, 8).value = "LicenseType:"
excelapp.Cells(1, 9).value = "Licensee/Agent"
excelapp.Cells(1, 10).value = "Telephone"
excelapp.Cells(1, 11).value = "Type/IP Exp./Lic#"
excelWorksheet.Columns.AutoFit()

' Apply bold to cells A1:B1.
objrange = excelWorksheet.Range("A1", "K1")
m_objFont = objrange.Font
m_objFont.Bold = True

For Each line1 As String In Regex.Split(content, "< / table >")

cellcount = cellcount + 1

'Searching for each Field in the Content

'1) Licensee: No

Dim Licensee As String = extractword(line1, "License Number:", 1)
excelapp.Cells(cellcount, 1).value = StrConv(Licensee, VbStrConv.ProperCase)
excelWorksheet.Columns.AutoFit()

'2) Date Submitted:
Dim datesub As String = extractword(line1, "Date Submitted:", 3)
excelapp.Cells(cellcount, 2).value = datesub
excelWorksheet.Columns.AutoFit()

'3)Status

Dim status As String = extractword(line1, "Business Name:", 1)
excelapp.Cells(cellcount, 3).value = StrConv(status, VbStrConv.ProperCase)
excelWorksheet.Columns.AutoFit()

'4 Location Address
Dim officer As String = extractword(line1, "Location Address:", 1)
excelapp.Cells(cellcount, 4).value = StrConv(officer, VbStrConv.ProperCase)
excelWorksheet.Columns.AutoFit()

'5)CITY
Dim city As String = extractword1(line1, "Location Address:", "CITY")
If (city.Contains("&nbsp")) Then
city = removespace(city, " ")
End If
excelapp.Cells(cellcount, 5).value = StrConv(city, VbStrConv.ProperCase)
excelWorksheet.Columns.AutoFit()

'6 ZIP

Dim zip As String = extractword1(line1, "Location Address:", "ZIP")
If (zip.Contains("&nbsp")) Then
zip = removespace(zip, " ")
End If
excelapp.Cells(cellcount, 6).value = StrConv(zip, VbStrConv.ProperCase)
excelWorksheet.Columns.AutoFit()

'7 County
Dim County As String = extractword(line1, "County/License Type:", 1)
If (County.Contains("&nbsp")) Then
County = removespace(County, " ")
End If
excelapp.Cells(cellcount, 7).value = StrConv(County, VbStrConv.ProperCase)

excelWorksheet.Columns.AutoFit()

'8 License Type:
Dim licencetype As String = extractword(line1, "County/License Type:", 2)
excelapp.Cells(cellcount, 8).value = StrConv(licencetype, VbStrConv.ProperCase)
excelWorksheet.Columns.AutoFit()

'9 Licensee/Agent/Tel.
Dim license As String = extractword(line1, "Licensee/Agent/Tel.:", 1)
excelapp.Cells(cellcount, 9).value = StrConv(license, VbStrConv.ProperCase)
excelWorksheet.Columns.AutoFit()

'10 telephone
Dim phone As String = extractword(line1, "Licensee/Agent/Tel.:", 2)
excelapp.Cells(cellcount, 10).value = StrConv(phone, VbStrConv.ProperCase)
excelWorksheet.Columns.AutoFit()

' 11 License Query System Date

Dim licensequery As String = extractword(line1, "Type/IP Exp./Lic. #:", 1)
Dim dat As String = extractword(line1, "Type/IP Exp./Lic. #:", 2)
Dim licno As String = extractword(line1, "Type/IP Exp./Lic. #:", 3)

excelapp.Cells(cellcount, 1).value = licensequery + dat + licno
excelWorksheet.Columns.AutoFit()

Next

sr.Close()
' excelbook.Save()
End If
If (ProgressBar1.Value <= ProgressBar1.Maximum) Then ProgressBar1.Value = ProgressBar1.Value + 1 labelincr = labelincr + progressincr Label2.Text = labelincr.ToString End If Next Label2.Text = "Completed" excelbook.SaveAs(filename) excelapp.Workbooks.Close() excelapp.Quit() GC.Collect() Me.Close() Else MessageBox.Show("Select the folder") End If Catch ex As Exception excelbook.Save() excelapp.Workbooks.Close() excelapp.Quit() GC.Collect() MessageBox.Show(ex.Message + " " + testfile) End Try End Sub Private Function extractword(ByVal content As String, ByVal searchstr As String, ByVal count As Integer) Try Dim counter As Integer = 0 Dim word As String = "" For Each line2 As String In Regex.Split(content, "")
counter += 1
If (counter > count) Then
' Dim pos As Integer = line.IndexOf("")
Dim pos As Integer = line.IndexOf(">")
word = line.Remove(0, pos + 1)
If (word.Contains("")) Then
word = word.Remove(0, Len("") + word.IndexOf(""))
End If
If (word.Contains("")) Then
word = word.Remove(word.IndexOf(""), Len(word) - word.IndexOf(""))
End If

'If (word <> "") Then
Exit For
'End If
'word = word.Remove(0, word.IndexOf("") + Len(""))

End If
Next
counter = 0
End If
Next

Return word
Catch ex As Exception
Return ""
End Try
End Function
Private Function extractword1(ByVal content As String, ByVal searchstr As String, ByVal type As String)
Try

Dim counter As Integer = 0
Dim word As String = ""
Dim trcount As Integer = 0

For Each line2 As String In Regex.Split(content, "")
If (line2.Contains(searchstr) Or type = "OVER") Then
If (type = "CITY") Then
trcount = 0
type = "OVER"
Continue For
End If
If (type = "ZIP") Then
trcount = 1
type = "OVER"
Continue For
End If
For Each line As String In Regex.Split(line2, "")
If (line <> "" And line <> " ") Then
counter += 1
If (counter > trcount) Then
Dim pos As Integer = line.LastIndexOf(">")
word = line.Remove(0, pos + 1)
If (word <> "") Then
Return word
End If
'word = word.Remove(0, word.IndexOf("") + Len(""))

End If
End If
Next
End If
counter = 0
Next

Return word
Catch ex As Exception
Return ""
End Try
End Function

Private Function removespace(ByVal word As String, ByVal checkstr As String)
Try
Dim addresspos As Integer = word.IndexOf(checkstr)
word = word.Remove(addresspos, Len(word) - addresspos)
Return word
Catch ex As Exception
Return word
End Try
End Function

Private Function RemoveHTMLTags(ByVal strText As String) As String
Return Regex.Replace(strText, "<[^>]*>", "")
End Function

End Class

Regular Expression To remove Html Tags

noreply@blogger.com (Bishar.B.N) — Thu, 01 May 2008 11:33:00 +0000

Read the html File using the Stream Reader

If (Path.GetExtension(file).ToUpper = ".HTML" Or Path.GetExtension(file).ToUpper = ".HTM") Then

Dim sr As StreamReader

sr = New StreamReader(file)
'Read from the html file
Dim content As String = sr.ReadToEnd
dim Output as string="'
Output= RemoveHtml(content)

Private Function RemoveHTMLTags(ByVal strText As String) As String
Return Regex.Replace(strText, "<[^>]*>", "")
End Function

Please Try this at ur Code

Compiling C++ programs using VC++ .net

noreply@blogger.com (Bishar.B.N) — Tue, 22 Apr 2008 05:52:00 +0000

1. Open the Visual Studio 2008 Command Prompt window.

Click the Start button, point to All Programs, Microsoft Visual Studio 2008, Visual Studio Tools, and click Visual Studio 2008 Command Prompt.

2. At the command prompt, type notepad simpleclr.cpp and press Enter.

Click Yes when you are prompted to create a new file.

3. In Notepad, type the following lines:

4.           int main()

5.           {

6.               System::Console::WriteLine("This is a Visual C++ program.");

7. On the File menu, click Save.

You have created a Visual C++ source file that uses a .NET class (Console) and is located in the System namespace.

8. On the File menu, click Exit to close Notepad.

9. At the command prompt, type cl /clr simpleclr.cpp and press Enter. The cl.exe compiler generates an executable program simpleclr.exe.

10. To see a list of all files in the directory named simpleclr with any extension, type dir simpleclr.* and press Enter.

The .obj file is an intermediate format file that you can safely ignore.

The .manifest file is an XML file that contains information about the assembly. (An assembly is the .NET unit of deployment, such as an .exe program or .dll component or library.)

11. To run the simpleclr.exe program, type simpleclr and press Enter.

The program displays this text and exits:

This is a Visual C++ program.

12. To close the Command Prompt window, type exit and press Enter.

Compiling C++ programs using VC++ .net

http://facweb.cs.depaul.edu/msvcdocs/vc++.net/instruction.html

Here are instructions to compile C++ programs using VC++ .net, by way of "project", for two situations:

Starting a new file and a new project
Already having a file, and creating a new project

The Steps:

Start VC++ .net. You will see an opening screen similar to the following.

Click on "New Project" tab in the right pane, then you see a pop-up window comes up. In this window, single-click on the "Managed C++ Empty Project" icon in the right "Templates" pane (Note you will probably need to scroll down to find the ion).

Case 1: If you are creating a new file (source code):
Suppose you want to create a file called "temp.cpp" in a subdirectory/project called "assign1" under a path "c:\courses\309" (thus the new project path will be c:\courses\309\assign1\). In the same pop-up window, type in (or browse) "c:\courses\309" for the "Location" and "assign1" for the "Name". As you type in for the Name, you see "temp.cpp" is appended at the end of "Project will be created at".
Case 2: If you already have a file
Suppose you have a file called "temp.cpp" under a directory "c:\courses\309\assign1\". In the same pop-up window, type in (or browse) "c:\courses\309" for the "Location" and "assign1" for the "Name". As you type in for the Name, you see "temp.cpp" is appended at the end of "Project will be created at".

Hit "OK". Then you are back to the main screen. Now you see several info appeared in the "Solution Explore" pane on the left.

Now you must add a file to the project.

Case 1: If you are creating a new file (source code):
From the top menu-bar, select "Project", then "Add New Item". In the pop-up window, click on the "C++File (.cpp)" on the right pane, and enter "temp.cpp" (or any name for the new file) in the "Name" box..

Case 2: If you already have a file
From the top menu-bar, select "Project", then "Add Existing Item". In the pop-up window, select all files with .cpp extension (only -- DO NOT ADD header files!) If you have more than one .cpp file, hold down the control key and single-click on all .cpp files.

Hit ok. You are back to the main screen again. If you are starting a new file, type in the code on the right pane, and save the file by hitting the Save button at the top. If you are working on an existing file (or files), double-click on the icon of the file you like to work on in the left "Solution Explore" pane (Note that icons for some files may be under "Header Files" or "Resource Files").

Now you build the project by selecting Build at the top menu-bar, then "Build assign1". You can see the progress of compilation in the "Output" pane at the bottom. If any syntax error is detected in your code, fix it/them and do the Build procedure again.

After the project is built, you execute the project by selecting "Debug" from the top menu bar, then "Start without debugging" . The program/project is executed and an MS-DOS window shows up with the output of the program.

Refer this link

http://facweb.cs.depaul.edu/msvcdocs/vc++.net/instruction.html

To compile a Visual C++ .NET console application on the command line

noreply@blogger.com (Bishar.B.N) — Tue, 22 Apr 2008 05:50:00 +0000

1. Open the Visual Studio 2008 Command Prompt window.

Click the Start button, point to All Programs, Microsoft Visual Studio 2008, Visual Studio Tools, and click Visual Studio 2008 Command Prompt.

2. At the command prompt, type notepad simpleclr.cpp and press Enter.

Click Yes when you are prompted to create a new file.

3. In Notepad, type the following lines:

4.           int main()

5.           {

6.               System::Console::WriteLine("This is a Visual C++ program.");

7. On the File menu, click Save.

You have created a Visual C++ source file that uses a .NET class (Console) and is located in the System namespace.

8. On the File menu, click Exit to close Notepad.

9. At the command prompt, type cl /clr simpleclr.cpp and press Enter. The cl.exe compiler generates an executable program simpleclr.exe.

10. To see a list of all files in the directory named simpleclr with any extension, type dir simpleclr.* and press Enter.

The .obj file is an intermediate format file that you can safely ignore.

The .manifest file is an XML file that contains information about the assembly. (An assembly is the .NET unit of deployment, such as an .exe program or .dll component or library.)

11. To run the simpleclr.exe program, type simpleclr and press Enter.

The program displays this text and exits:

This is a Visual C++ program.

12. To close the Command Prompt window, type exit and press Enter.

Compiling a Native C++ Program from the Command Line (C++)

noreply@blogger.com (Bishar.B.N) — Tue, 22 Apr 2008 05:43:00 +0000

Compiling a Native C++ Program from the Command Line (C++)

Visual C++ includes a C++ compiler that you can use to create everything from simple Visual C++ programs to Windows Forms applications and components.

In this procedure, you create simple Visual C++ programs by using a text editor and compile them on the command line.

You can also compile Visual C++ programs that you created with a text editor by using the Visual Studio development environment. See Compiling a C++ Program that Targets the CLR in Visual Studio (C++) for more information.

You can use your own Visual C++ programs instead of typing the simple programs shown in these procedures. You can also use any of the Visual C++ code sample programs in the help topics.

To create a Visual C++ source file and compile it on the command line

1. Open the Visual Studio 2008 Command Prompt window.

Click the Start button, point to All Programs, Microsoft Visual Studio 2008, Visual Studio Tools, and then click Visual Studio 2008 Command Prompt.

2. At the command prompt, type notepad simple.cpp and press Enter.

Click Yes when you are prompted to create a new file.

3. In Notepad, type the following lines:

4. #include
6. int main()
7. {
8. std::cout << "This is a native C++ program."

9.               return 0;

10. On the File menu, click Save. You have created a Visual C++ source file.

11. On the File menu, click Exit to close Notepad.

12. At the command prompt, type cl /EHsc simple.cpp and press Enter. The /EHsc command-line option instructs the compiler to enable C++ exception handling. For more information, see /EH (Exception Handling Model).

The cl.exe compiler generates an executable program simple.exe.

You can see the executable program name in the lines of output information that the compiler displays.

13. To see a list of all files in the directory named simple with any extension, type dir simple.* and press Enter.

The .obj file is an intermediate format file that you can safely ignore.

14. To run the simple.exe program, type simple and press Enter.

The program displays this text and exits:

This is a native C++ program.

15. To close the Command Prompt window, type exit and press Enter.

Compiling a Visual C++ Program That Uses .NET Classes

This procedure shows the command line that you use to compile a Visual C++ program that uses .NET Framework classes.

You must use the /clr (Common Language Runtime Compilation) compiler option because this program uses .NET classes and requires the Visual C++ compiler to include the necessary .NET libraries. The Visual C++ compiler generates an .exe file that contains MSIL code instead of machine executable instructions.

You can follow the steps in this procedure to compile any sample Visual C++ program in the help topics.

How to add Software Expriation

noreply@blogger.com (Bishar.B.N) — Tue, 22 Apr 2008 04:54:00 +0000

For 30 days or 60 days trial:

check the date on installation or on first run of program(the setting variable will be 0 in first time):

save the current date in the setting variable

now every run read that variable and see if the software is expired: it is better to read the date from internet using web service

install the software on only one computer:

Create setting variable for example license
when the software run check this variable if it is not contain the correct value then:
1- the software read the processor number
2- the user give you the number by phone or email or...
3- you generate the license key from processor number(by calculation manually or by calculation with small software)
4- you give it to the user
5- the software save it in setting variable
6- the software must check the setting variable and the processor number and make the calculation to see if it contain the current number before starting,if not it will give the processor number to user to send it to you
and so the license key will work only on one computer.

Parsing XML with XmlDocument

noreply@blogger.com (Bishar.B.N) — Thu, 10 Apr 2008 05:07:00 +0000

Parsing XML with XmlDocument
The XmlDocument class is modeled based on Document Object Model. XmlDocument class is appropriate if you need to extract data in a non-sequential manner. Figure 3 below outlines parsing of xml file with XmlDocument
Collapse
Imports System.IO
Imports System.Xml
Module ParsingUsingXmlDocument
Sub Main()
Try
Dim m_xmld As XmlDocument
Dim m_nodelist As XmlNodeList
Dim m_node As XmlNode
'Create the XML Document

m_xmld = New XmlDocument()
'Load the Xml file

m_xmld.Load("C:\CMS\Personal\family.xml")
'Get the list of name nodes

m_nodelist = m_xmld.SelectNodes("/family/name")
'Loop through the nodes

For Each m_node In m_nodelist
'Get the Gender Attribute Value

Dim genderAttribute = m_node.Attributes.GetNamedItem("gender").Value
'Get the firstName Element Value

Dim firstNameValue = m_node.ChildNodes.Item(0).InnerText
'Get the lastName Element Value

Dim lastNameValue = m_node.ChildNodes.Item(1).InnerText
'Write Result to the Console

Console.Write("Gender: " & genderAttribute _
& " FirstName: " & firstNameValue & " LastName: " _
& lastNameValue)
Console.Write(vbCrLf)
Next
Catch errorVariable As Exception
'Error trapping

Console.Write(errorVariable.ToString())
End Try
End Sub
End Module
Figure 3: Xml Parsing with XmlDocument
Compilation and Result
Make sure you have vbc.exe in your path. From the command prompt go to C:\Personal>. Compile ParsingUsingXmlTextReader.vb and ParsingUsingXmlDocument.vb.
C:\Personal>vbc /out:ParsingUsingXmlTextReadervb.exe ParsingUsingXmlTextReader.vb
C:\Personal>vbc /out:ParsingUsingXmlDocumentvb.exe ParsingUsingXmlDocument.vb
When you run the individual program
C:\Personal>ParsingUsingXmlTextReadervb.exe
OR
C:\Personal>ParsingUsingXmlDocumentvb.exe
You will see the following result for both
Gender: Male FirstName: Tom LastName: Smith

Gender: Female FirstName: Dale LastName: Smith
Conclusion
There are different ways to parse XML files and the best method depends on your situation and the programming style preferred.

Register Clients Script

noreply@blogger.com (Bishar.B.N) — Thu, 10 Apr 2008 05:06:00 +0000

Introduction
Registering Client script from server itself useful when , you want certain java script to be executed when page finished loading or when user does a submit on the form .
Background
To get the complete idea about the clientside java script registration from server , u go through the URL http://msdn2.microsoft.com/en-us/library/ms178207.aspx
Using the code
You have a clientscriptmanager object on each aspx page you have . the object name is ClientScript , using ClientScript you can register the script in 4 modes
1. RegisterClientScriptBlock:-Adds Script to the top of the page
2.RegisterClientScriptInclude:- Refer to a external .js file
3.RegisterStartupScript:- script is registered before onload event of a page
4. RegisterOnSubmitStatement:- Script is registered on onSubmit event of page
Have a look at the following example below which uses startupscript in my project, I used this one because I needed script to be executed and load a activex object before page is loaded.
Collapse
if (!ClientScript.IsClientScriptBlockRegistered("exampleScript"))
ClientScript.RegisterStartupScript(this.GetType(), "exampleScript","

");

//you can also do the Add script on the events of the controls , like button click

//I wrote a generic method for adding confirm box to the web controls as shown below

public static void ConfirmMessageBox(ref System.Web.UI.WebControls.WebControl webControl, string message, string webControlName, string eventName)
{

StringBuilder sb = new StringBuilder();
sb.AppendFormat("var str = trim(document.forms[0].{0}.value);", webControlName);
sb.Append("if(str != null)");
sb.Append("{");
sb.Append("if(str != '')");
sb.Append("{");
sb.AppendFormat("var bRet = confirm('{0}');", message);
sb.Append("if(!bRet)");
sb.AppendFormat("document.forms[0].{0}.value = '';", webControlName);
sb.Append("return bRet;");
sb.Append("}");
sb.Append("}");

webControl.Attributes.Add(eventName, sb.ToString());

}
//you can add this script to any textbox or button control on page load as shown below

WebControl control = (WebControl)textBoxControl;
ConfirmMessageBox(ref control, "Are you sure , you want to create this domain",
textBoxControl.ClientID, "onblur");

//Hope this helps in getting better understanding of the client side script registration from server

ClientScript.RegisterStartupScript(this.GetType(), "exampleScript", "");

Programming Read and Write To XML

noreply@blogger.com (Bishar.B.N) — Thu, 10 Apr 2008 05:02:00 +0000

The XmlWriter and XmlTextWriter classes are defined in the System.XML namespace.
The XmlTextWriter class is derived from XmlWriter class, which represents a writer that provides fast non-cached forward-only way of generating XML documents based on the W3C Extensible Markup Language (XML) 1.0 specification.
In this article, I will show you how to use XmlTextWriter class to create an XML document and write data to the document.
Adding namespace Reference
Since Xml classes are defined in the System.XML namespace, so first thing you need to do is to Add the System.XML reference to the project.
using System.Xml;
Creating an XML Document
The constructor of the XmlTextWriter class creates an XML file if file doesn't exist. In this sample, I create a new XML file called xmltest.xml in C\temp directory.
XmlTextWriter writer = new XmlTextWriter("C:\\temp\\xmltest.xml", null);
NOTE: If you don't want to write data in an XML file and want to display XML contents on the Console, pass Console.Out as a parameter of the constructor.
XmlTextWriter writer = new XmlTextWriter(Console.Out);
Adding Data to the Document
The WriteStartDocument method starts a new document. The WriteStartElement and the WriteEndElement pair is used to add a new element to the document. The WriteString writes a string to the document.
writer.WriteStartDocument();
writer.WriteComment("Commentss: XmlWriter Test Program");
writer.WriteProcessingInstruction("Instruction","Person Record");
writer.WriteStartElement("p", "person", "urn:person");
writer.WriteStartElement("LastName","");
writer.WriteString("Chand");
writer.WriteEndElement();
writer.WriteElementInt16("age","", 25);
writer.WriteEndDocument();
Souce Code: Attachment createxml1.cs 2 KB
namespace WriteToXML
{
using System;
using System.Xml;
///

/// Summary description for Class1.
///

public class Class1
{
public Class1()
{
}
public static int Main(string[] args)
{
try
{
// Creates an XML file is not exist
XmlTextWriter writer = new XmlTextWriter("C:\\temp\\xmltest.xml", null);
// Starts a new document
writer.WriteStartDocument();
//Write comments
writer.WriteComment("Commentss: XmlWriter Test Program");
writer.WriteProcessingInstruction("Instruction","Person Record");
// Add elements to the file
writer.WriteStartElement("p", "person", "urn:person");
writer.WriteStartElement("LastName","");
writer.WriteString("Chand");
writer.WriteEndElement();
writer.WriteStartElement("FirstName","");
writer.WriteString("Mahesh");
writer.WriteEndElement();
writer.WriteElementInt16("age","", 25);
// Ends the document
writer.WriteEndDocument();
}
catch (Exception e)
{
Console.WriteLine ("Exception: {0}", e.ToString());
}
return 0;
}
}
}

Active desktop recovery

noreply@blogger.com (Bishar.B.N) — Thu, 10 Apr 2008 04:49:00 +0000

desktop.htt pretty much controls the size and position of your desktop. IE7 is a little bit incompatible with the old profile you may have had already. To fix it go Start >Run, type and enter regedit
Go to this key:
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Desktop\SafeMode\Components
Change the value of DeskHtmlVersion to zero instead of decimal 272.

Configure Asp.Net with IIS

noreply@blogger.com (Bishar.B.N) — Thu, 13 Mar 2008 05:32:00 +0000

1.Go to the Control Panel-> Add/remove Program ->Add/Remove Windows Component
2.There you can see a Window pop up in that Look for IIS (internet Information System)

3)Click the Details button from it is active (Tick almost all the Check Box) and Click Ok.
4)You need the OS(Operating System) CD to install these.So put the OS CD in Drive.and Insatll

5.After Installations has been finished.Make Sure that it had its Service Running in the Windows Services

To run a local Web site in IIS 6.0
1. On the Start menu, click Run.
2. In the Open box, type inetmgr and then click OK.
3. In IIS Manager, expand the local computer, right-click the Web Sites folder,
4. There you see the that the IIS is running.if Not make it Run

Figure of IIS:-This what it look like

All these are You can Make sure that IIS has been Configured.

Still You have Problem

Please Check these reasons
1.Make Sure that All components in the IIS has been installed.(look at Add/remove Windows Components)
2.If that all installed and its showing in the intemgr.But Still Can’t run the Website.Go to Step 3
3.Register the IIS with Asp.net
4.Go to Visual Studio Command Prompt or .Net framework Command Prompt
5. register ASP.NET with my IIS Web Server
Please follow the procedure below to register ASP.NET:
1. Open Command Prompt.
2. Change directory as follows:
o For 32-bit machines change to:
Microsoft.NET\Framework\\
o For 64-bit machines change to:
Microsoft.NET\Framework64\\
3. Run the command ‘aspnet_regiis.exe -i’ and press enter.
If This Doesn’t Solve the Problem.Please make a Comment along with the error or mail to me.
Sure that we can find a solution for any reasonable doubts.

Secrets of Successful Software Requirements

noreply@blogger.com (Bishar.B.N) — Thu, 13 Mar 2008 05:31:00 +0000

Although most companies do some form of requirements, there is often a lack of understanding as to exactly why the requirements need to be created and the level of detail that should be included in the requirements.

Software is always created to solve a need for a client. The client may be an internal client, an external client, or even the general public. Detailed requirements are important to ensure that a program correctly and fully addresses client’s needs.

Detailed requirements make initial development easier and faster because the developers know exactly what should be developed and do not need to make their best guess at the functionality to be implemented or delay development by creating requirements during development. Giving the developers accurate requirements will also result in less rework at the end of development because the stakeholder’s requirements will have been implemented correctly initially and will not be arrived at through trial and error.

A project manager can use the detailed requirements to create accurate timelines and give correct estimates to the client. This ensures that stakeholders are completely aware how long development will take so they can adjust the scope of a project or proactively add resources if necessary.

Finally, testers can use the requirements to create test plans while development is ongoing rather than waiting until development is complete. The requirements give them information about what the program will do so there cannot be disputes between developers and testers as to what the program functionality should be. High quality requirements also describe problem paths that may need additional testing.

Even though highly detailed requirements make development easier in future phases, this is not always possible due to time constraints imposed by the client or market conditions. With this in mind, let’s look at some secrets to improve your requirements process even under tight deadlines.

Include Use Cases

Use cases look at the requirements from the standpoint of an end user working with the program and how the program responds to the user’s inputs. At its simplest level, a use case can be thought of as a play where the end user is one actor and the program is another actor. These two actors then have dialogs which explain the interactions between the actors. More complicated scenarios can have additional actors including other programs, other types of users, and even hardware. Use cases have proven to be very easy to read and understand even for non-technical clients.

Each use case explores what happens when something goes wrong in addition to the “normal” interactions. The exploration of these failure conditions is very important because these cases are the most difficult to code and can cause the most amount of testing. Traditional requirements often ignore these cases. It can be helpful to have developers and testers both think of additional possible failures in a use case so they can be fully documented in the requirements.

Use cases do not provide a complete picture of the system though. A technical specification should also be included in the requirements to detail formulas and routines that take place behind the scenes.

Prototype Screens with a Design Tool

A user of the program only interacts with a program through the user interface so it makes sense to spend a significant amount of time during requirements to ensure that the user interface makes sense, that all functionality is included, and that the most commonly used functionality is easily accessible. The easiest way of doing this is using a screen prototype. There are a variety of methods of making screen prototypes which range from simply drawing the interface with a pen and paper to building “working” prototypes in a higher level language like Visual Basic which allows rapid screen design. However, each of these extremes has serious drawbacks. A pen and paper prototype does not allow users to interact with the prototype and it is more difficult to change. A “working” prototype done in a programming language like Visual Basic can lead the client to believe that the program is nearly complete and that development should not take very long or it can lead the client to believe that changes to the prototype will be costly making them reluctant to make necessary suggestions to improve the program.

Between these two extremes lies screen design applications which allow you to draw the screens and model interactions between screens. High quality prototyping tools allow you to enter sample data and allow users to move between screens by pressing buttons so they can easily understand the interface and its functionality. Most prototyping tools produce the final output in an HTML format so they can be easily shared even if a client is not in the same office where requirements are being developed.

When looking for a prototyping tool, make sure to select a tool which is easy enough to use that you can easily prototype screens while your customer is in the room. This will allow you to brainstorm and make changes to the screens without delays. A prototyping tool should already have common controls already defined to maintain design standards and improve the appearance of your screens. Being able to enter sample data in each screen can allow the customer to pinpoint areas that may be incorrect.

Work Directly with End Users

When designing a new application or making revisions to an existing application, there is no substitute for the direct experience that end users have. An end user can give immediate feedback on your design to point out awkward or incorrect functionality. They also help to ensure that all controls are logically placed for the most efficient use of the system.

Using an interactive prototyping tool allows you to walk a user through the interface or even allow them to work directly with the prototype so they can quickly suggest improvements. As use cases are being developed, it is a good idea to walk users through the use case to ensure that the use case is well thought out and that all functionality is captured both in the use case and the prototype.

Work Directly with End Users

Storing Images to Database and Retrieving to GridView

noreply@blogger.com (Bishar.B.N) — Thu, 13 Mar 2008 05:30:00 +0000

Storing Images to Database and Retrieving to GridView

Introduction

Over the internet, one can easily find a lot of references for uploading images to a database. The major problem arises when one has to retrieve these images and display them in some server control, like the GridView control. In this article we will tackle exactly that. So let's begin... shall we?

Prerequisites

This tutorial assumes that you own a copy of Visual Studio 2005 or Visual Web Developer Express. It also assumes that you are familiar with ASP.Net 2.0 basics and have worked with SQL Express before.

Creating the File Upload page:

We will start with the default page, from where we will provide the user the functionality to upload the images. Open Default.aspx and switch to design-view. Drag-n-drop controls from the toolbox onto the page to create a similar form:

The Text-Box followed by the Browse button is the HTML File Input control. After adding this control onto the form switch to Source-View and add modify the control's source to include runat="server". This will allow us to use the control as a server control.

In the above page, the controls are as follows:

fileUpload - To select the file to upload.
txtTitle - The title of the image.
btnUpload - On click uploads the selected image.
lnkView - The View Images link that loads the images from the databases inside a GridView.
Validation Controls - The Required Field Validation Controls in order to make sure that Title and File are selected.

Let us suppose that the Database File already exists. If not then add one now by right-clicking the Project and clicking on Add Item. Select Database and name it imgDB.mdf. The database will contain one table which is as follows:

Switch to the code-behind class of Default.aspx and add a button click event handler for btnUpload.

Protected Sub btnUpload_Click(..., ...) Handles btnUpload.Click

Dim intLength As Integer

Dim arrContent As Byte()

If fileUpload.PostedFile Is Nothing Then

lblStatus.Text = "No file specified."

Exit Sub

Else

Dim fileName As String = fileUpload.PostedFile.FileName

Dim ext As String = fileName.Substring(fileName.LastIndexOf("."))

ext = ext.ToLower

Dim imgType = fileUpload.PostedFile.ContentType

If ext = ".jpg" Then

ElseIf ext = ".bmp" Then

ElseIf ext = ".gif" Then

ElseIf ext = "jpg" Then

ElseIf ext = "bmp" Then

ElseIf ext = "gif" Then

Else

lblStatus.Text = "Only gif, bmp, or jpg format files supported."

Exit Sub

End If

intLength = Convert.ToInt32(fileUpload.PostedFile.InputStream.Length)

ReDim arrContent(intLength)

fileUpload.PostedFile.InputStream.Read(arrContent, 0, intLength)

If Doc2SQLServer(txtTitle.Text.Trim, arrContent, intLength, imgType) = True Then

lblStatus.Text = "Image uploaded successfully."

Else

lblStatus.Text = "An error occured while uploading Image... Please try again."

End If

End Sub

What this function does is that it grabs the file selected in the File Input control and gets its extension. If the file is of type jpg, bmp, or gif, then it proceeds otherwise it throws an error. This terminates upload if the selected file is not an image of supported format.

After checking the file format, we get the length of the file and create a Byte Array of that same length. This Byte Array will store our file/image for us. Using the InputStream.Read method of fileUpload control, we load the image into the Byte Array.

After having saved the file into the byte array, we call our function Doc2SQLServer to store the file. We pass in the title that was supplied by the user, the byte array (which is our image), the total length, and the type of image.

In the Doc2SQLServer method, we create a connection to our SQL Express database and create an insertion command. After connecting to the database, we execute the query and store our image and its information to the database. Below is the Doc2SQLServer method.

Protected Function Doc2SQLServer(ByVal title As String, ByVal Content As Byte(), ByVal Length As Integer, ByVal strType As String) As Boolean

Try

Dim cnn As Data.SqlClient.SqlConnection

Dim cmd As Data.SqlClient.SqlCommand

Dim param As Data.SqlClient.SqlParameter

Dim strSQL As String

strSQL = "Insert Into tblImage(imgData,imgTitle,imgType,imgLength) Values(@content,@title,@type,@length)"

Dim connString As String = "Data Source=.\SQLEXPRESS;AttachDbFilename=""|DataDirectory|\imgDB.mdf"";Integrated Security=True;User Instance=True"

cnn = New Data.SqlClient.SqlConnection(connString)

cmd = New Data.SqlClient.SqlCommand(strSQL, cnn)

param = New Data.SqlClient.SqlParameter("@content", Data.SqlDbType.Image)

param.Value = Content

cmd.Parameters.Add(param)

param = New Data.SqlClient.SqlParameter("@title", Data.SqlDbType.VarChar)

param.Value = title

cmd.Parameters.Add(param)

param = New Data.SqlClient.SqlParameter("@type", Data.SqlDbType.VarChar)

param.Value = strType

cmd.Parameters.Add(param)

param = New Data.SqlClient.SqlParameter("@length", Data.SqlDbType.BigInt)

param.Value = Length

cmd.Parameters.Add(param)

cnn.Open()

cmd.ExecuteNonQuery()

cnn.Close()

Return True

Catch ex As Exception

Return False

End Try

End Function

The Image Grabber

Next we create a web-page that will grab the image whose id is passed to it as a query string. Right-click the project in solution explorer and add a web-page imgGrab.aspx.

Define the page_load method as follows:

Protected Sub Page_Load(...,...) Handles Me.Load

Try

Dim ds As New DataSet

Dim da As SqlClient.SqlDataAdapter

Dim arrContent As Byte()

Dim dr As DataRow

Dim strSql As String

strSql = "Select * from tblImage Where imgId=" & Request.QueryString("ID")

Dim connString As String = "Data Source=.\SQLEXPRESS;AttachDbFilename=""|DataDirectory|\imgDB.mdf"";Integrated Security=True;User Instance=True"

da = New SqlClient.SqlDataAdapter(strSql, connString)

da.Fill(ds)

dr = ds.Tables(0).Rows(0)

arrContent = CType(dr.Item("imgData"), Byte())

Dim conType As String = dr.Item("imgType").ToString()

Response.ContentType = conType

Response.OutputStream.Write(arrContent, 0, dr.Item("imgLength"))

Response.End()

Catch ex As Exception

End Try

End Sub

What this does is quite simple. It gets the image data whose id is passed in and writes it to the web-page. Response.ContentType sets the web-page as an image content holder and when we write the complete byte array to the response stream, we actually get the image.

Loading Images into the GridView Control

A major problem faced by developers is when loading images back into the datagrid or the new gridview control. I myself faced long hours trying to come up with a solution for this, which in the end was a simple procedure.

Create a new-page, Viewer.aspx and add a GridView onto it. (This page is linked from the Default.aspx page via lnkView). Name the GridView imgGrid and click on the small box located at the upper-right corner of the control.

Click on Edit Columns to open the Fields Dialog as shown below.

In this dialog, uncheck "Auto-generate fields" and add two fields; a bound field and an image field. For the bound field set the column header text to Title and the DataField property to imgTitle (This will bind this column to the imgTitle column in the dataset to which we will load our table data). As for the image field, set the caption to Picture and the DataImageUrlField to imgFile. You might think where this imgFile comes from, especially since the database does not contain a column with such a name.

Switch to the code-behind class and create the page_load event as follows:

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load

Dim ds As New DataSet

Dim da As SqlClient.SqlDataAdapter

Dim strSQL As String

strSQL = "Select imgId,imgTitle from tblImage"

Dim connString As String = "Data Source=.\SQLEXPRESS;AttachDbFilename=""|DataDirectory|\imgDB.mdf"";Integrated Security=True;User Instance=True"

da = New SqlClient.SqlDataAdapter(strSQL, connString)

da.Fill(ds)

ds.Tables(0).Columns.Add("imgFile")

For Each tempRow As DataRow In ds.Tables(0).Rows

tempRow.Item("imgFile") = ("imgGrab.aspx?id=" & tempRow.Item("imgID"))

imgGrid.DataSource = ds

imgGrid.DataBind()

End Sub

What this function does is the simple task of grabbing data from the database. It grabs two columns, imgId and imgTitle. What it does afterwards is the key concept... and the few-lines of code that marks the solution to a big problem.

After filling in the dataset, we know that it contains one table, at index 0 of course. We add a custom column "imgFile" to it.

After that, we traverse through each dataRow in the table. And for each row, we make a call to our imgGrab.aspx page with the id from that row. We set this equal to the record for imgFile for that row.

Thus on display of the GridView, for each row being displayed, the imgGrab.aspx web-page is called and the image is displayed in return.

A screen-shot of the resulting grid:

And all things must come to an end

The main emphasis in this article was on uploading images to a SQL Express database and then displaying those images in the GridView control. I know there are a lot of different articles explaining the technique for uploading to the database, but none for explaining a simple method to retrieve them to a GridView or similar control. Please download the code for this article and play around with it to learn more about it. I hope you found this article interesting and informative. I am open for suggestions and remarks, both negative and positive. Feel free to contact me at salman@premierpos.com.

Tutorial toolbar: Tell A Friend | Add to favorites | Feedback

How to: Implement Simple Forms Authentication

noreply@blogger.com (Bishar.B.N) — Thu, 13 Mar 2008 05:21:00 +0000

To configure the application for forms authentication

This example in this topic presents a simple implementation of ASP.NET forms authentication. It is intended to illustrate the fundamentals of how to use forms authentication to log users into an ASP.NET application.

In the scenario for the example, users request a protected resource, namely a page named Default.aspx. Only one user has access to the protected resource: jchen@contoso.com, with a password of "37Yj*99P". The user name and password are hard-coded into the Logon.aspx file. The example requires three files: the Web.config file, a page named Logon.aspx, and a page named Default.aspx. The files reside in the application root directory.

More Details

Asp.net request handling

noreply@blogger.com (Bishar.B.N) — Fri, 22 Feb 2008 16:12:00 +0000

An Overview of ASP.NET Request Handling

To understand how HttpModules and HttpHandlers fit into the scheme of things, you have to understand the way that ASP.NET handles a request. When a request is received by Internet Information Server (IIS), it looks at the extension to determine which ISAPI filter should handle the request. For any of the supported file extensions, such as .aspx or .asmx, the answer is aspnet_isapi.dll. When ASP.NET fires up, it performs almost the same process again. It looks at the request and compares it to the section of the .config file. By default, machine.config maps .aspx files to the PageHandlerFactory and .asmx files to the WebServiceHandlerFactory. This mapping determines the HttpHandler (class) that is responsible for handling the request. With the concept of mapping, you can create a new HttpHandler and map it to a new type of request. In fact, this is exactly what Microsoft did with Trace.axd. You will find that it is a new HttpHandler that is registered in machine.config for any request path that ends in trace.axd.

While processing a request received from IIS, ASP.NET raises several events. They are raised in the following order:

BeginRequest
AuthenticateRequest
AuthorizeRequest
AcquireRequestState
ResolveRequestCache
Page Constructor
PreRequestHandlerExecute
Page.Init
Page.Load
PostRequestHandlerExecute
ReleaseRequestState
UpdateRequestCache
EndRequest
PreSendRequestHeaders
PreSendRequestContent

The items in bold represent several of the page-level events that are raised during the execution of a page. Each of these events can be sunk, providing opportunities to participate in the processing of each page in an application. In Chapter 7, "Security," we looked at handling the AuthenticateRequest and AuthorizeRequest events.

Reading Image From DB

noreply@blogger.com (Bishar.B.N) — Fri, 22 Feb 2008 16:11:00 +0000

Image tempImg = pictureBox1.Image;
System.IO.MemoryStream memBuffer = new System.IO.MemoryStream();
tempImg.Save(memBuffer, System.Drawing.Imaging.ImageFormat.Bmp);
byte[] output = new byte[memBuffer.Length];
memBuffer.Read(output, 0, (int)memBuffer.Length);
// Write to SQL here

// Read from SQL here
memBuffer.Write(output, 0, output.Length);
tempImg = Image.FromStream(memBuffer);
pictureBox1.Image = tempImg;

ASP.NET Email Tutorial

noreply@blogger.com (Bishar.B.N) — Fri, 22 Feb 2008 16:10:00 +0000

ASP.NET Email Tutorial
This tutorial will show you how to send a simple email message using ASP.NET 2.0 and C#

Download the Full Working Version of this Project written with Visual Studio.NET C# 2005 Here!

Sending a email using ASP.NET 2.0 and C# 2.0 is actually very simple.

First, you will need to import the System.Net.Mail namespace.

The System.Net.Mail namespace contains the SmtpClient and MailMessage Classes that we need in order to send the email.

using System.Net.Mail;

We use the btnSubmit_Click event to do the work.

We then call the emailClient.Send to send the message using the variables from our ASP.NET coded page.

protected void btnSubmit_Click(object sender, EventArgs e)
{
try
{

MailMessage message = new MailMessage(txtFrom.Text, txtTo.Text, txtSubject.Text, txtBody.Text);
SmtpClient emailClient = new SmtpClient(txtSMTPServer.Text);
emailClient.Send(message);
litStatus.Text = "Message Sent";

}
catch (Exception ex)
{
litStatus.Text=ex.ToString();
}
}

The front end .aspx page looks something like this:

To
From
SMTP Server
Subject
Body
Action
Status

The flow for the code behind page is as follows.

using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Net.Mail;

public partial class _Default : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{

}
protected void btnSubmit_Click(object sender, EventArgs e)
{
try
{

}
catch (Exception ex)
{
litStatus.Text=ex.ToString();
}
}
}

Download the Full Working Version of this Project written with Visual Studio.NET C# 2005 Here!

Measuring the Size of Uploaded Images

noreply@blogger.com (Bishar.B.N) — Fri, 22 Feb 2008 16:08:00 +0000

Introduction

It's not uncommon that you want to check the dimensions of an image that a user uploads to your web site. For example, you may want to check the size of an uploaded banner in an advertising web site, or check the size of an image that is shown in a news article. You could, of course, just allow any uploaded image and resize it on the fly, but in many cases you end up with distorted images because they have been resized with incorrect proportions. So, depending on your requirements, it can be a good idea to check the dimensions of the image, and reject the uploaded file if it doesn't meet your requirements. By checking the dimensions of the uploaded file before it's saved to disk, you save yourself the trouble from deleting the temporary image when it doesn't meet the specifications.

Fortunately, this is all quite easy to accomplish. The code download at the end of the article contains a small web site with a fully working example in both VB.NET and C#. The web site contains a web.config file with two appSettings keys for the required dimensions:

The values for the height and width are arbitrary in the sample application and can easily be changed to meet your requirements. These values are read and stored in private variables in the page when it is posted back (that is, when a file has been uploaded) with the following code (I am showing the C# version here, but you can find similar code for VB.NET in the demo application which you can download at the end of this article):

if (Page.IsPostBack)

{

height = Convert.ToInt32(

ConfigurationManager.AppSettings.Get("RequiredHeight"));

width = Convert.ToInt32(

ConfigurationManager.AppSettings.Get("RequiredWidth"));

}

These values are used to validate the dimensions of the image, which is shown later.

The markup of the demo page contains an control, a Button and a number of validator controls, used to ensure the user has selected a file and to provide feedback about the uploaded file and whether it meets the validation rules.

When the user has selected a file and clicked the Upload button, the following code is triggered:

Page.Validate();

if (Page.IsValid)

{

if (FileUpload1.HasFile)

{

string extension = Path.GetExtension(FileUpload1.PostedFile.FileName);

switch (extension.ToLower())

{

// Only allow uploads that look like images.

case ".jpg":

case ".jpeg":

case ".gif":

case ".bmp":

try

{

if (ValidateFileDimensions())

{

string fileName = Path.GetFileName(

FileUpload1.PostedFile.FileName);

string saveAsName = Path.Combine(

Server.MapPath("~/Uploads/"), fileName);

FileUpload1.PostedFile.SaveAs(saveAsName);

lblSucces.Visible = true;

}

else

{

valInvalidDimensions.IsValid = false;

valInvalidDimensions.ErrorMessage =

String.Format(valInvalidDimensions.ErrorMessage,

height, width);

}

catch

{

// Unable to read the file dimensions.

// The uploaded file is probably not an image.

valInvalidFile.IsValid = false;

}

break;

default: // The uploaded file has an incorrect extension

valInvalidFile.IsValid = false;

break;

}

The code first checks if a file has been uploaded by checking the HasFile property of the FileUpload control. It then proceeds to check the extension of the uploaded file to see if it's an image or not. You can add or remove case blocks to the switch statement to change the type of files that your users are allowed to upload.

When the uploaded file looks like an image, the method ValidateFileDimensions (shown later) is called to check the dimensions of the uploaded image. If this method returns true, the image meets the specifications and it is saved to disk using the SaveAs method of the PostedFile. If the image has incorrect dimensions, the CustomValidator called valInvalidDimensions is shown to the user. Notice how String.Format is used to embed the required height and width into the ErrorMessage of the validator. In the markup, the ErrorMessage property contains two placeholders that are replaced by String.Format to inject the dimensions in the message:

ID="valInvalidDimensions"

runat="server"

ErrorMessage="The image you uploaded has incorrect dimensions.

Please select a file with a height of {0}px and a width of {1}px."

Display="Dynamic"

EnableViewState="false">

The most important part of the sample page is the ValidateFileDimensions method which is remarkably simple:

public bool ValidateFileDimensions()
{
using (System.Drawing.Image myImage =
System.Drawing.Image.FromStream(FileUpload1.PostedFile.InputStream))
{
return (myImage.Height == height && myImage.Width == width);
}
}

This code creates a new Image (3) object by calling Image.FromStream (4) and passing it the InputStream property of the PostedFile. This creates an in-memory representation of the image which exposes properties like Height and Width. Those are then used to check the dimensions of the image against the required height and width fields. The method returns true when the image has the exact same dimensions as specified in the private height and width fields. Otherwise it returns false. When the uploaded file doesn't contain a valid image at all, Image.FromStream raises an exception which is handled in the calling code.

The code contains a using block to ensure that the image is disposed of as soon as it's not needed anymore.

Notice I am prefixing the Image class with its full System.Drawing namespace to avoid name collisions with the Image class from the System.Web.UI.WebControls namespace which is imported by default.

Summary

Checking the dimensions of an image that is uploaded by your users is useful in many situations. Being able to check the image before it's even saved to disk is even better, as it frees you from deleting invalid images after they have been uploaded. With the code from this article you can now perform the validation while the image is still in memory and only save it to disk when it meets your requirements.

Download Files

Source Code for this Article (7) The download contains a working example in both C# and VB.NET.

HTTP 500 - Internal server error

noreply@blogger.com (Bishar.B.N) — Fri, 15 Feb 2008 07:54:00 +0000

When viewing an ASP page in a web browser, visitors see the following error:

HTTP 500.100 - Internal Server Error - ASP
Internet Information Services

Note: The error above was generated using an IIS 5.0 web server running on Windows 2000. The error message may differ depending on your web server.

Reason

The web server is having a problem processing the ASP page. The problem could either be with the ASP code itself, the database connection or the SQL code.

Solution

Please Register the IIS with asp.net using the command prompt of asp.net
cmd>aspnetreg_iis –I this will register the iis with asp.net
also want to know more command type help

Configuring SQL Server Express 2005 for Remote Access

noreply@blogger.com (Bishar.B.N) — Fri, 15 Feb 2008 07:49:00 +0000

Errors connecting to SQL Server Express 2005

Are you getting errors connecting to SQL Server Express 2005 via remote client software and yet have no problem connecting to it on the local machine?

Some of the errors you might be seeing are:

sql server does not allow remote connections
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified
An error has occured while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes Provider,error:40-Could not open connection to SQL Server))
Server does not exist or access denied

If yes, then read on because SQL Server Express 2005 is not automatically configured for remote access during installation. It can be enabled however, so the problems you are having are more of a "feature" than a bug.

Why this page?Well, we too ran into this problem - just as you have now. In recognition of all of the kind help we received from the Internet newsgroups we thought it might be useful to collect the information here so as to provide assistance to others in the same position. If you have any suggestions for updates to this page please let us know.

Here's a quick summary of the actions you need to take. The first three actions have a separate page which provides more details and some screen shots of the procedure.

[Link] Enable the TCP/IP protocol using the Surface Area Configuration Utility
[Link] Make sure the TCP/IP protocol is enabled in the SQL Server Configuration Utility
[Link] Make sure the SQL Server browser is started. Note this step is optional. It is possible to set the SQL Server instance to use a fixed IP address - but this is non-standard for named instances. See sqlexpress's WebLog for details.
Make sure SQL Server and SQL Server Browser are exempted by the firewall on the server machine. This is done by putting sqlservr.exe and sqlbrowser.exe as an exception in the windows firewall.
Note: In order to get things to work. You might need to completely reboot the server machine after making the changes. There have been reports (thanks P.C.) that starting and stopping the SQL Server and Browser software is not enough.

Client software for testing remote connectivity to SQL Server Express 2005

Need some software to test out remote connectivity to SQL Server Express 2005? Probably there are lots of ways. Here are four to try out:

Download and install the SQL Server Management Studio Express Community Technical Preview. SSMSECTP (as it is affectionately known) is a freebie, upgraded and cut down version of the SQL Server 2000 management software. Works pretty well for simple management tasks, has a T-SQL window and, of course, nicely tests out remote connectivity.

To install SSMSE you will need the following (note the 2.0 Beta version of the .NET framework is not acceptable. Uninstall it first if you have it.). It is probably best to install them in the order below

Microsoft .NET Framework Version 2.0 Redistributable Package

Microsoft Core XML Services (MSXML) 6.0

Microsoft SQL Server Management Studio Express - Community Technology Preview (CTP) November 2005

Or try the ADO bare bones Connection tip using .udl files sent in by Kieran H and Dan P.
Or try the client side osql.exe utility with the following command line:

· osql -S SERVERNAME\SQLEXPRESS -U

To use OSQL, start up a Windows command session (Start:Run...:cmd) and type in the above command. On our test machine the OSQL binaries are located in the C:\Program Files\Microsoft SQL Server\90\Tools\Binn directory. If you do not have this directory somewhere it probably means you did not install the client side tools.

So of course now the question is ""how to install the OSQL tool (and others) on the client" Well fortunately it is not too difficult as they are co-located in the same installation package as the SQL Server Express 2005 software. To install them just go back to the same installer you used to create the SQL Server Express 2005 instance on the remote system and run it on your client system. Instead of accepting the default install (which installs the server engine) choose to install only the client side utilities. This will create the above directory and install the tools without installing the database on your client machine.

For further testing you can also dig around a bit and find out how to use the SQLCMD.exe utility.

Or use the following snippet of C# code. Note: If you are using the Visual Studio 2005 environment you might want to read the page entitled Using Visual Studio 2005 to Connect to SQL Servers by Name

· private void button1_Click(object sender,

· System.EventArgs e)

· {

· SqlDataReader rdr = null;

· // 1. Instantiate the connection

· // test by server name instance name

· // SqlConnection conn = new SqlConnection(

· // "Data Source=MYSERVERNAME\\SQLEXPRESS;

· // Initial Catalog=Northwind;

· // User ID=sa;

· // Password=sa");

· // test by ip address, port and instance name

· SqlConnection conn = new SqlConnection(

· "Data Source=123.123.123.123,1066;

· Network Library=DBMSSOCN;

· Initial Catalog=Northwind;

· User ID=sa;Password=sa;");

· // 2. Open the connection

· conn.Open();

· // 3. Pass the connection to a command object

· SqlCommand cmd = new SqlCommand(

· "select * from Customers", conn);

· // 4. Use the connection

· rdr = cmd.ExecuteReader();

· // print the CustomerID of each record

· while (rdr.Read())

· {

· Console.WriteLine(rdr[0]);

· }

· // close the reader

· if (rdr != null)

· {

· rdr.Close();

· // 5. Close the connection

· if (conn != null)

· {

· conn.Close();

· }

· MessageBox.Show("Done",

· "Done",

· MessageBoxButtons.OK,

· MessageBoxIcon.Exclamation);

· }

Again it shows errors please consult with the system admin or the network admin that this will due to prohbition made onthe firewall...