Providing links to exe files is always a difficult thing to pull off. Lots of browsers will block the download of exe. As will anti virus and organisation group policy.
MS has provided a deployment framework for installing .Net applications. The framework is called ClickOnce.
You can either publish the exe you want installed as a ClickOnce application or create a wrapper which installs the exe if you don't have access to the source.
ClickOnce Deployment [
^]
Also doing a response redirect to an exe file is always a bad idea. Otherwise you could quite intrusively try and force software installation to all of your users.
Browsers are less inclined to block a download if the file is downloaded directly from a user action such as clicking a hyperlink for the exe. Doing a response redirect to an exe is a poor practice.