We have WPF desktop application which we have packed in setup executable. Because of SmartScreen we need to certificate our application. We have used Windows App Certification Kit (WACK) from Windows 10 SDK to generate XML reports. And now we have to submit those reports to Microsoft.
https://learn.microsoft.com/en-us/windows/desktop/win_cert/windows-certification-portal
We have created developer account as company, and when I click on submitting reports:
Test locally and upload the results
After your run the Windows App Certification Kit tests, upload the results to the Windows Certification Dashboard.
https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/
It directs me to Windows Hardware Dev Center dashboard?!?
Were do we upload our WACK reports for our desktop application certification?
I have opened a ticket with Microsoft regarding this and it turns out the "classic desktop" logo program has been discontinued.
The only way you can "certify" your application is either the Ready for Windows program or the Windows Desktop Application program.
Related
I have a Tauri (https://tauri.app/) react app. (latest 1.1, and latest react versions).
I used the Windows Configuration Designer to provision a kiosk device.
I attached the MSI installer of the react application in the kiosk device provision.
The provision worked and I tried to apply it on a different windows 10 PC.
A new account was created for the kiosk user (based on the configuration) but when I`m trying to use this kiosk user a bluescreen appears with the following error message:
We weren't able to start your app. Press Ctrl+Alt+Del to sign out or contact your system Admin. For more info, search online for error code: 0x80070057
My question is, how can I set up a kiosk provision package with a Tauri app?
I wanna use my custom desktop app (Tauri & react) in kiosk mode on windows 10.
Our .NET Windows Forms Desktop Bridge app on the Microsoft Store cannot read network shared files only in a very specific situation:
The network shared files have been marked as Offline Files in Windows (a Windows Sync Center feature), and
"Always available offline" has been enabled on the shared files, and
The network shared files are offline (disconnected from the share)
Below is a screenshot of an example shared/synced/offline file:
When receiving a file path from the share in our software (e.g., U:\pdf\document.pdf), File.Exists(string path) returns false as if the file does not exist. When using the file open dialog (System.Windows.Forms.OpenFileDialog) and navigating to the shared drive, the dialog states:
An error occurred while reconnecting U: to \XXXXXXXXX\Share Microsoft
Windows Network: The local device name is already in use. This
connection has not been restored
Our app, like all Desktop Bridge apps, runs under full trust. Our non-Microsoft Store distribution of the software, when run side-by-side with the Microsoft Store version, recognizes and opens the files fine. Other UWP apps on the Store can open files in the network share as well.
What's going on?
UPDATE:
I added the permission broadFileAccess to the manifest per Nico Zhu's recommendation. I'm testing by sideloading the app. File.Exists() still returns false, but I get a different error from System.Windows.Forms.OpenFileDialog when clicking the share location--a network error due to permissions:
Are there other permissions I need to add? Is it possible that Desktop Bridge apps are required to use FileOpenPicker?
UPDATE 2:
I looked at the manifests of other Desktop Bridge apps on the Store, and they only include the runFullTrust permission and not the broadFileSystemAccess permission. However, they are able to open the "Offline Files" while my app cannot, leading me to believe that adding additional UWP permissions is not the solution.
Sample Project
You can reproduce the issue with this linked project (VS2017 WinForms 32-bit project with Inno Setup installer converted via DAC to an appx): WinForms DAC Project
The WinForms app has only a button that opens a System.Windows.Forms.OpenFileDialog. I sideloaded the appx with Windows 10 1709 and see the same error result as my app when trying to access the offline files location. The network share is hosted by a Windows Server 2019 instance.
We developed an Outlook Web addin in React, build with Webpack. It works on the web, on apps, and on desktop.
We have a very strange case we cannot explain with a customer. We did test on a virtual machine (Windows : 10.0.16299.0 ; Office license : Microsoft Office 365 ProPlus ; Outlook desktop version : Outlook for Office 365 MSO 16.0.10730.20264 32 bit) with both administrator account and normal user account :
Addin is working well with an administrator account, web and desktop.
Addin is working well on web with non admin account, but JS seems not to be executed on desktop. Static HTML content appears, meaning it is not a network or firewall issue.
We have another version of the addin, not using Webpack and React, just pure JS : it is working well both on web and desktop, meaning JS can be executed on the non admin account. We can see the addin loaded in the cache files of AppData.
Is there any problem of React based addin which could explain this very strange behavior (why this difference between an admin and non admin account ? how could JS could be interpreted differently depending on the type of account ?) ? Or any known incompatibility with Webpack ?
Microsoft Store developers did not find this problem running tests on the code...
I created Windows Phone 8.1 Silverlight app, and I can't to upload it into WP store. I want to use Create App Packages tool in Visual Studio 2013 Professional, but it's impossible for Silverlight apps. I read many guides on dev.windows.com. It's necessary to upload only .appx, .appxbundle or .appxupload files, but I have .xap file only in Bin\ARM\Release folder. May anyone help me?
I'm having the same problem, which I just solved.
WP8.1 Silverlight application may not be packaged with the "Create App Packages" tool, so you have to perform several operations manually.
The process is described on msdn (https://msdn.microsoft.com/en-us/library/windows/apps/dn655122%28v=vs.105%29.aspx)
- First you have to start the submission of the app on your msdn dashboard.
- From here, you'll get some informations, such as reserved application name, and several IDs that you have to edit into both WMAppManifest.xml and Package.appxmanifest
- Then you can deploy your app (or run the emulator for release)
- This last step will create the package you can upload.
First my apologies if I failed to find an answer searching - I tried a variety of search topics but none that were directly related.
I have a Lightswitch app deployed and working fine, running on IIS 7 and Windows Server 2008. It is an internal intranet app only.
I am using only FORMS AUTHENTICATION, all others are disabled.
The app works fine for MOST windows users.
However, some windows users get nothing but a blank screen - no login, no "loading..." and no silverlight "98%" display.
In the IIS log, I don't even see where it looks like it is being accessed when they attempt to load the app?
So, my question is, since this is FORMS authentication only, what could be causing it to NOT work based on which windows user is trying to run the app?
In other words, on the same Windows 7 machine, it works for 10 users, but not for others.
by the way, the application is remote - it is not running on the local machine.
The users ARE able to access the other ASP.NET applications hosted by the same IIS server in the same root inetpub folder.
The lightswitch application is using the ASP.NET v4.0 Classic app pool in calssic managed pipeline mode.
Any help greatly appreciated!!!
Happy to post any details/config/logs - I did not do so yet as I wasn't sure what would be most useful....
On the users machine you need to use Fiddler or the F12 tools in Internet Explorer to see exactly what calls are being made to the server and which ones are failing. LightSwitch is just an ASP.net website that launches a Silverlight application.
So the only other thing I can think of is that those users do not have Silverlight installed on their machines?
The users need to install the latest version of Silverlight. Apps built with LightSwitch 2011 require v4 or above and those built with LightSwitch for Visual Studio 2012 require v5
Silverlight Installation