I really hope that the problem that I am facing is caused by my lack of experience on the Symbian platform (Windows Mobile developer) and with Carbide.c++ itself. I can't accept that this Symbian and Carbide.c++ are so poorly designed!
I am working on a simple application that at the moment uses the web client to get the content of a web page. Everything works great in the emulator.
Now on the actual device (N73). The application installs ok (with warning message) and when I press the menu item to do IssueHTTPGetL() it says "unable to execute file for security reasons". Ok... it must be a selfsign and capability issue. In my MMP file I add NetworkServices. I run the capability scanner and it says:
"Platform Security Scan Results
* These capabilities were detected in your source code:
* These capabilities are defined in your project settings:
* You may need to add these capabilites to your project settings:
** DEPENDENT capabilities indicates that particular APIs can have different capabilities depending on runtime context. It is not a defined capability." My God... did you ever heard of something more vague then the last sentence?
Anyway... from the project properties if I add a password in the sis file creation window for the self signed radio button, after pressing build the error message is: "signsis.exe returned with exit value = 1". If I don't enter anything in the password field then the .sisx file is created. The application won't connect to the http server from the phone. www.whythefuckwontmysisfileinstall.com says that there are no capabilities... Ok... I tried manually signing the application with the same result both on the phone and on the above mentioned site.
My guess is that it has something to do with the UID? This is pasted from the mmp file: UID 0x100039CE 0xE94E7E10.