I am working with a platform on ASP.net that does not have a native mobile version.
I am tasked with debugging a problem that is only for mobile users however searching the codebase for "mobile" or "useragent" does not return anything meaningful that I can use to reverse engineer to find the root problem. It appears that the only mobile checks on the platform are from jQuery regex checks against the useragent and are very very minimal checks to disable a button and not set any global or local variables.
I have tried using Chrome's Mobile Simulator but it seems that only changes the screen resolution rather than simulate a real mobile device. I have also tried modifying the user agent using browser extensions to no avail.
How can I force my desktop browser to load the mobile version of the website for debugging?
Where does ASP.NET determine the device type at?
I have recently completed the workflow described on the Capacitor website to convert my react app to a mobile web app for iOS.
It's a really impressive tool, but I've noticed some small differences in the way the Mobile and Web apps render (see picture below). You can see the Mobile App in the simulator on the left, the Web App in a browser in the centre, and developer tools on the right.
Does anyone know why such differences arise? Is there any way to debug this? I can't tell what in the CSS might be causing the layout differences, so am having to revert to trial and error and am not getting anywhere that way.
You can see and grab the code from my sandbox here.
I am debugging some network issues in a desktop application that makes requests to a service using RestSharp. The actual problem is failing authentication to the service in some limited scenarios, although that is really not relevant to my question.
I have been using Fiddler4 but that has not helped. I wondered if the network tool in Visual Studio 2015 might give some other light on the problem.
https://blogs.msdn.microsoft.com/visualstudio/2015/05/04/introducing-visual-studios-network-tool/
However, when I start the performance profiler the Network tool is grayed out and in the list of 'Not Applicable Tools' (incidentally my menu structure is somewhat different to the screen shot shown in the link above.)I wondered if my Professional Edition does not have the tool enabled, but research on the Microsoft site does not seem to give any information about that. The word 'network' does not appear on this page
https://www.visualstudio.com/vs/compare/
Can anyone tell me what I need to do to access the network diagnostic tool to monitor my application ?
At the moment, the tool only works with the WinRT client. Is that what you are using?
Referring to the comment at the link you provided:
Operations made using the old .NET HttpClient API aren’t captured.
I am trying to build a simple app using tidesdk , but unfortunately as stated here :
https://stackoverflow.com/a/14207566/1724929
that currently there is no way to protect the source code which is visible to the app users.
but after taking a look at wunderlist for Windows which is built using tidesdk and .net framework , i saw that the source code is not visible also i searched if it were hidden somewhere but i found nothing , so any one have an idea how they protect the source code from being visible . is there any tool or something to achive that ?
Latest version of Wunderlist is not built using TideSDK. They have re-implemented all different versions pure natively on each platform they are supporting.
TideSDK currently does not support Code hiding however the Developers of TideSDK are developing TideKit which is releasing soon with a new CLI, app and will provide platform builds. It will also provide Code Hiding. You can follow recent developments at http://www.tidekit.com. The video of what is coming is here: http://youtu.be/aE7gN-d0GhU. This will give you modern tools to use where the experience of creating and your projects is much better.
Can a Flex application that was designed for use on a PC be run on an iPad, iPhone, or Android-based mobile device?
Seems like a simple enough question. Visiting http://www.adobe.com/products/flex.html yields a picture of a dude running a (presumably) Flex application on an Android. So at first glance, the answer would appear to be "yes." End of story.
but yet…
There is so much (mis)information out there on various tech sites that suggest Flash-based technologies simply won't run on iOS or other mobile platforms. Why is this? Perhaps they mean to say that Flex won't run "out of the box" and requires a plugin? Or do they mean it won't run at all?
Every time I think I've reached a definitive conclusion, some post on SlashDot or CNET directly contradicts it. So what's the scoop? Can one take an existing Flex application and run it on iOS/Android? (I realize there are screen size issues to consider so the app might not run effectively. I just want to know if the runtimes are available on the mobile devices to allow the Flex app to launch at all.)
Sorry for the noob question. My background is WPF / HTML5. Adobe technologies are completely foreign to me.
I wrote a lot below if you'd like to read it enjoy, if not sorry for taking your valuable bytes :) I directly answered the questions up here first:
Why is this?
It's a confusing matter read below for the why details.
Perhaps they mean to say that Flex won't run "out of the box" and requires a plugin?
Or do they mean it won't run at all?
Using the flash builder tools (the bin folder in the SDK) you can compile for native desktop application, desktop web browsers, native iOS application, native Android application. Android with FlashPlayer plugin installed will show Flash content within the web browser, iOS will only run the ones compiled with AIR, not in the the web browser but as a native app.
Every time I think I've reached a definitive conclusion, some post on SlashDot or CNET directly contradicts it. So what's the scoop? Can one take an existing Flex application and run it on iOS/Android?
Yes, if using AIR and run as a native app on all three platforms (the desktop Flex API is for the most part a superset of the web Flex API), your other points about performance and form factor are valid and should be considered though. The nice thing is you can write your model/controller code in a common library in AS3 then write separate presentation layer interfaces that all share the library.
Here's the very long version:
Using the flash compiler results in "bytecode" in the form of a file with a swf extension using the swf format, you can read a ton more about that here:
http://www.adobe.com/devnet/swf.html
To interpret the file you need some sort of run-time similar to some degree to running WPF/XAML/C# within a .NET framework context (either desktop or using silverlight on the web). In the case of adobe technologies (rough equivalence):
AS3 = C#
MXML = XAML
Flex = WPF+WCF (client side RPC not server side)
Flash Player = Silverlight
AIR (Adobe integrated runtime) = .NET
Framework Redistributable .dll(s)/.so(s) for desktop OSes
(Read this list very loosely please, I know XAML is preserved in the MSIL or whatever which is different because MXML is compiled to AS3 and only if a debug flag is set on the compiler does it include the debugging symbols, there's certainly tons of differences but I think this is an easy and correct enough model to use)
On iOS the browser does not allow for plugins in the traditional sense of netscape browser plugins or ActiveX plugins. For this reason you'll not be able to execute a plugin ie flashplayer or silverlight in the browser. Since Adobe did release a flashplayer for Android devices that does run in the browser it will work on those devices in the browser, however they have essentially thrown in the towel for supporting this long term, as they have to support the majority mobile device platform, iOS, in order to remain relevant (this was I think more a collective throwing in of the towel by Google, device manufacturers, carriers, Microsoft, all just following suit and trying to make the best business decision, WebKit and V8 or SpiderMonkey can probably do 99% of what Flash can do and better in some cases and WebKit will hopefully not splinter and will remain open source... frameworks and the browsers just need to get fleshed out and stabilized).
If the user installs AIR (or the runtime is packaged with the app) then a Flex/Flash (that is stuff coded in AS3 and/or MXML and compiled to a swf) can be transcoded/packaged to be interpreted by the run-time for that device correctly (be it iOS or Android or whatever RIM did, I don't think they have AIR for Windows Phone 7 and Win8 on ARM won't support browser plugins either). Part of the confusion is possibly from the fact that Apple denied the distribution of Apps that were "cross-compiled" which kept AIR out of the list of options for iOS for a good year, just after Adobe started announcing it was usable for that purpose (kicking Adobe while their down). Another part of the confusion probably comes from real vids of people who have 1 hacked their device or 2 were able to get open source alternatives to the flash player run-time to work on their iOS device (gnash was one I'm aware of from some occasional Linux tinkering, also possibly FAKE vids).
You can run Flex applications on mobile devices, but you cannot simply run any Flex project.
In Flash Builder ( Flex Ide) or in Flash Professional you can create mobile projects. These projects generate native applications for iOS and Android.
Last time I tried, the result and the available components where less than what I expected. So, if you can, I'll much recommend you go for something like Appcelerator.com or similar, which turns HTML5/Js code into native apps. I tried them, worked a lot better than Flex.
Short answer: No
Long answer: You can use Adobe's tools to compile your Flash/Flex app for use as a native iOS app. So you won't be able to embed the app in a web page like you normally could with Flex, but you can build it as a native app. Note you have to have Flash Builder 4.5 to do this.
It won't run on iPhone as a .swf file, but it will run on Android based devices that have adobe flash installed. It will also run on the BB playbook, which also has flash.
Flex is a framework.( Anyway it is very beutiful one which even sometime looks like complete different language ).
As soon as you are building AIR application it can run on various platforms like : Windows, iOS, Android, upcomming TV's, PlayBook, even .. into the future ( maybe/hopefuly ) on Windows Phone, plus Linux ( which AIR future is not very clear anyway ( but hopefuly Adobe will reconsider ) ).
So - application created with Flash Builder 4.5+ would probably run everywhere as soon as it is AIR application.
The compilation methoods is really simple, and you almost simultaneously compiling for everything you wanna to.
And one of the most important things here - your applications will run, work, look and feel the same way you were designed on one device. Flex is the thing which is responsible for everything to looks beutiful on each platform it is running.
For instance i am compiling currently for Android, and without even test i can clearly say that it will looks and feel the same way under iOS and Windows, and it will.