I have an MSI installer to submit it in the Partner Center or Microsoft store. I converted my MSI installer into MSIX package format using the MSIX packaging tool.
I had already an idea of how to publish my app in the MS store using this reference: https://www.advancedinstaller.com/msix-publish-microsoft-store.html
However, there's a question that comes to my mind. Once I published my application in the MS store and
What if I have new updates in my app, what are the steps how to do that?
I did some research most of the results have something to do with source code.
My preferred approach is to update the app without coding configurations.
The submission process is managed through the Microsoft Partner Center dashboard, which is a web portal that allows developers to publish applications, and manage the updates of the application to allow keeping the app up to date automatically.
Once you submit updates to a published application, the updated packages will be available on average about two hours after submission (though this can sometimes take longer, especially with larger packages). Price, screenshot, or description changes take on average 16 hours to go live. Customers will receive the updated package the next time their device looks for updates, if (automatic app updates) are turned on,
or when they trigger the update by proceeding to the Windows Store and choosing (Check for updates) on the downloads. By default, automatic updates are turned on in the Microsoft Store, so users will always use the latest version of your application.
References:
MSIX Auto Updates https://www.advancedinstaller.com/msix-auto-updates.html
Update a public app https://blogs.windows.com/windowsdeveloper/2016/05/13/publish-or-update-a-public-app-dev-center-tip-1/
Mandatory updates https://learn.microsoft.com/en-us/windows/uwp/packaging/self-install-package-updates#mandatory-package-updates
Upload app packages https://learn.microsoft.com/en-us/windows/uwp/publish/upload-app-packages
Related
I have an access database that uses data pulled from an API, this data export is conducted hourly.
I would like the access database to automatically run an update module (which imports the exported data and cleans it up), based on the same schedule the API exports my data, so Access will be current at all times.
The database I designed is used company wide. The accde and backend are both located on a windows 2008 server.
I just wanted suggestions on the best way to automate this, without the need of human intervention, preferably nor my local machine.
From rough research (accompanied by my own ignorance and stupidity) I’m assuming I need to setup a task scheduler on the server to launch access and run the module on open if FOS username is the local machines user (administrator).
I highly welcome any feedback as again, I just taught myself access these past two months and am horribly unknowledgeable on the implementation side.
I've developped a MySQL database containing informations about different documents and products. Now I have to create a user interface which has to be integrated in a sharepoint. As I'm new to sharepoint, I am a bit lost and I don't know what I should choose (developping a Web Application on visual studio which will be hosted on Sharepoint, developping a WebPart...etc I have no idea of what to do).
So my question is : What's the best option to develop this user interface on Sharepoint ?
Thanks
You can go different ways:
Push data from your MySQL database to SharePoint list periodically or event-based.
In this case you already have UI interface of SharePoint list view. If out-of-box UI not enough then you can create your own using javascript or by creating your own web part or by creating SharePoint add-in.
You can do it many ways:
1.1. C# console app (create with Visual Studio). Console app will connect to your SQL database and create list items in SharePoint list. You can schedule this console in Windows Task Scheduler.
1.2. Another periodically running code that external to your database. May be PowerShell script, SharePoint timerjob, Windows service, SharePoint workflow or something else. This code will connect to database and push data to SharePoint list.
1.3. I don't know how you fill your database but in your logic you can add logic to also create SharePoint list item in list when you add record to database.
It is event-based logic.
Get all data from your database in SharePoint on page load each time.
Add some web part to SharePoint that get data from your database on page load (you can mix some parts below to get intented behavior):
2.1. Create your own Visual Web Part in Visual Studio. Deploy solution with web part to SharePoint. Add web part to any page in SharePoint.
This web part will get data from your database on page load.
2.2. You can create web service hosted anywhere (SharePoint, another place) that return data from your database.
Create javascript logic that call this web service to get data and render data.
Add this javascript logic in Content Editor or Script Editor web part in SharePoint. CE and SE web parts is out-of-box web parts, you don't need to develop this.
2.3. Create SharePoint add-in that will get data from web service.
2.4. etc ....
May be I can suggest other options if you specify more precise requirements to implementation.
Just say how you see it in your imagination and I can suggest ways how to implement it.
Describe how it must be from user experience. Like 'I see page where I have three green buttons, color highlighted rows, auto-calculated field and so on and so on. I click button and get following result... ". Describe your expected user experience.
About trends - javascript rules now. In SharePoint Online you cannot create server code solutions hosted in SharePoint.
Best solution to use javascript to not change many things on migration to different version of SharePoint.
I recently discovered Power BI as part of our Office 365 subscription so am very new to it.
We have a MySQL database with about 5 million rows in AWS. I want to add this as a data source to our Office 365/Power BI service.
How to do this?
I see there is no content pack service that allows me to do this.
According to this SO question and answer, there is no direct way to do this: How to connect POWER BI web with AW mysql database?.
I also looked at using a Power BI Gateway to achieve this. There are two types: Personal and On-Premises. We don't have any Windows Servers, so this leaves the Personal option: https://powerbi.microsoft.com/en-us/documentation/powerbi-personal-gateway/
For Personal, the documentation at that link says "A personal gateway is not required in order to refresh datasets that get data only from an online data source" which is a little confusing given that this seems to be the only option for connecting to my online data source (maybe this document meant to say "from a supported online data source"?). It seems that I install this on a local machine in our office, connect to my AWS MySQL database, query/model on my desktop, then upload my results to our Power BI Service for the rest of our company to access. I schedule refreshes using the Personal Gateway. Is this correct? I hope this does not involve the transfer of millions of rows to/from desktop and/or Power BI Service?
p.s. I also considered developing something similar to the content packs that are provided for GitHub, Google Analytics, MailChimp, etc but there doesn't seem to be a "private" way to do these. Doing it this way seems to involve becoming a Certified Azure Developer (even though there is no Azure in this problem) and then making the solution public (which I obviously don't want to do): https://azure.microsoft.com/marketplace/programs/certified/apply/. If there is a way to develop my own "private" solution without the certification and publication process, I would consider that.
I would tackle this through Power BI Desktop. You will need a windows machine to install this on, and it will need the MySQL Connectors installed, ref:
https://stackoverflow.com/a/32746679/1787137
Then I would develop and publish your queries, datasets and reports using PBI Desktop.
Finally I would configure PBI Personal Gateway to schedule refresh of the published report datasets.
5m rows is not trivial but quite possible in this scenario. You will likely only need a selection of your tables and columns, that have analytical value.
I have a website online with just HTML and I am not willing to use any other programming language apart from Javascript. All I need to do is connect my Microsoft Access database on my computer to a form hosted online so when information is submitted online it is updated on MS access the next time I open the file up. Is this possible and how can it be done?
Turns out, you can do this with zero code. If you use office 365, and publish an Access web forms.
Any information entered into the Access web form will automatic appear in your local database. The synchronizing of data from the web site and pulling down of the records to a local copy works automatic and without the need to write any code. In fact the sync starts automatic when you launch the client application. (it runs in disconnected mode). And any records you enter in the client application will also sync up and appear on the web site.
So, you can use Access and write zero code, and this two way sync feature is built in.
You need Access 2010, and either SharePoint 2010 (enterprise), or you can use office 365 and the $6 per month p1 plan which also does support Access web publishing.
However, I suspect issues of user logons and security may well be a greater issue here, and thus office 365 might not be correct from a user logon point of view. You can invite up to 50 users to that site for the basic $6 per month, but all users of the site will require a logon (which can be due to being invited to the site).
There are two videos of mine here showing this setup in action here:
http://www.youtube.com/playlist?list=PL27E956A1537FE1C5&feature=plcp
I think what you are trying to do is very impractical. You'll need to use Server Side Javascript to insert your data into a database, preferably SQL Server, and then you'll have to write some kind of code to sync the SQL Server Database to your Access database.
Alternately, you could setup your Access database so it connects to the same instance of SQL Server as your website using ODBC linked tables or ADO. I cannot really recommend this, especially if the data you have in your Access database is anything you wouldn't want to be public. Also, using MS Access to access a database across the WAN/Internet is really not recommended although it can certainly be done, as long as you aren't working with large amounts of data, large quantity of records, etc.
I am not willing to use any other programming language apart from Javascript.
And why aren't you willing to use something else? I don't think you're going to get anywhere if you don't open your mind to using the right tools for the right job.
Here's something that might help you get connected to SQL from Javascript:
How to connect to SQL Server database from JavaScript in the browser?
I am using Access2000 and Developer Tools, JRO for internet synch, RepMan 4, and was using Win Server 2003 (dedicated server). Just upgraded to Win Server 2008 and have been trying to get Internet synch operational, but with no luck. Here's my problem: I see that MS is urging/forcing subscriptions to SharePoint2010 for internet synchs, however I am not sure that their new platform is as useful to me as their old. Each company I distribute to will run a runtime version of my access application at multiple locations(could be 1 location per company, could be 100). They need to be able to direct synch within each location via LAN (anywhere from 2 to 20 computers). They do not always have an Internet connection (they are at sea), and when they do, it's by satellite and transmission costs are high. And so occasionally they will connect with one computer and perform Internet Replication to send data to home office(could be daily, weekly, or monthly). My current means of synching via JRO is very simple. After attaining an Internet connection, just open a form and either click the synch LAN button or the synch Internet button. Also, by not utilizing automatic synchs, we avoid corrupting other replicas when one is bad or a user has deleted massive amounts of data inadvertently (since deletes always win).
I feel that eventually I will have to update to Access2010 just to keep abreast on new developments in MS (i.e. new .PDF reports instead of .SNP). I recently purchased Office 2010 Pro in order to begin looking into this, but of course this will take some time to work thru.
Here are my questions:
Will SharePoint2010 allow for only one subscription per remote location to handle synchronization back to main office, or would every replica that performs a direct synch at the remote office be required to maintain a Sharepoint2010 subscription?
Can I still use JRO to complete direct synchs among replicas at a remote location and within the home office, and therefore only use Sharepoint 2010 to pass those updates via Internet to the home office.
Will Sharepoint 2010 Enterprise allow me to host multiple company databases in one central account (similar to RepMan4), or must I set up a separate account for each of my customers? If so, do I need to purchase a copy of Sharepoint 2010 for each of these customers?
Will Sharepoint 2010 handle basic data replication and/or design updates in a similar manner to my current set-up? Will I be able to utilize my custom conflict manager?
Also- do you have any info whether Internet synchronizations are indeed capable utilizing Access2000 viaIIS 7.5 on Windows Server 2008 with RepMan4? I have not found anyone who has accomplished this – latest suggestion is that maybe IIS needs to be run in a 32-bit environment in order to open the synchronizer, but I have not yet tried this.
My company makes a product called [EQL OnWeb - link deleted] which is designed for exactly your use case. It works with getting Access 2000 databases on the web without rewriting them first, and there's a free trial so you can see if you like it.
I won't comment in detail on SharePoint 2010 because clearly I'm biased... but I like our product better :)