I know this is repeated question. I read almost all the threads , googled a lot and became more confused. I read Microsoft Mobile Internet Toolkit (MMIT) is not used anymore and Windows Mobile 6.5 Developer Tool Kit is widely used .
Requirement:Develope and publish websites for mobile phones.
Envoirnment:VS2008/.net 3.5
I am new to mobile web application development. I want to know how to start ,what are the frameworks i should know/download,sample websites or articles..
Thanks,
Vanitha
If you want to create web applications for mobile devices using microsoft technologies check out this site:
http://www.asp.net/mobile
It has simple how-to.....
If you're going to invest in a new skill, I'd focus on iPhone and Android development - they're far more widespread than windows mobile.
Related
I would like my Windows store app (Windows 8 + Windows rt) to integrate real time voice conversation with other users of the app (aka VoIP). Are there any in-app communication solution or SIP client for this?
I know about a solution for Windows Phone 8, but I'm looking for a solution for Windows 8/RT:
http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj206983.aspx
I would be able to host a server (FreeSwitch for instance) and to pay for a product if needed. My conditions is it integrates in a Windows store app (compatible WinRT).
I am pretty sure you've already looked over the Windows 8 Real-time communication sample!?
If you've already checked it out please share your experience with it. I am trying to use it for a video-chat functionality of my app, but this sample is "not very mature" - to put it mildly. Good luck with your voip solution!
I want to evaluate the new sandboxing mechanism in Windows 8/Windows Server 2012. I searched MSDN site for any resources but the documentation is extremely scarce. In comparison with FreeBSD Capsicum documentation, the one provided by Microsoft is just unusable.
How are we supposed to build robust sandboxed apps? Are the sandboxing APIs intended for metro style apps only?
I'm not sure what you mean by "sandboxing APIs". All "metro" (Windows 8 UI Applications) are sandboxed. I'm not aware of any way to sandbox desktop applications in the same way. See here.
Metro apps are pretty tightly sandboxed, and apps submitted to the
Windows Store need to declare many types of capabilities that they use
— not unlike Google Play's permissions list.
. . .
Windows 8 features a specific SDK for Metro style apps . . .
A quick explanation of capabilities: There are certain potentially sensitive things that you can do on a user's machine, such as access the Pictures library or use the webcam. If an app wants to do these things, the developer must declare a capability in the app's manifest. Then, when users download the app from the Windows Store, they can clearly see if the app is using any of this functionality. More info and a list of all of the capabilities is provided at App capability declarations.
Regarding sandboxing, there is some information at http://msdn.microsoft.com/en-us/library/ie/hh673561(v=vs.85).aspx. Yes, Metro-style apps are sandboxed in a way that desktop apps are not.
There is a whitepaper discussing security in Windows Store apps built with HTML5 at Secure development of Metro style apps with HTML5. There are also some common security scenarios documented.
I realize it's been asked countless times whether iPhone apps can be built in Windows and that the simple answer is no, with workarounds such as using VM or even something like Dragon SDK which requires the app to be written in C/C++, but I would like to build an app using Objective C.
My question is can the code for an iPhone app not be developed on a Windows computer, uploaded to a remote Mac computer, compiled on the Mac, and then downloaded back to Windows to install via iTunes? I don't want to buy a Mac mini to get my feet wet with iPhone development, but I don't want to be limited to writing an HTML 5 app using Phone Gap or similar.
If nothing else, wouldn't it be possible to develop the app directly on a remote / virtual Mac using a remote desktop connection?
If either of these are possible, does anyone know of a company offering such a service? If not, what would be a likely reason that it hasn't been created? It seems like there would be enormous demand.
Perhaps http://www.macincloud.com/ is what you are looking for.
I believe what you're trying to do is not possible but how about MonoTouch ?
http://xamarin.com/monotouch
Using .NET on Windows technologies to develop iPhone and other apps ?
I need to connect a symbian mobile to my application to do a transfer of information between my vb.net windows application and my mobile
i'm looking to have a software on the mobile side to send the information
can any one help me with this issue
Please refer to Nokia PC Suite Connectivity API for such tasks.
at first i thought with Titanium, i can develop for Mobile and Desktop over AIR on Desktop only, but a quick look at the AIR Site, i guess i am wrong.
Benefit from a consistent, flexible,
and visual development environment for
applications on multiple platforms and
devices such as smartphones,
smartbooks, tablets, netbooks, and
PCs.
so my question is are there any major differences of titanium over air that i shld be aware of?
if no, i guess now air maybe better documented and has the backing of a more recognized company? after working with titanium desktop for a while i felt abit helpless and the docs are not really helping much
There are a lot of subtle differences, of course, and there are advantages and disadvantages to working in either, but the largest difference is that Titanium can produce apps for the iPhone/iPad, and AIR can't (well, at least not conveniently).
AIR can produce iPhone apps that you can deploy using the ad-hoc provisioning, but you can't distribute via the app store.
I've got desktop apps on both and am making a mobile app right now. Titanium desktop will cut your dev time to 1/3 of the time you'll take jumping through AIRs various sandboxes and security measures. Best yet, the code I wrote for my Ti desktop app is all javascript with about 3 Ti API calls and can be taken anywhere. The AIR app is all mangled by the wild structure you have to use with AIR apps and 1 million api calls.
The downside to Ti desktop is the API isn't as fully featured, and the Ti team pushes 4 times as many updates for the mobile API as the desktop API. Also, you won't be able to port your app from desktop to mobile easily as they are two different structures and APIs.
That said, developing for iPhone and Android on Ti is the same exact process and that won't happen on AIR.
Lots to weigh, but for my money it's Ti over AIR.
Hope this helps.