I'm currently, with some friends, on a freelance project. For some reasons, the customer asked us to don't make a new server but just use Parse. The thing is, we knew that Parse will stop but he was keep wanting this thing, so we used it. Today, Parse has been stop and the costumer said he moved the data/stuff on another server. He also told us; "you just have to change the server address."
However, I can't find the way to change this address from xamarin forms. I found a solution which doesn't exist on my side:
ParseClient.Initialize(new ParseClient.Configuration
{
ApplicationId = "MYAPPID",
Server = "http://example.com/parse/"
});
But I as said above, it doesn't work since Initialize takes only 2 params which are the following, and not a ParseClient.Configuration stuff.
So I would like to know if you have any idea? It's not the only thing I tried but it seems to be the best example I can show you.
Any help is welcome, thank you !
I just started to use Parse. So maybe I can help you.
In fact with Xamarin Forms applications, Parse's configuration is a little bit different than with native platforms.
I suspect you don't use correct Parse DLL in your project. For instance in your iOS app (AppDelegate.cs), reference Parse.iOS.dll. Personally, I don't use Nuget packages and downloaded the correct DLLs from here:
Parse SDK .NET (github)
So referencing this dll in your project, you should be able to initialize Parse like that:
ParseClient.Initialize(new ParseClient.Configuration
{
ApplicationId = "xxxxxxxx-xxxx-xxxx-xxxx-b1782265ea00",
Server = "http://myParseServer.com/Parse/",
WindowsKey = parseID
});
For a more detailed description on how to use Parse for Xamarin Forms, I wrote a Post describing my solution:
Setup Parse for Xamarin Forms, conditional builds
Hope this helps
Related
As the title says, I use System.Environment.GetFolderPath(System.Environment.SpecialFolder.Personal) a lot in my app. It is crucial, I just migrated my app over to Maui from Xamarin and now it is not locating those files. What name/part of the build/package needs to be changed to match so that it finds those files. My users are going to lose a LOT of data if I can't figure this out.
Thank you!
The application ID and title both match exactly, the default namespace IS different, but I figured it looked deeper than that. It obviously looks at something to determine which app it is.....I just need to know what and how to make it match.
I'm learning Parse (the Javascript flavor) using their Todo App tutorial. I'm trying to write my first query. In the tutorial, I found this code:
var TodoList = Parse.Collection.extend({ ... });
I can't find any info about Parse.Collection in their JS Guide nor their API docs.
Can someone shed some light on what a Parse.Collection is and when I should use it?
You're not seeing anything in the docs because Parse.Collection was removed from the JavaScript SDK in v.1.6.0.
Downloads Page and JavaScript Changelog
SDK no longer contains Backbone-specific behavior. Moving forward, the core SDK will not be tied to any single framework, but we will work with the community to produce up-to-date bindings like Parse+React. The major changes are the removal of Parse.Collection, and allowing Parse.Objects to act as event channels.
In previous versions of the SDK, Parse.Collection was used almost identically to Backbone.Collection, as the Parse SDK was based on Backbone. Things are particularly confusing right now because tutorials on parse.com use pre-1.6.0 versions of the SDK.
I been set the mission to look at Xamarin and its cross plaform / code resuse ability, I come from a iOS/Android background.
I want to aim for the holy grail of one universal front end (basic) and one reusable service layer.
I created my first project as a Xamarin Forms PLC, hit the issue it can not support compiler directives, which seem to be something your going to need. Also I was unable to add Parse package to the PLC. You need to reference it per platform / write code per platform?
I have now created Shared Asset Project, the default setup (new project). This does not allow me to add parse to the shared layer. Some of the examples I see add a new project called service, what type of project is this?
So, my question is, forgetting how many members are in a dev team, which one (PCL, SAP) lets me have a universal backend (parse).
I found a Github sample project that could help you. It can be found here: Sample Parse Project
The link to the xamarin component can be found here: Parse component This Xamarin Component should be able to be added into your project and it should get you started immediately. Also when you add the component to you project you should be able to view sample projects that come along with it.
I would start with the sample project and see what I can do with it, but it should become a lot easier by just adding the Parse component in. This would make it so you could probably use either type of project with some Dependency Injection.
I'm trying to port FirefoxOS on Motorola G but I don't understand how to write device manifest. What should be specified in the manifest? Where do I start? Mozilla's official documentation isn't that helpful actually.
The manifest is tricky but like a bike - one you get the hang of it then it becomes second-nature.
Here are the links I used to understand the manifest:
https://developer.mozilla.org/en-US/Apps/Developing/Manifest
https://developer.mozilla.org/en-US/Apps/Developing/About_app_manifests?redirectlocale=en-US&redirectslug=Web%2FApps%2FFAQs%2FAbout_app_manifests
The main point that helped me was to understand that only two fields are required: name, and description. This make other options specific to your needs, so I stripped all other members out to start: "locales" and "developer".
The primary config that I needed to get right was:
launch_path - I got it to work through trial-and-error, but then moved the app within my architecture and was surprised when the app went 404! I shouldn't have been surprised because... the path was incorrect. After updating the path the app installed correctly.
For example:
/Apps/App1/app1.html
Final bit of advice on Manifest. The best way to understand it is to get a test app working from the mdn-app-template! This way you can see how it works and test it's capabilities. I strongly recommend this as a first step. https://github.com/chrisdavidmills/mdn-app-template
Other suggestions:
- It took a while to get the workflow down. It is possible to just click a 'refresh' link in the App Manager. Which is a rather immediate workflow.
- Uninstalling in Android was weird. The app is actually saved within Firefox. So you have to go to about:apps to uninstall. Here is the link: https://developer.mozilla.org/en-US/Apps/Developing/Apps_for_Android
Hope it helps.
First time poster here, so if you need more info or when I am too vague, please say so.
We are using Biztalk 2010 here, together with (of course) VS 2010 (Ultimate in my case, not that it matters) on a 64bit server.
I need to create a custom functoid and have done this (enough tuts on the web, albeit usually for older versions of Biztalk).
What I have problems with now are getting the name, tooltip, description and icon to show up when I add my custom dll to the Toolbox. Whatever I try with my resources, I cannot for the life of my have them appear in Toolbox (always null).
Picture link is below, I am not allowed to include more than 2 hyperlinks in my message yet.
I have used this link as (one of my) sources : http://www.eggheadcafe.com/tutorials/aspnet/f843db77-a775-415e-bd08-71c2b1127e40/biztalk-writing-and-usin.aspx
I must be doing something wrong in a stupid way, but I am at the end of my wits here. So, if anyone can please take my hand and help me through this ordeal.. please.. don't let me hold you back.
Thanks in advance !
http://i.stack.imgur.com/3UAJ6.png
Solution by the original author (Dennis):
I copied the sample functoid solution from Microsoft into a new project. Used that as a basis to create my own functoids and all is good. Not really the way to go I suppose, but it worked. The reason for my problem (I think) might have been the blank custom tool namespace on the properties of the resources.