Problem with Browser object in C#

[Carl00]

OK.. i have a weird problem.

I made a C# program which uses the Browser Object contained in .Net (i assume this creates an instance of an IE browser)

Now, it loads webpages perfectly on my PC, however when i run the program on any other pc , the browser always shows "the page can not be displayed"
Strangely though, if you use IE standalone, it works perfectly.

I even disabled all firewalls and installed the latest version of IE, but it still shows the same error message.

I dont understand this.. are there some settings required?

ps. .Net framework 3.5 is also installed on all Pcs.. program loads/works perfectly, except for teh browser part..

[wreckedcarzz]

Make sure you are using all needed Includes (just a thought) and that the settings for the browser are not hard coded to your PC (mistakes happen)... just some thoughts (I do VB .NET, not C#, but same OOP system),

And yes, it uses the version of IE present on the computer.

[Carl00]

I haven't coded in any extra settings / properties.. its just the default browser object. All im doing is navigating using the inbuilt webbrowserobj.Navigate("www.blahblah.com" ); function


What includes? I assumed everything would be in the .net framework? Am I missing something?

[app103]

Not sure how you are transferring the files to another pc, but try this:

• Right click the .exe file in Explorer and select properties.
• See if there is a button that says "Unblock" right below the Advanced button on the General tab.
• If there is, click it and then click Apply and then OK.
• Try your file again and see if it works.

If that doesn't work, make sure there isn't a "#" character in the file's path. If there is, change it.

[Carl00]

Thanks for your replies guys,
I figured out the problem though it doesnt make any sense logically..

I set the property "ScriptErrorsSuppressed" = true; and it worked fine.

Doesnt make sense why i couldnt browser at all without that, considering it worked fine on my PC.

[wreckedcarzz]

At least you got it resolved, though!