Welcome to the Official BlackBerry® Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

Web and WebWorks Development

Reply
New Developer
bkuhn
Posts: 3
Registered: 11-18-2009

Simulators and VS2008

I've installed several Blackberry simulators on my XP box (9630,8300,8310,8320 and the Default Blackberry Widget Simulator 9500).

 

I'm trying to develop a website for a client who insists on using the Curve Blackberrys, which apparently the 8300 series.(?).

 

In Visual Studio 2008, in the Tools/Options/Blackberry section, I can only choose the Blackberry Widget Simulator 9500 as a browser. If I click on the link to see a list of installed simulators I see all the others that are installed, but apparently the others do not have Browser Web Page debugging capability..?

 

The obvious workaround is to debug my website using a real browser and then manually light off one of the simulators and browse to the page (specifying the port # for the ASP.NET development server).

 

Doesn't work. When I try to browse to the page in the simulator (such as http://localhost:4229/Blackberry_Web/Default.aspx) I get an "HTTP Error 403: Forbidden error. You are not authorized to view this page. Please try loading a different page" message. I've tried substituting localhost with IP address and machine name.

 

I have to test from my development environment.

 

Real browsers have no problem with this.

 

I am running MDS Services simulator 4.1.2 since apparently that is needed for internet access.

 

Is there a way for me to test web apps with an 8300 series Blackberry? I need to let my customer know whether we proceed with Blackberry or move to a Windows smartphone.

 

 

 

 

Please use plain text.
BlackBerry Development Advisor
tneil
Posts: 3,555
Registered: 10-16-2008
My Carrier: Rogers

Re: Simulators and VS2008

It may be having an issue with the "localhost" that is being used in the url.  Can you try using the fully qualified domain name of the computer you are accessing?

Tim Neil
Director, Application Platform & Tools Product Management
Follow me on Twitter
Please use plain text.