Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
WebBrowser control not the same from VFP to .NET
Message
From
21/10/2004 16:32:44
Mike Sue-Ping
Cambridge, Ontario, Canada
 
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Environment versions
Visual FoxPro:
VFP 8
OS:
Windows 2000 SP3
Miscellaneous
Thread ID:
00953427
Message ID:
00953495
Views:
18
Hi Rod,

I tried your suggestion and it didn't seem to help. I get the same error. What I'm curious about is the following:

In VFP, intellisense cuts out after thisform.oBrowser.Document. The same is true for C#. VFP compiles and runs perfectly. C# won't compile without the error.

My question is, how does C# know what the content of my HTML document is when I don't have it displayed in the browser during development time. How does it know that "frames" is not valid? It is when the HTML is navigated to at runtime!


Thanks for any assistance.

Mike



>My bet is taht in C# you should use the square brackets [] instead of parens ()
>
>Rodman
Previous
Reply
Map
View

Click here to load this message in the networking platform