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

 

[Tosco]

I think that this page would help me, but I'm not able to find the
example.
How can I download the mentioned files?

 

[Ralph]

I think that this page would help me, but I'm not able to find the
example.
How can I download the mentioned files?

--
<response type="generic" language="VB.Net">
This newsgroup is for users of Visual Basic version 6.0
and earlier and not the misleadingly named VB.Net
or VB 200x. Solutions, and often even the questions,
for one platform will be meaningless in the other.
When VB.Net was released Microsoft created new newsgroups
devoted to the new platform so that neither group of
developers need wade through the clutter of unrelated
topics. Look for newsgroups with the words "dotnet",
"framework", or "vsnet" in their name.

For the news.microsoft.com news server try these:

news://msnews.microsoft.com/
microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb
microsoft.public.dotnet.languages.vb.upgrade
microsoft.public.dotnet.languages.vb.controls
microsoft.public.dotnet.framework.windowsforms.controls
microsoft.public.vsnet.general
microsoft.public.vstudio.general
microsoft.public.dotnet.framework.aspnet....
</response>

 

[Cor Ligthert [MVP]]

Ralph,

In VB6 and VB.Net 2002/2003 was the interop AXWebbrowser used.
In VB.Net 2005 is integrated the Net Class Webbrowser.

Be aware that it are still interops to Interenet Explorer. The webbrowser
class has a little bit less events as the AXWebbrowser, however it has more
properties to manipulate the document.

One problem I have is that you cannot do anymore download complete, however
Herfried has put in this newsgroup nice code to overcome that.

Cor

 

[RobinS]

--
<response type="generic" language="VB.Net">
This newsgroup is for users of Visual Basic version 6.0
and earlier and not the misleadingly named VB.Net
or VB 200x. Solutions, and often even the questions,
for one platform will be meaningless in the other.
When VB.Net was released Microsoft created new newsgroups
devoted to the new platform so that neither group of
developers need wade through the clutter of unrelated
topics. Look for newsgroups with the words "dotnet",
"framework", or "vsnet" in their name.

For the news.microsoft.com news server try these:

news://msnews.microsoft.com/
microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb
microsoft.public.dotnet.languages.vb.upgrade
microsoft.public.dotnet.languages.vb.controls
microsoft.public.dotnet.framework.windowsforms.controls
microsoft.public.vsnet.general
microsoft.public.vstudio.general
microsoft.public.dotnet.framework.aspnet....
</response>

Ralph -- he posted it to both groups -- both .Net and VB6andUnder.

Robin S.

 

[mayayana]

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?

You can find a much lighter way here:
http://www.jsware.net/jsware/vbcode.php3#htp

It uses the Windows Winsock library wsock32 to
fetch via http on Win95 and up with no dependencies.
I have no idea whether it works on VB.Net. If you want a
specifically-VB.Net answer then don't post it to
a VB newsgroup.

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.

If you're "upgrading" to VB.Net then why worry
about bloat and "memory leaks"? You're going
to be saddled with 70 MB of runtime being loaded.
You can't do that a "lighter way", so there's not
much point being concerned about relatively minor
sloppiness like loading a whole instance of IE just to
download a webpage.

 

[Jeff Johnson]

Ralph -- he posted it to both groups -- both .Net and VB6andUnder.

Then the proper response would be "please do not crosspost to both .NET and
non-.NET newsgroups."

 

[RobinS]

Then the proper response would be "please do not crosspost to both
.NET and non-.NET newsgroups."

Well, he was talking about moving something from VB6 to VB.Net, so
I could understand why he cross-posted it. He was probably hoping
that someone who had moved from VB6 to .Net could help, although
why he thinks they would be lurking in the VB6 newsgroup is a
mystery. At least he cross-posted it instead of multi-posting it.

Robin S.

 

[Herfried K. Wagner [MVP]]

In VB6 and VB.Net 2002/2003 was the interop AXWebbrowser used.

Well, as VB6 was actually COM-based, no "interop" was required ;-).
However, you are right, .NET 2.0 comes with a wrapper around the original
classes which simplifies its usage.

 

[Ralph]

You can find a much lighter way here:
http://www.jsware.net/jsware/vbcode.php3#htp

It uses the Windows Winsock library wsock32 to
fetch via http on Win95 and up with no dependencies.
I have no idea whether it works on VB.Net. If you want a
specifically-VB.Net answer then don't post it to
a VB newsgroup.


If you're "upgrading" to VB.Net then why worry
about bloat and "memory leaks"? You're going
to be saddled with 70 MB of runtime being loaded.
You can't do that a "lighter way", so there's not
much point being concerned about relatively minor
sloppiness like loading a whole instance of IE just to
download a webpage.

LOL

 

[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]

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.WebClient. 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.

 

[RobinS]

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

Robin S.

 

[Bob O`Bob]

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.WebClient. 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]

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.

 

[Cor Ligthert [MVP]]

Tom,

Can you disconnect the Microsoft.public.dotnet.languages.vb group from this
kind of messages.

In my idea does this makes no sense now.

))))))))))))))))))))))

Cor

 

[Tom Shelton]

Tom,

Can you disconnect the Microsoft.public.dotnet.languages.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.

 

[Tosco]

Thankyou for the answer, I will try to use System.Net.WebClient, 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

 

[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.
------------------------------

 

[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