C#B - SHARED SOURCE PROJECT FOR A C# Browser
Let's sort this stuff out once and for ALL.
===============================================================
Anyone who's having problems in the design space "C# WebBrowser
Customization" is welcome to join me on a project to refine, works & shares
the FULL-CODE base for a #C WebBrowser, to put it in CONTEXT, and ANSWER in
PRACTICE many of the questions/problems posted on these news groups.
===============================================================
Here is the - RANT - FLAME - MOTIVE - for this project....
Take a look at the situation doing C# COM INTEROP on SHDocVw.dll, from what
I can see it's a complete MESS.
Partial bits of code from people saying "I haven't tested it, but this
should work". How hard does it have to be?
All the hype with the .NET programming interfaces, but when it comes to
making it work, it sure doesn't feel like 2004.
The commercial companies...
AOL, Encyclopedia Britannica, Microsoft Encarta, Microsoft Outlook,
Microsoft Studio, Qualcomm Eudora, Neoplanet, Custom Browser, Active
Worlds, Intuit Quicken, TopStyle, Allaire Coldfusion, company X, Y, and Z
...have got it worked out (admittedly in C++) but I'm sick of playing the
plumber, shifting around in their muck (little code snippets and crappy
examples) while they rake in the big bucks. How about something that works
for me??
All those UNANSWERED questions on the newsgroups. Where are the examples
that do a bit more than FORWARD and BACK??
What a mess. It couldn't be more regressive -- everyone going through the
same pain, wasting huge amounts of time trying to achieve something that's
been already been done a hundred times before. It seemed so simple (such a
common thing to want)-- hosting a Browser control on a Form -
setting a few properties, handling some events. Why is it still so
obscure?? Save me some time and tell me this SHDocVw COM INTEROP is not just
a poorly wired toy? Where are the real programmers who make things clear,
concise, viable and open for customization for ALL concerned, I haven't seen
their work in this
design space. How about some CODE? COMPLETE, IN CONTEXT AND WORKING.
Otherwise what good is it?
Don't we all have better things to do? Come on let's sort this stuff out
once and for ALL.
Joshua Donnelly
Brisbane Australia
Dave Boal - 02 Oct 2004 19:05 GMT
End of Day 2...all I wanted to do was programically print an Html document.
...I really wanted to load an HTML string into a SHDocVw.Document, then
print it...and that is where the documentation got a little challenging for
me...and I am still unable to do it.
So, I cannot agree more with the comment that documentation is "challenged".
The docs appears to tell me that to Document object is read only. It also
says that the SHDocVw.Document object maps to the mshtml.IHTMLDocument2
(whatever that means...it certainly does not implement or inherit from it).
How am I to gain access to the Document.body?
I hope you are tagged to get responses from this responses from this,
because I would love to talk to you about your experience, and alternate
information sources...
Thanks Dave
> C#B - SHARED SOURCE PROJECT FOR A C# Browser
>
[quoted text clipped - 53 lines]
>
> Brisbane Australia
Colin Priest - 04 Oct 2004 07:22 GMT
I tried and gave up a few years ago. The practical solution for me was
to write my own C++ ActiveX wrapper around the webbrowser object, and
then allow C# to talk to my ActiveX.
>End of Day 2...all I wanted to do was programically print an Html document.
>
[quoted text clipped - 72 lines]
>>
>> Brisbane Australia