i am trying to setup the tidesdk in titanium studio but it won't work for some reason... Here is what i've done so far:
Downloaded Titanium Studio v2.1.2.201208301612 from appcelerator
Downloaded TideSDK v1.2.0.RC4 from tidesdk.org
Added the sdk in Titanium Studio like this: "Help > install specific
titanium sdk"
Basically i just followed the instructions from this: https://groups.google.com/forum/?fromgroups=#!topic/titanium-desktop-transition/wv6fiRD6Sbo
But the option to start a new desktop project won't come up. Is there something i am doing wrong or something?
I am using lion 10.7.4, according to this google group that shouldn't be a problem. Anyone's got any ideas?
Here are a couple of things to help you on your way:
Lion and Mountain Lion with Xcode 4.x are supported in the upcoming 1.3.0 but not 1.2.0.RC4. 1.2.0.RC4 will work fine with Snow Leopard 10.6.x on Xcode 3.x. Another possibility in the short term is to consider developing on either a Windows 7, or Ubuntu 11.04 virtual machine until the 1.3.0-beta has released. This release is expected very soon and provides updates to core libraries and offers support for current operating system versions of OSX, Windows and Linux.
Code you write in 1.2.0.RC4 will work fine in 1.3.0 since there are no API changes. The only change will be in the JavaScript namespace. In 1.3.0, the JavaScript namespace for the future will use 'Ti' as opposed to 'Titanium'. By setting a global variable in your code, you can start using 'Ti' to begin with.
var Ti = Titanium;
As far as Titanium Studio, unfortunately Appcelerator dropped the desktop support but have revived it. They have come out with an update that is reported to work:
http://preview.appcelerator.com/appcelerator/studio/desktop/update/beta/
If your run into any issue, an alternative is to download TiDev Community:
http://api.appcelerator.net/p/pages/app_page?token=m4rZLSv6
TiDev Community is really reaching the end of its life cycle but it will work for creating in running your apps in the short term.
The TideSDK team has a new app under development called TideSDK Builder. TideSDK Builder will provide the basics of creating, running and packaging your apps. It will also feature scaffolds for kickstarting your app projects. A new tidebuilder CLI will also be available with comparable functionality. We are hoping to bundle these for the official release of 1.3.0 that is targeted for the end of September.
Appcelerator has provided a Titanium Studio SDK. The TideSDK team is exploring this to see that Titanium Studio IDE can continue for the future.
One last thing to keep in mind is that Titanium Studio and TiDev Community no longer support the network packaging service that Appcelerator once offered. This means local packaging in the interim while TideSDK team continues to examine options.
Please follow TideSDK on twitter for updates and announcements at http://twitter.com/TideSDK
Related
I am trying to combine obfuscating my xamarin android project and then bundle the assemblies into native code with the Visuals Studio 2017 Pro option.
I was able to obfuscate my assemblies with this tutorial https://blog.noser.com/xamarin-android-code-obfuscation/
Unfortunately the obfuscated assemblies does not find its way into the native bundle.
Likely i intercepted the build proccess at the wrong place.
<Target Name="Obfuscate" AfterTargets="_CopyIntermediateAssemblies" Condition="'$(Configuration)' == 'Release'">
Does anyone know how to merge the obfuscated assemblies into the native bundle? Thx for help in advance.
I help develop another .NET obfuscation/protection tool, Dotfuscator.
We've written a Xamarin build integration that automatically handles protection as part of the normal build process, so you don't have to manually write your own MSBuild targets or copy files around.
The official Xamarin docs recommend using Dotfuscator to protect Android builds, but this integration also works for iOS and UWP.
As Dotfuscator's Community Edition is included in Visual Studio, you can try this integration out for free.
I wrote a guest post for the Xamarin Blog that explains how to do this.
Edit regarding the setting in the question: I did some limited testing and Dotfuscator works fine with the "Bundle assemblies into native code" setting. I installed the latest version of Visual Studio 2017 Enterprise, version 15.7.2, but found out that version has a bug related to this setting. To work around it, I used the unofficial VSIX install mentioned at that link. Then I opened a Dotfuscator-Xamarin sample app and enabled the native code setting. I also added code to the sample to show the name of a class used by the application. Then I deployed the app to an emulator. The app ran normally and the logging statement showed an obfuscated name for the class, indicating that Dotfuscator correctly protected the app before it was bundled into native code.
I have a Phonegap project which so far has been used to build an Android app. I'm using locally installed Phonegap on Windows with a pre-populated SQLite database. The project uses Cordova-sqlite-ext plugin, my version is about a year old, have not had need to update.
Now I need to build a Windows version which should run also on Windows 8.1, not only Windows 10. This is for real computers, phones are not that important. It seems that in a few months also an iOS version may be needed.
After checking Cordova-sqlite-storage, Cordova-sqlite-ext, Cordova-sqlite-evcore-extbuild-free and Cordova-sqlite-legacy-build-support at GitHub I'm lost and don't know can I use any to reach all my goals.
Switching from Phonegap to Cordova is not an option because
building an iOS app on Windows is not possible with Cordova,
right?
PhoneGap CLI and Build are supported only by
evcore-extbuild-free which does not support pre-populated
databases.
Building for Windows 8.1 requires the legacy one
which does not support pre-populated databases.
So my question is that has anyone tried something like that? I'm wishing the documentation might not be up-to-date but perhaps that's a long shot. If nothing else I might be able to create the database structure and then ask a user to download data to populate it, but would prefer to avoid this.
One solution could be to develop the app using Windows and build the iOS version on a Mac. You could buy a single Mac to use as a build server or use a service like MacInCloud. If you're using Visual Studio, there are instructions for setting this up.
I want to port a Compact Framework/Windows CE app to Xamarin to create Android and IOS (and possibly Windows Phone) "versions." I reckon I need Windows 8 for Windows Phone (8) but for now I thought I could get started with Android and IOS in moving this prehistoric app into the 21st century.
According to this article, I first need "Project linker" and can NuGet it, but searching for it via Tools > Extensions and Updates in VS 2013 returns no search results.
That article says you need VS 2012 or better; the direct link to "Project Linker," though, says it supports VS 2010.
Where do I go from here?
UPDATE
I went here, and am in the processing of downloading.
UPDATE 2
Here, it says, "Modern Integrated Development Environment (IDE) – Xamarin uses Xamarin Studio on Mac OS X, and also Xamarin Studio or Visual Studio 2010 on Windows."
Yet in VS 2013, I do have project types now for Android and IOS*, so I reckon that's just a typo (hasn't been updated)?
although I don't have a Mac, so that is not possible for me right now; also, since I'm still on Windows 7 at work, Windows 8 Phone apps are not yet a possibility, either. So at present, Xamarin within Visual Studio is simply a replacement for Eclipse/Java in the creation of Android apps.
UPDATE 3
I've been waiting for something better than PhoneGap, and I think maybe I've found it. If MS were to buy this company and bake Xamarin into Visual Studio -- voila!/yowza/wow! The cats in Cupertino will have to reach for the Pepto-Bismol!
That's a bit outdated and there's a much better approach available today.
You can use Portable Class Libraries (PCL) to share code across project spanning iOS, Android, Windows (Phones) and even OSX.
See this article (and where it leads) for more details.
I certainly agree with #poupou that PCL's are the way to go (if possible). I would recommend James Montemagno's app on github. He just created this for channel9 using VS 2013. I just created a cross-platform app based off of this and it worked out well. I would only use the file-linking for the platform specific implementations with compiler directives. This can be seen in his ServiceRegistrar class in said app.
This SO answer actually explains how to get the 2012 Project Linker to work with 2013 if you still want to go that route and gives a link to the extension.
Also, you may want to check out MvvmCross. It is open-source, has a large user-base and following, and really helps with maximum code re-use. Best part, it uses PCLs and all of it's features (plugins) are available via nuget.
I would recommend reading the article #poupou posted, watching James' channel9 videos on his github page, and (if you want to check out mvvmcross) watch #slodge's N+1 videos on mvvmcross.
I have just developed and android app using eclipse and now I want to develope its IOS version. I want to use Visual Studio and C# (I feel pretty much comfortable in these environments).
I read that, to achieve this I can use Xamarine. Everything is OK with configuring Xamarine on Visual Studio and using it in Visual Studio (I understood this part). I couldnt understant the "mac" part. They are saying that in order to build this app I need a mac running in my local network. Unfortunately I have no idea about Mac. Instead of using it in a local network, could I just install it in a Virtual Machine in windows and configure it on that way that I can see this mac from Visual Studio (How can I do this ?! :S).
I am sorry if my question is unclear but I would be greateful if any of you helps me understand these issues and help me develop my first IOS app in Visual Studio.
If you are going to do iOS development using Xamarin you need a Mac. A Mac will always be required to submit the app to the app store, and the way Xamarin works, you need to use a Mac to create the UI for iOS apps as well.
To get the most of the Xamarin, you ideally would develop your base code using Xamarin and C#, then build separate UI's for both Android and iOS. While your UIs are separate, your base core code is all the same for both apps.
It really does not make sense to have a native Android app all in Java, and then write the entire iOS app in C#. Either stick to completely native apps for both platforms, or use a wrapper like Xamarin for both.
Xamarin.iOS for Visual Studio makes it possible to develop iOS
applications on Windows, but you will still need a Mac in order to
compile and run the code.
Today, Xamarin.iOS integration in Visual Studio is focused on enabling
developers to develop in C#. Xamarin developers who write Xamarin.iOS
applications on Windows typically hand-code their user interfaces—or
they will need to switch to the Mac to use Xcode (or a beta version of
Xamarin’s new iOS Designer) to interactively design an iOS user
interface layout.
"or use a wrapper like Xamarin for both"
I have discovered the term wrapping is not correct for this product.
Unlike other products (Corona, Phonegap, Titanium, ...) that wrap up in a common, genericized library, Xamarin compiles at core level with no penalty. It is 100% native. All functionality in all it's supported platforms is 100% available and not watered down.
Wrappers can be faster to program in, in theory, but when you factor in the time you will spend looking for workarounds for the one piece of functionality that is available natively but not in your wrapper library. When you factor in the constant bugs because wrapping for 3 or more platforms is a constantly moving target and you can't count on it working from day to day.
When you factor all those things in, writing native in c# for all platforms is the better option.
I tried them all, and xamarin was my last choice as I was distracted chasing that perfect golden goose wrapper product.
Any one can tell me that how to Blackberry sdk installation with netbeans for Mobile application development
i am trying to plugin but not able to do .
I have used this tutorial in the past. You can ignore the part about J2ME Polish. Also, I think the Mobility Pack might come with new versions of Netbeans now (it didn't use to). Or, it's possible that in the Netbeans -> Tools -> Plugins menu, you might need to make sure the Java ME plugin is installed.
He references much older SDK versions, but as long as you download the newer JDE versions here (SDKs) from BlackBerry, the same basic instructions should work for you.
I've been using Netbeans less and less, and the BlackBerry Eclipse plugin more, in recent years, despite the fact that I like Netbeans better, as a general-purpose IDE. Unfortunately, you'll find that RIM is focused on Eclipse at this point.
But, you should still be able to use Netbeans if you like.