Questions that baffled me

Here you go.... https://www.youtube.com/watch?v=QETUuZ27N0w

http://en.wikipedia.org/wiki/FFmpeg   Cross Compiling it for iOS https://blog.fh-kaernten.at/wehr/?p=1764   Cross Compiling it for Android http://stackoverflow.com/questions/9605757/using-ffmpeg-with-android-ndk  

Maintainability – In future they will need two skill set people with classic ASP and .NET. Code base – As a part of maintainability also as the .NET code  base is lesser in size typically Performance - Classic ASP is using Inline Queries. We are planning to use entity framework and that performance is good. Outdated technology- No object orientation concepts in ASP and .NET code is more structured and modular Security- SQL injection has been implemented in current codebase using ASP but you are never sure. Newer frameworks are always more secure. Browser Support - Browser support is limited in ASP. Browser compatibility has to be sorted out with many workarounds. Faster Development time – Future enhancements will be faster as in ASP you have to build a lot of functionality yourself, where as in .NET has in build feature

Thanks to our friend Parimal to have sent this.   Default URL Schemes provided by Apple https://developer.apple.com/library/ios/featuredarticles/iPhoneURLScheme_Reference/Introduction/Introduction.html   Inter-App Communication using Custom URL Schemes https://developer.apple.com/library/ios/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/Inter-AppCommunication/Inter-AppCommunication.html   Examples: http://blog.mobiloitte.com/deep-linking-101/ http://blog.originate.com/blog/2014/04/22/deeplinking-in-ios/    

Here is a good link on SO http://stackoverflow.com/questions/155964/what-are-best-practices-that-you-use-when-writing-objective-c-and-cocoa