ASP.NET Web PDF Document Viewer/Editor Control Library

Figure B-1. Sample make file for Drush Make Drush Make files are saved with a .make extension and have a number of capabilities:

If it came from the local filesystem, it will be of the form:

ssrs ean 128, ssrs ean 13, ssrs pdf 417, ssrs code 128, ssrs code 39, ssrs data matrix, c# remove text from pdf, itextsharp replace text in pdf c#, winforms upc-a reader, itextsharp remove text from pdf c#,

Helicon Tech has one free and one fully supported edition of its product. The Ionic extension is free and open source, so we ll configure our application using that. First, we need to download the latest version of the filter from CodePlex. Once we have the latest binaries, we re ready to configure our MVC application to use the ISAPI Rewrite module. The general idea behind our URL rewriting strategy is to do the following:

Figure 11-9 illustrates how multiple stores get involved when you have several users and several different assemblies. User 1 asks MyApp.exe to perform some task, which asks for user/assembly isolated storage. It gets Store 1. Imagine that User 1 then asks MyApp.exe to perform some other task that requires the application to call on MyAssembly.dll to carry out the work. If that in turn asks for user/assembly isolated storage, it will get a different store (labeled Store 2 in the diagram). We get a different store, because they are different assemblies. When a different user, User 2, asks MyApp.exe to perform the first task, which then asks for user/assembly isolated storage, it gets a different store again Store 3 in the diagram because they are different users. OK, what happens if we make two copies of MyApp.exe in two different locations, and run them both under the same user account The answer is that it depends.... If the applications are not signed the assembly identification rules mean that they don t match, and so we get two different isolated stores. If they are signed the assembly identification rules mean that they do match, so we get the same isolated store.

Our app isn t signed, so if we try this experiment, we ll see the standard first run output for our second copy.

Configure ISAPI rewrite to add an .mvc extension to our URLs. Allow IIS to pass the request for the .mvc extension to ASP.NET. Configure our web application to remove .mvc extensions.

Be very careful when using isolated storage with signed assemblies. The information used from the signature includes the Name, Strong Name Key, and Major Version part of the version info. So, if you rev your application from 1.x to 2.x, all of a sudden you re getting a different isolated storage scope, and all your existing data will vanish. One way to deal with this is to use a distinct DLL to access the store, and keep its version numbers constant.

Isolating by domain means that we look for some information about the application domain in which we are running. Typically, this is the full URL of the assembly if it was downloaded from the Web, or the local path of the file. Notice that this is the same rule as for the assembly identity if we didn t sign it! The purpose of this isolation model is to allow a single signed assembly to get different stores if it is run from different locations. You can see a diagram that illustrates this in Figure 11-10.

Download core and contributed modules Check out code from the git, SVN, CVS, and bzr repositories Create a .tar, .gz, or .zip file of all modules defined in the makefile Fetch and apply patches

To get a store with this isolation level, we can call the IsolatedStorageFile class s GetUserStoreForDomain method.

Because our web application removes the .mvc extension before the MVC route handler processes the request, we won t need to change our routing configuration. To configure ISAPI rewrite, follow these steps:

A third level of isolation is by user and application. What defines an application Well, you have to sign the whole lot with a publisher s (Authenticode) signature. A regular strong-name signature won t do (as that will identify only an individual assembly).

If you want to try this out quickly for yourself, you can run the ClickOnce Publication Wizard on the Publish tab of your example project settings. This will generate a suitable test certificate and sign the app.

We need to modify our web application to remove the .mvc extension at the beginning of the request. Place the following code in a custom HTTP module:

To get a store with user and application isolation, we call the IsolatedStorageFile class s GetUserStoreForApplication method.

See the Drush Make project homepage (http://drupal.org/project/drush_make) for syntax, example usage, and more.

So, it doesn t matter which assembly you call from; as long as it is a part of the same application, it will get the same store. You can see this illustrated in Figure 11-11.

This can be particularly useful for settings that might be shared between several different application components.