I've written a simple console application in VS what users should retrieve from a website. In IE I'm able to download by right-click -> 'Save target as...', but a simple click on the link drops me the below error.
I've "googled" around and it seems there is no reliable way to force the download and skip the choice of direct running.
Is it possible that my app has some signature or security issues? How can I avoid this error?
*edit: It's just a standalone program, not an installer.
*edit2: Not a duplicate, it has to work on a static html page.
After removing ClickOnce manifest signature I don't get the error, and I can download it without any issues.
Related
I followed the guide HERE to link my app to an https URI. It works perfectly fine during testing, for both Debug and Release versions: when I click a hyperlink for the website, the app is launched instead of Edge. The OnActivated event is triggered and the app goes to the desired page, all well and good.
Keep in mind, I'm not using the LaunchUriAsync technique that opens the link only if the app is in foreground.
But when I uploaded the app to the store and downloaded it on the same device I was testing on, the app is not launched. Instead, the webpage opens in Edge. Why is this happening? Is it really mandatory to do some server-side changes to make this work? I'm afraid I don't have access to that, as my app is a third party alternative.
Can someone informed on this topic tell me how I can go about this?
Also, the app does show up under the "Apps for websites" section in Settings -> System when installed through the Store.
The document has a mistake before 8/26, The Json file name should be "windows-app-web-link", not "microsoft-app-uri-handlers". If you have referenced the previous document to lead to not work, please update.
If you still have issues after updated, please test the configuration of your app and website by running the App host registration verifier tool (Details please see the 'Test it out: Local validation tool' section of https://msdn.microsoft.com/en-us/windows/uwp/launch-resume/web-to-app-linking)
Because according to the document,
all side loaded apps with AppUriHandlers will have validated links for the host on install. You do not need to have a JSON file uploaded to test the feature. It seems may be something wrong with the JSON file so you can have a test.
I have a c# app that users download from a website. I bundle the .exe and some other files in a zip file. The problem is that the Chrome browser has suddenly started showing the following warning when users download my zip file:
"flc-app.zip is not commonly downloaded and could be dangerous"
Here's somebody reporting the same problem.
What do I need to do so Chrome doesn't put up this warning when users download the zip file?
Do I need to sign the app? How do I do that and how much does it cost?
While looking at this, I think I found some apps delivered as zips that weren't signed and didn't cause Chrome to put up the warning. This pop3 utility is provided as an exe rather than a zip. It doesn't appear to be signed and Chrome doesn't warn about it when I download it.
I have seen suggestions elsewhere that registering with Google's WebMaster Tools may fix the problem. That doesn't apply in this case as the website has been registered with Google WebMaster Tools for years.
The best resources are this blog post and this blog post.
To sum up:
Sign you package with an authenticode signature.
Don't be malware (I'm sure you got that covered).
Logo your software (if it's not a browser plug-in).
This can be a frustrating process, so hang in there. Microsoft has not disclosed how many downloads one needs to build a reputation, but in practice once you stop changing the package (the hash is part of the reputation) then you can get past this fairly quickly.
I was able to get around this issue by posting the zip file on my Microsoft skydrive
Its possible to direct link to sky drive files as explained in this guide, the main points are outlined below.
Upload your zip file to your Microsoft skydrive.
Right click on the file and select share.
Click on get a link.
Select the view only option.
Now copy the link and replace 'redir' with 'download' to create a direct link as shown.
https://skydrive.live.com/redir?resid=xxxxxxxxxx&authkey=!xxxxxxxxxx
https://skydrive.live.com/download?resid=xxxxxxxxxx&authkey=!xxxxxxxxxx
I was able to download the file in chrome without it complaining provided that I linked to the file from a https location.
I'm writing a custom WebDav integration for our website and in IE I can use new ActiveXObject to open e.g. Word from javascript then open a file. It's got to be like this to enable the applications WebDav integration, I can't just use a link.
We support Firefox as a browser however and new ActiveXObject doesn't work. I've toyed with writing a Silverlight 4 app which apparently can open Word on the user's desktop or even asking the user to download some sort of Console app that launches Word/Excel/etc. I don't want to do this though and I keep thinking someone must have had this issue before.
So.. is there a way to open Word from Firefox FIRST, THEN open a url from Word.
Cheers,
Adam.
UPDATE: Silverlight 4 no longer an option, don't want to use OOB
Not in plain HTML. But a firefox extension should allow this.
Is it possible give full trust, programmatically to an ActiveX control embedded in a web page?
We are trying to build an activeX dll which creates and open a word document and refreshes its data based on some data from another site. It works fine, if I give the assembly full trust from Administrator Tools -> .net 2.0 configuration tool.
Can this be done through code ?
I don't think so. Code permissions can only be set through the configuration of an application, and even if it can be done through code, then the code that sets them would need to have permission to do this as well. Even then the settings from the web.config or machine.config would take precedence.
The point of these code permissions is that admins are able to control what an application can do. If the AppDommain for your application doesn't have rights to do certain things, why would and ActiveX you create have them?
I can't seem to understand how I can find out what is erroring out when I implement URL Routing on IIS6 and Webforms.
I continue to get 404 errors when I try to access a route.
I add the ISAPI module as described here:
http://blog.codeville.net/2008/07/04/options-for-deploying-aspnet-mvc-to-iis-6/
SO that way ASP.Net handles all the requests, but THEN I get a 404 error just accessing the site.
Is there a way to tell if the URL Routing engine is even getting the request?
UPDATE:
For the 64-bit version of Windows (which I failed to mention) the correct DLL is:
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll
If you're not sure which version (or you want to be sure you get the right path) just copy the value that is in the Executable Path of the “aspx” extension in the ListBox above the WildCard Mapping box.
Here are the exact steps we took to fix this problem, although you may have already done this based on your post. On our development boxes, it worked fine, but not on the Windows 2003 server with IIS6.
In IIS, right click on the Virtual Directory, select Properties.
Under the Directory tab, click the Configuration... button.
Under the Mappings tab, under the Wildcard application maps (order of implementation): click the Insert... button.
Browse and select C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll for 32-bit or C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727 for 64-bit, leave Verify that the file exists unchecked.
Move Up aspnet_isapi.dll to the top of the list.
Click Ok, Ok, and try it. Try recycling the application pool if you don't see it work.
Can you confirm this is a server, not your dev box? Can you confirm that the server has .Net 3.5 SP1?