Access to internet with VB Express Edition

[Tosco]

I'm new to VB.net and I want to upgrade an application from VB6 to
VB2005.
The VB6 application uses an invisible WebBrowser control to access some
pages and parse the content.
Is there a better way with VB2005?
Nothing wrong with the WebBrowser (besides the memory leaks), but since
I don't need to show any web page content I was wondering if there is a
ligher way.

Thanks,
Stefano

[Cor Ligthert [MVP]]

Robin,

I have tried to avoid these discussions by just removing the link to the
general vb newsgroup.

Maybe is the counterpart that Jeff and others cannot see my answer and the
addition on that from Herfried.

Therefore for those who thinks this question is still open. It is answered
for VB.Net.

Ralph had already given a message about the use of newsgroups, I saw no
reason to repeat that.

Cor

[Tom Shelton]

On 2007-01-01, Tosco <st***********@ gmail.comwrote:

I'm new to VB.net and I want to upgrade an application from VB6 to
VB2005.
The VB6 application uses an invisible WebBrowser control to access some
pages and parse the content.
Is there a better way with VB2005?
Nothing wrong with the WebBrowser (besides the memory leaks), but since
I don't need to show any web page content I was wondering if there is a
ligher way.

I didn't see it mentioned (but I could be worng), but there most certainly is
a lighter way then using the WebBrowser control. Especially, since I believe
I saw further down the thread that these files were not going to be displayed.
The answer lies in System.Net.WebC lient. There is an VB.NET example in the
help files for this class. If you need more specific help, please feel free
to post again.

--
Tom Shelton

[RobinS]

Got it. Thanks for clarifying that for me, Cor.

Robin S.
-------------------
"Cor Ligthert [MVP]" <no************ @planet.nlwrote in message
news:eU******** ******@TK2MSFTN GP02.phx.gbl...

Robin,

I have tried to avoid these discussions by just removing the link to
the general vb newsgroup.

Maybe is the counterpart that Jeff and others cannot see my answer and
the addition on that from Herfried.

Therefore for those who thinks this question is still open. It is
answered for VB.Net.

Ralph had already given a message about the use of newsgroups, I saw
no reason to repeat that.

Cor

[Bob O`Bob]

Tom Shelton wrote:

On 2007-01-01, Tosco <st***********@ gmail.comwrote:

>I'm new to VB.net and I want to upgrade an application from VB6 to
VB2005.
The VB6 application uses an invisible WebBrowser control to access some
pages and parse the content.
Is there a better way with VB2005?
Nothing wrong with the WebBrowser (besides the memory leaks), but since
I don't need to show any web page content I was wondering if there is a
ligher way.

I didn't see it mentioned (but I could be worng), but there most certainly is
a lighter way then using the WebBrowser control. Especially, since I believe
I saw further down the thread that these files were not going to be displayed.
The answer lies in System.Net.WebC lient. There is an VB.NET example in the
help files for this class. If you need more specific help, please feel free
to post again.

But NOT to the NON-DOTNET newsgroups.

Bob
MS MVP, VB 2000-2006
--

[Tom Shelton]

On 2007-01-03, Bob O`Bob <fi*******@yaho ogroups.comwrot e:

Tom Shelton wrote:

>On 2007-01-01, Tosco <st***********@ gmail.comwrote:

>>I'm new to VB.net and I want to upgrade an application from VB6 to
VB2005.
The VB6 application uses an invisible WebBrowser control to access some
pages and parse the content.
Is there a better way with VB2005?
Nothing wrong with the WebBrowser (besides the memory leaks), but since
I don't need to show any web page content I was wondering if there is a
ligher way.

I didn't see it mentioned (but I could be worng), but there most certainly is
a lighter way then using the WebBrowser control. Especially, since I believe
I saw further down the thread that these files were not going to be displayed.
The answer lies in System.Net.WebC lient. There is an VB.NET example in the
help files for this class. If you need more specific help, please feel free
to post again.

But NOT to the NON-DOTNET newsgroups.

I apologize - I meant to set the followups to the .net group. I will try not
to let it happen again.

--
Tom Shelton

[Cor Ligthert [MVP]]

Tom,

Can you disconnect the Microsoft.publi c.dotnet.langua ges.vb group from this
kind of messages.

In my idea does this makes no sense now.

:-))))))))))))))) ))))))))

