T
Tim Greenfield
Hello,
Maybe this is old news to some of you but I discovered a really cool
feature... if you put a .NET exe on your web site you can load it from a
client machine by just running the URL. For example:
http://www.myserver.com/something/test.exe
No Open or Save As dialogs... it just runs like a web page would.
It will even grab dependency assemblies as long as they're in the same
folder as the exe on your server. Plus, updates are recognized the next time
you run the app.
There are some security warnings that pop up depending on where you run the
exe from and what your exe does but these can be easily corrected by adding
the website to your intranet zone in IE and specifying a low level of
security for that internet zone in the .NET config wizard.
Why write internal apps in ASP.NET when you can do this!? Windows apps are
so much easier to write and debug and are so much more user-friendly. Good
bye HTML based intranets.
-- Tim
Maybe this is old news to some of you but I discovered a really cool
feature... if you put a .NET exe on your web site you can load it from a
client machine by just running the URL. For example:
http://www.myserver.com/something/test.exe
No Open or Save As dialogs... it just runs like a web page would.
It will even grab dependency assemblies as long as they're in the same
folder as the exe on your server. Plus, updates are recognized the next time
you run the app.
There are some security warnings that pop up depending on where you run the
exe from and what your exe does but these can be easily corrected by adding
the website to your intranet zone in IE and specifying a low level of
security for that internet zone in the .NET config wizard.
Why write internal apps in ASP.NET when you can do this!? Windows apps are
so much easier to write and debug and are so much more user-friendly. Good
bye HTML based intranets.
-- Tim