ASP.NET

Re: Extract text from webpages

19-Jul-06 3:52

Hi,
I am developing a webcrawler/webspider in C#.Net 2005, I am extracting text from web pages through the code below. But the problem is that it only extract text from html pages because asp.net pages does not contain headers like

…

. So how I extract text from asp.net & php pages.

Code for extracting text from html web pages
S is string which contains the webpage

MatchCollection mPage = Regex.Matches(s, @"((

|

)\s.+\s(

|||||))", RegexOptions.IgnoreCase);
foreach (Match mP in mPage)
{

StreamWriter i = new StreamWriter(@"C:\WebSpider\index.txt", true);
i.Write(mP.Groups[0].Value.ToString() +"\t"+ u +"\n");
i.Close();
}

Not Active19-Jul-06 4:02

Extract text from web pages

19-Jul-06 4:02

Posting the question once is enough Mad | :mad:

asif sharif19-Jul-06 3:51

Extract Text from web pages

19-Jul-06 3:51

…

. So how I extract text from asp.net & php pages.

Code for extracting text from html web pages
S is string which contains the webpage

MatchCollection mPage = Regex.Matches(s, @"((

|

)\s.+\s(

asif sharif19-Jul-06 3:46

Extract Text from asp.net/php/html pages

19-Jul-06 3:46

…

. So how I extract text from asp.net & php pages.

Code for extracting text from html web pages
S is string which contains the webpage

MatchCollection mPage = Regex.Matches(s, @"((

|

)\s.+\s(

asif sharif19-Jul-06 3:44

Re: Problem with dynamic tag

19-Jul-06 3:44

…

. So how I extract text from asp.net & php pages.

Code for extracting text from html web pages
S is string which contains the webpage

MatchCollection mPage = Regex.Matches(s, @"((

|

)\s.+\s(

Spell Check.

Vipin Venugopal19-Jul-06 3:44

Vipin Venugopal

19-Jul-06 3:44

Hi Friends,
Can anyone tell me how can we implement spell check in a web application. My problem is that i have a text area. what all words i enter there should be checked for its correctness.

Vipin

Re: Spell Check.

mnaveed19-Jul-06 4:48

mnaveed

19-Jul-06 4:48

check this

http://www.codeproject.com/asp/spell_check.asp[^]

Nav.

Problem with dynamic tag

hasanali0019-Jul-06 3:37

hasanali00

19-Jul-06 3:37

Hi
In my Web Form, I have this code:
<code><HEAD>
<title id="title" runat="server"></title>
</Head></code>

Then in the code-behind file, I set the title of the page dynamically.

My problem is that sometimes, my web form deletes runat="server" property from the <title> tag automatically. Because it deletes the runat property, my page stops working. I manually have to add runat="server" into the <title> again.

So please tell how I can solve this problem.

Thanks

eggsovereasy19-Jul-06 7:11

eggsovereasy

19-Jul-06 7:11

Just do this in the code behind:

<br />
this.Page.Title = "Your Title Here";<br />

Re: Problem with dynamic tag

Mircea Grelus19-Jul-06 9:16

Mircea Grelus

19-Jul-06 9:16

Or you could do this:
<head>
<title><%= pageTitle %></title>
<head>
and in your codebehind define pageTitle as protected and assign it in the Page_Load event: pageTitle = "the title of my page";

regards,
Mircea
Many people spend their life going to sleep when they’re not sleepy and waking up while they still are.

how to bound a context menu to table rows in ASP.NET

antontj19-Jul-06 3:29

antontj

19-Jul-06 3:29

Any one please help me to add context menu to a table row. And the menu should not come when right clicking other parts of the page.

Re: how to bound a context menu to table rows in ASP.NET

mnaveed19-Jul-06 5:39

mnaveed

19-Jul-06 5:39

this might help Confused | :confused:

http://msdn.microsoft.com/msdnmag/issues/05/02/CuttingEdge/[^]

Nav.

Exception handling

honeyman_can19-Jul-06 2:43

honeyman_can

19-Jul-06 2:43

Why is it necessary to implement try catches in your source code when there is already page-level and application-level error handling? To me it sounds a bit redundant.

In the page-level and application-level error handling I log the errors (and InnerExceptions) in the DB, email and the event logger.

Thanks

Fuze

Not Active19-Jul-06 3:25

19-Jul-06 3:25

It is good practice to handle exceptions as close to the source as possible. This gives you the opportunity to handle the exception in an intelligent way and resume work if appropriate. If you wait to catch it at the page or applicaiton level it may be too late.

Colin Angus Mackay19-Jul-06 3:30

Colin Angus Mackay

19-Jul-06 3:30

Mark Nischalke wrote:
It is good practice to handle exceptions as close to the source as possible.

I'd say not. It is good practice to handle errors where it is practical to handle errors regardless of the distance from the source. In my experience, if you handle exceptions too soon you end up writing code that is too defensive and that can actually hide bugs.

Mark Nischalke wrote:
If you wait to catch it at the page or applicaiton level it may be too late.

Absolutely! It is definitely too late to do anything but log the exception at that point.

Scottish Developers events:
* .NET debugging, tracing and instrumentation by Duncan Edwards Jones and Code Coverage in .NET by Craig Murphy
* Developer Day Scotland: are you interested in speaking or attending?
My: Website | Blog

Not Active19-Jul-06 4:00

19-Jul-06 4:00

Colin Angus Mackay wrote:
writing code that is too defensive and that can actually hide bugs

Agreed. As with anything the trick is know when and how to use the tools you have. What I meant was not to just bubble the exception back up the call stack when it can be handled at the source, especially in the case of a class library. If I can recover from an exception in my library I don't want to make it the responsibility of the calling application.

honeyman_can19-Jul-06 4:13

honeyman_can

19-Jul-06 4:13

Lets say if you accessing a webservice to retrieve party information and that causes an exception what is the most logical thing to do once it is caught? Im logging them at page and application level. Do I just revert the customer back to that same page where the error occurred and lot it or do I transfer the user back to the homepage and log it. Excuse my ignorance Im a novice with regard to error handling. Thank you

Fuze

Not Active19-Jul-06 4:29

19-Jul-06 4:29

How you handle it depends on the application. Without know how your app is desinged to function I would say to return the user to the page with some message indicating what has happened, i.e "Invalid data", "No record found", etc. Give them a chance to correct any entries. If there is nothing for them to correct, then possibly it would be appropriate to return the to the home page.