Cor

"Tom Shelton" <to*********@co mcastXXXXXXX.ne tschreef in bericht
news:nN******** *************** *******@comcast .com...

On 2007-01-03, Bob O`Bob <fi*******@yaho ogroups.comwrot e:

>Tom Shelton wrote:

>>On 2007-01-01, Tosco <st***********@ gmail.comwrote:

I'm new to VB.net and I want to upgrade an application from VB6 to
VB2005.
The VB6 application uses an invisible WebBrowser control to access some
pages and parse the content.
Is there a better way with VB2005?
Nothing wrong with the WebBrowser (besides the memory leaks), but since
I don't need to show any web page content I was wondering if there is a
ligher way.


I didn't see it mentioned (but I could be worng), but there most
certainly is
a lighter way then using the WebBrowser control. Especially, since I
believe
I saw further down the thread that these files were not going to be
displayed.
The answer lies in System.Net.WebC lient. There is an VB.NET example in
the
help files for this class. If you need more specific help, please feel
free
to post again.

But NOT to the NON-DOTNET newsgroups.

I apologize - I meant to set the followups to the .net group. I will try
not
to let it happen again.

--
Tom Shelton

[Tom Shelton]

On 2007-01-03, Cor Ligthert [MVP] <no************ @planet.nlwrote :

Tom,

Can you disconnect the Microsoft.publi c.dotnet.langua ges.vb group from this
kind of messages.

In my idea does this makes no sense now.

:-))))))))))))))) ))))))))

Cor,

I find this whole VB.CLASSIC vs. VB.NET war very tiresome. It has been going
on for years now - with the same old players on both sides. It's rediculous
to the extream. The OP was, IMHO, correct to post to both groups - his
question was about moving from VB6 to VB.NET. It is likely that people on
both sides of the VB fence would have some experience in that move - yet the
anti-dotnet group can't even read anything with the term VB.NET in it without
begining to froth at the mouth.

I realize that they have a few valid concerns - primarily with migrating
existing projects. But, most of their objections, are IMHO, plain silly.
For better or for worse, VB.CLASSIC is a dead product - and has been for years
now. It is time for some people to grow up and move on.

Anyway, sorry to vent. But this sort of bickering about a post that was,
IMHO, completly on topic and correctly cross-posted just takes away from the
spirt of the community.

--
Tom Shelton

[Tosco]

Thankyou for the answer, I will try to use System.Net.WebC lient, it
looks my solution.

I'm starting to use VB.Net because:
- I changed job and the new company doesn't have an old copy of VB6 and
wasn't able to buy a new copy, so now I can only use VB6 illegally;
- The memory leaks of the WebBrowser fatten up my old VB6 application,
and if it runs for hours it grows up to 2GB;
- I want to learn one language of the future (I should say present, I
know I'm late);
- I want to use some features not available in VB6 (without APIs) like
multi-thread applications, etc.

I apologize for bothering some sensitive souls, I shall not repeat.

Ciao,
Stefano

Tom Shelton wrote:

On 2007-01-03, Cor Ligthert [MVP] <no************ @planet.nlwrote :

Tom,

Can you disconnect the Microsoft.publi c.dotnet.langua ges.vb group from this
kind of messages.

In my idea does this makes no sense now.

:-))))))))))))))) ))))))))

Cor,

I find this whole VB.CLASSIC vs. VB.NET war very tiresome. It has been going
on for years now - with the same old players on both sides. It's rediculous
to the extream. The OP was, IMHO, correct to post to both groups - his
question was about moving from VB6 to VB.NET. It is likely that people on
both sides of the VB fence would have some experience in that move - yet the
anti-dotnet group can't even read anything with the term VB.NET in it without
begining to froth at the mouth.

I realize that they have a few valid concerns - primarily with migrating
existing projects. But, most of their objections, are IMHO, plain silly.
For better or for worse, VB.CLASSIC is a dead product - and has been for years
now. It is time for some people to grow up and move on.

Anyway, sorry to vent. But this sort of bickering about a post that was,
IMHO, completly on topic and correctly cross-posted just takes away from the
spirt of the community.

--
Tom Shelton

[RobinS]

If you're new to VB2005, check out Tim Patrick's book, "Start-to-Finish
VB2005". It has a lot of neat stuff in it, and explains things pretty
well.

Another good book is Francesco Balena's "VB2005: The Language". It only
covers the language, not forms or data, though. But it has info about
Multi-threading and Reflection and some of the more advanced topics.

Robin S.
------------------------------
"Tosco" <st***********@ gmail.comwrote in message
news:11******** **************@ h40g2000cwb.goo glegroups.com.. .

Thankyou for the answer, I will try to use System.Net.WebC lient, it
looks my solution.

I'm starting to use VB.Net because:
- I changed job and the new company doesn't have an old copy of VB6
and
wasn't able to buy a new copy, so now I can only use VB6 illegally;
- The memory leaks of the WebBrowser fatten up my old VB6 application,
and if it runs for hours it grows up to 2GB;
- I want to learn one language of the future (I should say present, I
know I'm late);
- I want to use some features not available in VB6 (without APIs) like
multi-thread applications, etc.

I apologize for bothering some sensitive souls, I shall not repeat.

Ciao,
Stefano

Tom Shelton wrote:

>On 2007-01-03, Cor Ligthert [MVP] <no************ @planet.nlwrote :

Tom,

Can you disconnect the Microsoft.publi c.dotnet.langua ges.vb group
from this
kind of messages.

In my idea does this makes no sense now.

:-))))))))))))))) ))))))))

Cor,

I find this whole VB.CLASSIC vs. VB.NET war very tiresome. It has
been going
on for years now - with the same old players on both sides. It's
rediculous
to the extream. The OP was, IMHO, correct to post to both groups -
his
question was about moving from VB6 to VB.NET. It is likely that
people on
both sides of the VB fence would have some experience in that move -
yet the
anti-dotnet group can't even read anything with the term VB.NET in it
without
begining to froth at the mouth.

I realize that they have a few valid concerns - primarily with
migrating
existing projects. But, most of their objections, are IMHO, plain
silly.
For better or for worse, VB.CLASSIC is a dead product - and has been
for years
now. It is time for some people to grow up and move on.

Anyway, sorry to vent. But this sort of bickering about a post that
was,
IMHO, completly on topic and correctly cross-posted just takes away
from the
spirt of the community.

--
Tom Shelton

[Cor Ligthert [MVP]]

Tom,

Are you writting this as reply to me. Tom it seems that I write not enough
in these newsgroups.

Otherwise you would see me smile if I see this kind of childness which we
have seldom in the dotNet newsgroups.

Cor

"Tom Shelton" <to*********@co mcastXXXXXXX.ne tschreef in bericht
news:QP******** *************** *******@comcast .com...

On 2007-01-03, Cor Ligthert [MVP] <no************ @planet.nlwrote :

>Tom,

Can you disconnect the Microsoft.publi c.dotnet.langua ges.vb group from
this
kind of messages.

In my idea does this makes no sense now.

:-))))))))))))))) ))))))))

Cor,

I find this whole VB.CLASSIC vs. VB.NET war very tiresome. It has been
going
on for years now - with the same old players on both sides. It's
rediculous
to the extream. The OP was, IMHO, correct to post to both groups - his
question was about moving from VB6 to VB.NET. It is likely that people on
both sides of the VB fence would have some experience in that move - yet
the
anti-dotnet group can't even read anything with the term VB.NET in it
without
begining to froth at the mouth.

I realize that they have a few valid concerns - primarily with migrating
existing projects. But, most of their objections, are IMHO, plain silly.
For better or for worse, VB.CLASSIC is a dead product - and has been for
years
now. It is time for some people to grow up and move on.

Anyway, sorry to vent. But this sort of bickering about a post that was,
IMHO, completly on topic and correctly cross-posted just takes away from
the
spirt of the community.

--
Tom Shelton