Visual Studio 2015 now lets developers use Grunt and Bower in certain projects. This is an excellent feature, but I would love to see the same tools and support available for the shared project in a universal WinJS app. It would be great to use Bower to install scripts once into the shared project, rather than installing two copies of the same script into the Windows project and the Windows Phone project.

It makes sense to disallow universal C#/Xaml apps installing packages to the shared project because they might only target Windows 8 or only target Windows Phone. However, it is extremely unlikely that a script installed from Bower will ever differentiate between the two.

Therefore, there should be no problem with installing scripts directly to the shared project using Bower, instead of installing two copies of the same script to two different projects.

I recently had to use this API for a private client certificate. And I was surprised to read in the MSDN that it returns "nothing" as a result of its async call. I would really have thought it returns the just imported pfx.

So here is my scenario and you can clearly see why this API change would help to improve the code flow:

var clientCert;
ensureCertficatesAsync = function() {
logger.trace("Checking client certificate");
if (clientCert) {
logger.info("Using already loaded client certificate");
return WinJS.Promise.as(clientCert);
}
var certQuery = new Certificates.CertificateQuery();
certQuery.friendlyName = "Client Cert";
return Certificates.CertificateStores.findAllAsync(certQuery).then(function(certs) {
if (!certs.length) {
return Windows.Storage.StorageFile.getFileFromApplicationUriAsync("ms-appx:///cert/client.pfx");
}).then(Windows.Storage.FileIO.readBufferAsync).then(function(buffer) {
var pfx = Windows.Security.Cryptography.CryptographicBuffer.encodeToBase64String(buffer);
logger.info("Installing client certificate");
return Certificates.CertificateEnrollmentManager.importPfxDataAsync(
pfx,
"XXXXX",
Certificates.ExportOption.notExportable,
Certificates.KeyProtectionLevel.noConsent,
Certificates.InstallOptions.none,
certQuery.friendlyName
);
}).then(function() { // This search in the store could be omitted
logger.info("Client certificate installed");
return Certificates.CertificateStores.findAllAsync(certQuery);
}).then(function(certs) {
return clientCert = certs[0];
});
} else {
logger.info("Client certificate already installed");
return clientCert = certs[0];
}
});
}

As you can see after installing the pfx I have to query the store again to fetch the pfx to use it in calls to HttpClient with a filter.

This is not a breaking change. Current users are not expecting any return in the success continuation, so they not check for any returned value.

Thanks for consideration!