Not sure if this is the right place to ask there, as I realize we're talking about a thick client through ClickOnce technology published over http. But maybe you can help me work through this.
I have a ClickOnce application published on my website. Say... mywebsite.com/myapplication/myapplication.application
Even if I have a web.config file in the myapplication directory denying anonymous users to that directory, it is still allowing anyone to run the application file. I believe this is because the IIS ISAPI support doesn't perform authentication on extensions it doesn't recognize (i.e. *.application). How can I get around this to publish a ClickOnce application over http to a public website, but restrict download to users/roles?? Any ideas?
...
Go to the complete details ...