Making FileUp available to ASP.NET for Application Level Accessibility

Before making FileUp available to .NET applications, you must first start by following the directions for installing FileUp for ASP.NET.

Step 1: Add the appropriate FileUp dlls to the bin directory of the application.
The following dlls need to be added to the bin directory of your .NET application:
.dll FileDescription
SaFileUp.dllIncludes the built-in interop support
SAPrgres.dll(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
FileUpModule.dll(Optional). It is recommended that your .NET FileUp application utilizes the HttpModule to overcome .NET performance limitations. Make the HttpModule available by placing the FileUpModule.dll file in the bin directory of your application.

The dlls can be added to the bin directory manually by simply copying the dlls to the bin. If you are using Visual Studio to develop your application, you should add the dlls as a reference to your project. This will automatically copy them to the bin folder of your application as well as make them available to the project during development. Please note that you must click the "Browse..." button in the Add Reference dialog and navigate to them in the FileUp\dotnet directory. They will not be listed in the .NET tab."

Step 2: Update the web.config file for the application.
Under the <configuration> ... <system.web>node in the web.config, update as instructed below.

(Optional). If you chose to implement the (recommended) HttpModule, you must add the following to the web.config file under the <configuration>and <system.web> nodes:

<httpModules>
<add name="FileUpModule" type="SoftArtisans.Net.FileUpModule,
FileUpModule, Version=$fu.version.module.build$, Culture=neutral,
PublicKeyToken=f593502af6ee46ae"/>
</httpModules>
<httpHandlers>
<add verb="*" path="*.uplx"
type="System.Web.UI.PageHandlerFactory"/>
</httpHandlers>

If you are running FileUp on version 2.x of the .NET Framework, your web.config changes to support the module will also include additions to the <compilation> node:

<compilation>
<buildProviders>
<add extension=".uplx"
type="System.Web.Compilation.PageBuildProvider"/>
</buildProviders>
</compilation>
<httpModules>
<add name="FileUpModule" type="SoftArtisans.Net.FileUpModule,
FileUpModule, Version=$fu.version.module.build$, Culture=neutral,
PublicKeyToken=f593502af6ee46ae"/>
</httpModules>
<httpHandlers>
<add verb="*" path="*.uplx"
type="System.Web.UI.PageHandlerFactory"/>
</httpHandlers>
Step 3: Instruct IIS to pass .uplx requests to ASP.NET for processing.

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 Application's App Mappings
  1. Open IIS, right-click your application's virtual directory, and select Properties.

  2. Select the Virtual 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:

Top

Copyright © 2010 SoftArtisans, Inc. All rights reserved.