I am experimenting a fail on xaml preview on my Xamarin project on VisualStudio for MAC 7.6.4.
After some update, xaml no render yet the preview showing a System.NullReferenceaException as showed in the picture.
Any help about tht issue?
Related
The preview for Xamarin's android development is in a word, unkind. It has to re render the view everytime and isn't as smooth as the Android studio one.
I keep hearing about XAML previewers. Why can't I preview my .axml files using these applications?
I have migrated my 6.1 project to 6.3 its getting stuck on splash screen. After sometime it showing white screen.
its not calling initOptions function also or else deviceready also. Is there any solution?
Without the requested sample application to debug we cannot help further.
The only alternative is to replicate your app in a new project and application in MobileFirst Studio 6.3 by copying over the contents of the HTML, JS and CSS (and any custom native code you may have implemented).
Hello I try to implement Charting with WinRT XAML Toolkit for windows phone 8.1.
It runs well while I do debug, but the page which contains chart can not be navigated after I release it.
But it only happened when I add Area,Line,Column, and Bar Chart, it works fine with pie.
Please let me know if something I need to do to fix this,
I install the Toolkit using Nuget Package Manager.
Thank you
I want to build a a simple Sencha Touch-2.3.1 application generated by Sencha CMD to run it on
Windows 8.1 Microsoft Surface Simulator.
1-I opened Visual Studio (2013) and created a new JavaScript Windows Store project.
2-Copied the generated Sencha Touch app files to my project.
3-Changed the start page from default.html to index.html.
I then ran it on the simulator, but the application hangs at the blue loading screen with white dots. I opened the js console and found nothing in the log.
Is the approach wrong from the beginning? Sencha Touch team Assume that they support windows 8, but I'm unable to find any documentation illustrating the building procedure.
If any further info are needed let me know, your contribution is highly appreciated.
The issue is the Windows 8 content security policy (CSP).
I have answered similar posts before, in addition to a few blog posts I've written (specific to Ext JS, but the same principle):
Creating Windows 8 Apps with Ext JS
First Thoughts on Windows 8, Visual Studio, and ExtJS
In short, neither of the Sencha Frameworks explicitly support the Win8 CSP... but with a little bit of hacking you can get it to work just fine.
I got a application from my teammate, and it is for both iphone and ipad devices (which it is developed under iPhone SDK 3.2).
I have iPhone SDK 3.1.3 installed in my mac book. When i tried to compile the application for iphone simulator i got the following error.
Interface builder is unable to open documents of type iPad XIB.
The above error is for interface builder created for ipad.
My Question is we can't compile the application on iPhone SDK 3.1.3 which the application developed under iPhone SDK 3.2?
Please shed some light of this?
thanks
mindus
Go to your project settings, and delete the line that says Interface Builder Plugin search path or something similar.
the exact line in project.pbxproj is: IBC_PLUGIN_SEARCH_PATHS = "${PROJECT_DIR}/**";
Short answer
Temporarily remove the iPad xib when working with the 3.1.3 SDK. Put them back when you go back to 3.2 and above.
Longer answer
This cropped up for me when compiling against 3.1.3. You can use conditional compiling to get code user newer features to build successfully (see Matt Gallagher's helpful post on conditional compiling).
There may be a smarter way to tell the compiler not to look at the iPad xibs. For testing on the 3.1.3 simulator I simply made a copy all my iPad xibs and then removed them from the xcode project. When going back to my current development set up, you have to put them back. It's a bit of pain, but not that fiddly.
To fix this:
Press Command-1 to go to the project tree
Select your project
The in the right panel select your project, and then click on "Build Settings"
In search field just below the "Build Settings" enter: "Overriding Plug-In"
Now, the only visible setting left should say "Overriding Plug-In and Framework Directory"
Double-click the value and remove all entries using "-" button
Click somewhere else so settings are saved
That should fix it