Question:
Why does the MSIX not automatically check for updates every time the application runs when sideloading is enabled?
Context:
We are migrating a WPF application to Azure and have created an MSIX installer with sideloading enabled and set to check for updates every time the application launches. Accordingly, the *.appinstaller file is as follows:
<?xml version="1.0" encoding="utf-8"?>
<AppInstaller
Uri="https://<AppService>.azurewebsites.net/<AppName>.Setup.appinstaller"
Version="1.0.1.0" xmlns="http://schemas.microsoft.com/appx/appinstaller/2017/2">
<MainBundle
Name="<SomeGuid>"
Version="1.0.1.0"
Publisher="CN=<CertificateName>"
Uri="https://<AppService>.azurewebsites.net/<AppName>.Setup_1.0.1.0_Development_Test/<AppName>.Setup_1.0.1.0_x64_Development.msixbundle" />
<UpdateSettings>
<OnLaunch
HoursBetweenUpdateChecks="0" />
</UpdateSettings>
</AppInstaller>
Unfortunately, every time we publish an update to the package to Azure, the application does not automatically check for any updates, and so it does not prompt us to update. However, when we go to the application's published weblink and click to install, the installer will see that the application is already installed and that an update is available.
Troubleshooting:
We tried adding to the app manifest's Content URI (tab) to the *.appinstaller site, but that did not work. I noticed that the *.appinstaller is appending the text _Test to the path name. I am not sure why that is being added. I have tried recreating the installer package in order to rule out any potential configuration errors. Could that be the source of the problem?
I have also enabled Use developer feature and followed all other instructions provided by Microsoft here: https://learn.microsoft.com/en-us/windows/application-management/sideload-apps-in-windows-10
Note: we tried creating a ClickOnce publish profile and that works. It does not make sense why sideloading works for ClickOnce but not MSIX.
From what I see here you need to update the schema to 2018:
xmlns="http://schemas.microsoft.com/appx/appinstaller/2018"
Also, what version of Windows 10 are you running? I see the appinstaller update settings have been introduced gradually, older versions of Win 10 do no support all of them.
Another older issue from 2019 seems to highlight a limitation for apps launched via a desktop or taskbar shortcut.
Related
Unable to get through the Hybrid Configuration Wizard in Modern mode. This is necessary because we want to migrate mailboxes. Classic mode works.
It knows that there is a Hybrid Agent, but I can't successfully install with either path of using existing or adding a new one. In Azure there is an App Proxy registration which appears to have the incorrect IP for the route to on-prem. This was due to a misconfiguration of our outgoing firewall. However after the firewall configuration was fixed, the App Proxy still has the old return IP, and there is no way in Azure to remove this record.
I've removed the app proxy components on the server, and let the HCW install again but this record is not updated or removed. Also have gone through 'Classic' path which according to community posts is supposed to remove the App Proxy record, but it doesn't.
According to what I've read, if the record is inactive for 10 days, it will be removed, but I'd rather resolve this without waiting for 10 days.
I've tried patching the record using Graph but it doesn't work.
2022.01.31 22:09:59.707 10333 [Client=UX, fn=SendAsync, Thread=15] FINISH Time=2170.2ms Results=BadRequest {"error":{"code":"InternalUrl_Duplicate","message":"Internal url 'https://LOCALFQDNSERVER/' is invalid since it is already in use","innerError":{"date":"2022-01-31T22:09:58","request-id":"d5c4dfe0-096d-4382-9da0-9559f45e0217","client-request-id":"d5c4dfe0-096d-4382-9da0-9559f45e0217"}}}
I have created an ISE Logic Apps environment, and am trying to add the FileSystem ISE connector to the Managed connectors list, as it does not appear in my default list. When I click on '+Add', I can see the File System connector in the drop down that comes up, but when I select it & click on 'Create', I get the following error:
Failed to create connector 'isefilesystem'
Operation name
Set Integration Service Environment managed API
Time stamp
Mon Jan 13 2020 16:53:24 GMT+0000 (GMT Standard Time)
Event initiated by
xxxxxxxxx#xxxx.xxx
Error code
IntergrationServiceEnvironmentManagedApiDefinitionTagsNotSupported
Message
The tags are not supported in the managed API 'isefilesystem'.
The ISE File System connector is available. The ISE File System connector will not be automatically added to the ISE, you will need to manually add it yourself. Our engineers are working on getting that automatically added with new ISE deployments.
Here are steps from the document to add it manually to the ISE :
On your ISE menu, under Settings, select Managed connectors. On the toolbar, select Add.
On the Add a new managed connector pane, open the Find connector list. Select the ISE connector that you want to use but isn't yet deployed in your ISE. Select Create.
Only ISE connectors that are eligible but not yet deployed to your ISE appear available for you to select. Connectors that are already deployed in your ISE appear unavailable for selection.
Checkout this GitHub issue as well for details.
File system connectors is not yet available in ISE. You can use the shared connector (With gateway) in a Logic app in ISE till it is available.
It is on-premises data gateway. Yes there is already a work items for this and it is in progress and will be there in near future but this timeline is subject to change. As far as new features go, we are not able to disclose much at this time.
Also you could vote up this feedback to promote this feature to be achieved quickly.
I am having problems with the ISE Create File (Preview).
I have an API Connection defined with the Root Folder setting using dot notation, e.g. 192.168.1.23, because there is a DNS issue with hybrid cloud-on-prem lookup, or so I am told.
The Logic App portal editor in Designer mode behaves strangely when configuring the folder path in the Create File action. When using the pop-out folder picker I see "The use name or password is incorrect".
I have made sure that the credentials are correct and have tested successfully via other means.
Is there a work around?
Is this a known issue?
I am distributing Firefox ESR in an enterprise environment, including a homemade WebExtension in the distribution\extension directory as explained in https://support.mozilla.org/en-US/kb/deploying-firefox-with-extensions
This instance of Firefox is installed to be used for a particular set of applications and is not intended to be used as the user's main browser. It is launched through a cmd script with a specific profile, for instance :
Firefox\browser\firefox.exe -profile myParticularProfile
Starting Firefox this way creates the profile if not already present, and the profile will not be visible in the profile manager.
Everything is fine after initial installation : every new profile of every user will get the extension copied to the extensions directory of its profile, and the extension is activated.
However, I need to be able to update the extension without reinstalling Firefox. The problem is, the updated extension does not get copied to existing profiles.
The documentation says that the extensions will be updated when Firefox is updated, but I need to be able to update the extension without updating/reinstalling Firefox.
Clearing the "extensions" folder in the profile does not solve the problem (the extension does not come back with the update version as I hoped)
I also tried clearing various cache directories without success
I hope I will not need to write a command script to update the extensions myself since I am not certain I will be able to easily locate and modify every user's profiles.
Maybe suggesting to firefox that it has been updated (even if it is not true) would do the trick, but I do not know if this is possible.
Any ideas ?
Whenever I run my appengine project on local host and run queries the datastore-indexes-auto.xml file does not generate the indexes. I've tried adding autoGenerate="True" but it didn't change a thing.
Whenever I run the project the file gets updates but always displays the same text:
<!-- Indices written at Wed, 27 Jan 2016 21:08:31 CAT -->
<datastore-indexes/>
I've searched for a fix to this issue but couldn't find anyone with the same problem.
This happens for all app engine modules I have on Android Studio.
I'm using Android Studio 1.2.2 and the libraries I'm using are:
App Engine SDK 1.9.21;
Objectify 5.0.
Making the comment an answer.
You need to set the autoGenerate="true" attribute in the WEB-INF/datastore-indexes.xml file:
From Using automatic index configuration:
Determining the indexes required by your application's queries
manually can be tedious and error-prone. Thankfully, the development
server can determine the index configuration for you. To use automatic
index configuration, add the attribute autoGenerate="true" to your
WEB-INF/datastore-indexes.xml file's <datastore-indexes> element.
Automatic index configuration is also used if your app does not have a
datastore-indexes.xml file.
I'm trying to create a new solution with dot net nuke.
I installed the packages and configured IIS to work with it.
Then with visual studio i created a new solution. I want to import an old module already created, so i copied/pasted the folder in "DesktopModules".
Then with VS i right click on the solution and selects add existing project.
This way i get an error:
The web application project "name" is configured to use IIS. The web server "http://dnndev.me/desktopmodules/name" is not found.
It's probably because the corresponding projet is configured to use a web server depending on the URL you've got.
I suggest you to edit the project file with notepad (csproj or vbproj) and to remove the specified URL configuration. You also have to set the UseIIS value to false.
Note that this configuration could be stored in the users project file (.vbproj.user or .csproj.user).
Then, try again to add this project to your solution.