auto-deploy

[adriann54]

about two weeks ago i attended a 2-day .net "tour" hosted by microsoft<BR><BR>they mainly mentioned things i already knew (luckily my compnay was paying for it instead of me), but they quickly mentioned a feature i found interesting but i can't seem to find any information about how to implement it<BR><BR>i'm talking about "auto-deploy"<BR><BR>apparently, the idea is that by using this feature, one can deploy an application (windows app - non-asp) on an intranet server and then clients within the intranet can basically download a "copy" of the app at runtime, allowing a windows app to follow a model similar to that of an asp app - it should make deployment far easier<BR><BR>at least, that's how i understood it - they rushed right through that particular topic<BR><BR>does anyone know anything about auto-deploy? or where i can find more info? i've been scouring the web all morning with no results<BR><BR>i thank you in advanceat the aforementioned seminar, we were given a set of reference materials - this is what the manual says about auto deployment:<BR><BR>...................................<BR>With a Windows Forms application, it is unnecessary to deploy an application to the end user's desktop. Instead, a user can invoke the application simply by typing a URL into a browser. The application will download to the client machine, run in a secure execution environment and it can remove itself upon completion.<BR><BR>Auto Deployment needs no installation:<BR>? Store the assembly on the Web server<BR>? In the applications, use Assembly.LoadForm<BR>? The application is downloaded, form by form as needed via the HTTP Web server<BR>? It is stored in the GAC and the Internet download cache<BR>? It is only downloaded as needed or when updated<BR>? Dependent components are automatically downloaded to the client so the application "trickles" onto the client<BR><BR>If you use an installer, the installer can download the .NET runtime for installation.<BR>...................................<BR><BR>so, according to the second bullet point, we should use "Assembly.LoadForm" in the application to allow this auto deployment to work<BR><BR>does anyone know how or where exactly to use that? should there be a separate app that uses that call to instantiate an assembly? if so, doesn't that defeat the purpose?<BR><BR>if anyone knows how to implement this, please let me know - i can't find any documentation on it<BR><BR>thank yousince my last post, i have created a simple "hello world" app, compiled it, and placed the .exe file on a server<BR><BR>using IE, i have successfully managed to start up the app by entering its url in the browser<BR><BR>however, doing this starts up 2-3 instances of the app<BR><BR>any ideas anyone? why wouldn't it start up just one?