To make FileUp available to any .NET application, server-wide, add the following dlls to the GAC.

1. Open a command prompt window and move to the directory FileUp\Dotnet.
   For example, enter cd Program Files\SoftArtisans\FileUp\Dotnet.
   
   
2. Enter gacutil /i SAFileUp.dll.



3. (Optional) If you chose to provide support for Progress Indication by registering the SAPrgres.dll file in COM, you must also make this dll available to .NET:
   Enter gacutil /i SAPrgres.dll.



4. (Optional) It is recommended that your .NET FileUp application utilizes the HttpModule to overcome .NET performance limitations. Make the HttpModule available by setting up the FileUpModule.dll file in the GAC:
   Enter gacutil /i FileUpModule.dll

1. Open the file machine.config (located in [Windows directory]\Microsoft.NET\Framework\ [.NET version directory]\CONFIG).
   
   
2. Add the following lines to the assemblies node of machine.config:
   
   <add assembly="SaFileUp, Version=v5.3.1,
Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>
<add assembly="SAPrgres, Version=$fu.version.progress.build$,
Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>
   
   

   The version attribute must correspond exactly to the version of SaFileUp.dll that you added to the GAC. To get the exact version of SaFileUp.dll, right-click the file and select the Properties tab, and check the File version (not the Product version).

   
   
   
3. (Optional)If you chose to add support for the HttpModule, add the following line to the httpHandlers node of machine.config:
   
   <add verb="GET,HEAD,POST" path="*.uplx"
type="System.Web.UI.PageHandlerFactory" />
   
   Add the line above to machine.config before these entries:
   
   <add verb="GET,HEAD" path="*"
type="System.Web.StaticFileHandler" />
<add verb="*" path="*"
type="System.Web.HttpMethodNotAllowedHandler" />
   
   
4. (Optional)If you chose to add support for the HttpModule, add the following to the httpModules node of machine.config:
   
   <add name="FileUpModule" type="SoftArtisans.Net.FileUpModule,
FileUpModule, Version=$fu.version.module.build$, Culture=neutral,
PublicKeyToken=f593502af6ee46ae"/>
   
   

   The version attribute must correspond exactly to the version of FileUpModule.dll that you added to the GAC. To get the exact version of FileUpModule.dll, right-click the file and select the Properties tab, and check the File version (not the Product version).

   
   
   
5. (Optional) If you are using the 2.x version of the .NET Framework and you chose to add support for the HttpModule, you must also add the following to machine.config:
   <compilation>
<buildProviders>
<add extension=".uplx"
type="System.Web.Compilation.PageBuildProvider"/>
</buildProviders>
</compilation>


If you chose to add support for the HttpModule, you must also instruct IIS to allow ASP.NET to process files with the .uplx extension. The HttpModule intercepts requests to files with the extension .uplx. After a request is handled by the HttpModule, the request needs to be forwarded to ASP.NET.

Add .uplx to the Web Site's App Mappings

1. Open IIS, right-click the Web Site, and select Properties.
   
   
2. Select the Home Directory tab.



3. Click Configuration.



4. Select the App Mappings tab.



5. Click Add.



6. Browse to aspnet_isapi.dll (typically in [Windows directory]\Microsoft.NET\Framework\[.NET version directory]\).



7. In the Extension field, enter .uplx.



8. Select All Verbs.



9. Check Script Engine, and click Ok.

Properly configured application mappings for the .uplx extension: