I'm a beginner of WP7, and I spent some time looking for solutions not only can consume
but also Insert/Update/Delete the data stored in SQL Azure.
I found a good tutorial here:
http://samidipbasu.com/2011/07/24/updating-odata-data-source-from-wp7-part-1/
However, the SQL Azure Lab no longer accepts registration.
http://www.microsoft.com/en-us/sqlazurelabs/labs/odata.aspx
So, is there any other solution for directly accessing SQL Azure in the cloud without setting up a server?
Thank you.
have a look at Windows Azure Mobile Service, that should cover the server side.
you can then access the REST-based API from Windows Phone, see Using Azure Mobile Services with Windows Phone
Related
Recently I've created an account on oracle cloud and created a autonomous database processing, i have a simple .NET Core API, she connect on my cloud database using EF Core and returns select result in JSON format, on localhost works normally, my application was connect to database and returns my expected result.
When i publish the application on azure web app free plan, the application doesn't connect to my autonomous database, i think because i'm trying using a free plan, someone just tried do something? (Oracle Cloud + Azure Web APP)
It is possible that you are hitting the Azure Web App's sandbox restrictions. Some tips to troubleshoot:
Take a look at the documentation on this topic and see if it applies to your web app, https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox
Check if you can find the any errors via App Service Diagnostics, https://azure.github.io/AppService/2018/09/24/Announcing-the-New-App-Service-Diagnostics-Experience.html
I'm about to finish an app that will run on Windows Phone and Android. It uses an azure web API and push notification service.
I was wondering if there is any standard or recommended way of protecting the 'signup' or 'register' functionality within an app like this? I note that some popular apps like snapchat will send you a text to verify the registration process. That would be ideal but obviously seems unfeasible for a modest app such as mine :-)
Can anyone enlighten me to some common ways to protect the 'register' functionality of a mobile app?
Thanks for any help!
Azure provides feature sets like Azure Mobile Services that provide authentication features that you can use in your Windows Phone apps. I doubt the authentication Azure Mobile Services uses is restricted to just Azure Mobile Services, but more information on getting started with this authentication can be found here:
http://azure.microsoft.com/en-us/develop/mobile/resources-wp8/#header-2
I recently installed Windows Server Service Bus 1.0 (on a Windows Server 2008 R2 machine).
That also installs "Windows Fabric" (not AppFabric).
Could not find much information on it, and googleing it I stumbled on a Lync server post (Windows Fabric is also installed by Lync Server 2013).
Definition:
"Windows Fabric is a Microsoft technology used for creating highly reliable, distributable, and scalable applications."
From the Service Bus architecture intro,it looks like Fabric is what allows for services replication, high availabilty, and fault tolerance.
Anyone knows if that can be used to host custom .NET services? Or any kind of direction would be greatly appreciated.
Thanks in advance.
Cos
I went to a talk by Mark Eisenberg on May 28th at the Microsoft NERD Center near MIT in Boston MA. The talk was mostly about the Azure Service Fabric. General consensus was that if you're using Azure from the infrastructure as a service perspective you aren't really using it.
The next step up is to use Azure naively as a platform meaning that rather than create VMs and hosting them there you're creating cloud services and web jobs and web apps and using the new Logic Api's etc...
But if you really want to build a stateful, resilient service enterprise class you'll want to go underneath the PaaS and write against the Service Fabric directly for greater control.
That's where the money is.
I did a write up on the talk and what the Azure Service Fabric is a few days ago and posted it here.
I don't actually think that Windows Fabric is open product. It is used for infrastructure purposes, and not for deploying custom services. For your custom services you have to use platform built on top of Windows Fabric, like Service Bus, Windows Server App Fabric.
I think Windows Fabric is for internal use by Windows Azure and Private Cloud for clustering, load balancing and so on.
UPDATE:
I've started developing Windows Azure application and here is what I've found.
I've added a Service role to Azure application and started it on local development machine (under Azure emulator). And my service was published in and started under Windows Fabric!
So the conclusion is: Windows Fabric is a platform for running YOUR Cloud Services.
Fabric which the name suggests in itself, is back-end.
It is no different than iSCSI or EIGRP. The main difference is that it is generic in form rather than specific like the aforementioned services/protocols.
IIS is a server service specific to web hosting.
SQL the same but database only..
fabric, applied to host fabric aware services and software.
Windows Fabric is used internal by Microsoft to building highly available, resilient and scalable services. It has been used for Service Bus, SQL Database, Document DB etc. according to this video: Building Resilient, Scalable Services with Microsoft Azure Service Fabric
Until now it has not been available for external parties but has now been announced as Service Fabric which will be available on Windows Azure and Window Server 2016.
Read more here: http://azure.microsoft.com/en-us/campaigns/service-fabric/
I am new to Windows Azure and SQL Azure and was wondering if there is a way that I can export the reports (on my reportserver) that I created and e-mail them to for example and administrator automatically like every week?
Kind Regards!
As you are new to both Windows Azure and SQL Azure, I would suggest the following:
SQL Azure Reporting is still in Preview (or CTP) mode so there are limited functionalities available.
SQL Azure reporting preview provides following 3 scenarios:
2.1 Embed Microsoft reports in Web or client applications
2.2 Design, publish, and view reports (.rdl) and report-related items on a SQL Azure Reporting report server.
2.3 Interact with the report server Web service by using SOAP API calls.
So when you are using SQL Azure Reporting Preview you can generate the reports however to send these reports via email you need a front end to take care of job or custom code running on-premise connected to SQL Azure Reporting service.
3.1 This front end could be a Windows Azure Web Role (using 3rd party email provider or online MS Exchange to send email) or your own SQL Azure reporting service sending emails by using custom code.
3.2 You can also write a client application talking to Reporting Service Web Service over SOAP to get reports and then email to required destination.
More information on SQL Azure Reporting Preview is here:
http://msdn.microsoft.com/en-us/library/windowsazure/gg430129.aspx
I assume your reportserver is running on Azure? Azure doesn't have an SMTP server so basically what you will need to do is
1) Use a third-party SMTP server (Gmail is free) to send out the emails. Azure recently have a deal with sendgrid who provide SMTP and email services as well.
2) Write a little application that runs in a worker role and periodically generates the reports and sends them out.
This question has probably less to do with actual programming and more to do with environment setup.
I'm developing an application for a Windows CE device, which will use a service hosted in Microsoft Azure. Obviously, this is all under development, and the service itself has not yet been uploaded to Azure. So I'm using the emulators provided by MS to deploy the service locally. Also, I don't think uploading the service to Azure just to debug it is a good idea, as that could net us a bill for Azure we don't yet want to pay.
Also, please note, I'm using VS2008 for the Windows CE project and VS2010 for the Azure project (thank you MS for dropping support for mobile devices -_-).
The problem is, the service seems to be accessible only via 127.0.0.1 or localhost, and if I physically connect a Windows CE device or use an emulated one, it becomes a new entity on the network, and cannot access that service any more.
How can I debug my Window CE application and have it see the service, whilst still being able to debug the service itself?
You are correct, the development fabric (the compute emulator that allows you to build an azure application and debug it locally) is only meant for local development. There are some hacks that allow you to get around that, but I wouldn't recommend it.
My recommendation would be to spin up the service in a more traditional hosting environment, at least in these early stages. You can define it as a web app just as you always would have, and get it functioning. Then, when you know its mostly complete, create a cloud service project and do an add existing to bring your web app into the cloud service solution. Once in, its a simple matter to add the web app as a web role.
From there, you can complete testing of the service in both the local and hosted azure environments as needed. This allows you to minimize your development costs while still leveraging the power of the cloud. As an upside, you also have done most of the basic work to ensure your service is compatible with multiple deployment scenarios giving you a greater degree of choice for its final production state.
OK, I don't know if this was intentional, or if I found one of the mentioned hacks, but I saw that IIS hosts the Azure site I created on port 5100, and the binding for this site is *, so it accepts all connections.
Using this I could access the service from my emulator, and I could still debug all Azure related stuff.