|
Earn Money Trading Forex Online Paramount Airways Free Data Recovery Cargo Job Portal HSBC Investment Management Cheap Web Hosting Make Trip Cheap Air Travel Leisure Hotel Free Air Travel Mutual Fund Informations Cheapest Cellular Plan Free Sexy Indians Call Center Software Hot Indian |
Programming Help |
Homework Help |
Counseling Astrology Advice | Tarot Advice | Parenting Dating Advice | Love Advice | Divorce Advice Legal Advice | Debt Advice | Career Advice Application Deployment and Isolation What options are available to deploy my .NET applications? The .NET Framework simplifies deployment by making zero-impact install and XCOPY deployment of applications feasible. Because all requests are resolved first to the private application directory, simply copying an application's directory files to disk is all that is needed to run the application. No registration is required. This scenario is particularly compelling for Web applications, Web Services, and self-contained desktop applications. However, there are scenarios where XCOPY is not sufficient as a distribution mechanism. An example is when the application has little private code and relies on the availability of shared assemblies, or when the application is not locally installed (but rather downloaded on demand). For these cases, the .NET Framework provides extensive code download services and integration with the Windows Installer. The code download support provided by the .NET Framework offers several advantages over current platforms, including incremental download, code access security (no more Authenticode dialogs), and application isolation (code downloaded on behalf of one application doesn't affect other applications). The Windows Installer is another powerful deployment mechanism available to .NET applications. All of the features of Windows Installer, including publishing, advertisement, and application repair will be available to .NET applications in Windows Installer 2.0. I've written an assembly that I want to use in more than one application. Where do I deploy it? Assemblies that are to be used by multiple applications (for example, shared assemblies) are deployed to the global assembly cache. In the prerelease and Beta builds, use the /i option to the GACUtil SDK tool to install an assembly into the cache: gacutil /i myDll.dll Windows Installer 2.0, which ships with Windows XP and Visual Studio .NET will be able to install assemblies into the global assembly cache. |
Earn Money Trading Forex Online Paramount Airways Free Data Recovery Cargo Job Portal HSBC Investment Management Cheap Web Hosting Make Trip Cheap Air Travel Leisure Hotel Free Air Travel Mutual Fund Informations Cheapest Cellular Plan Free Sexy Indians Call Center Software Hot Indian |