Web Connection
Switching from ISAPI to .NET
Gravatar is a globally recognized avatar based on your email address. Switching from ISAPI to .NET
  Stein Goering
  All
  Feb 2, 2018 @ 09:00am

We've had a couple of different problems come up where it's been suggested that the issue might be resolved by switching to the .NET managed handler.

Our problem is that we've got 100+ legacy customers who are currently running our app using ISAPI. If I'm going to suggest that they make changes to their production servers, I'd like to feel confident that the transition will go smoothly. I haven't seen anything in the docs that addresses how to migrate from ISAPI to .NET (maybe I missed something). Is it just a matter of dropping in the webconnectionmodule.dll and manually modifying web.config?

--stein

Gravatar is a globally recognized avatar based on your email address. re: Switching from ISAPI to .NET
  Rick Strahl
  Stein Goering
  Feb 2, 2018 @ 12:00pm

Stein,

ISAPI and .NET Handlers are pretty much interchangable. I switch between them all the time for testing - all I have to do is change the script map assignments.

The necessary info for that is here:

That topic also outlines the few differences the main one of which is multi-site/virtual support of a single instance, which ISAPI supports but the .NET handler does not. Each Web site/virtual has its own distinct address space and unique instance of the .NET handler running inside of it, while ISAPI modules can be global and apply to multiple sites. This may affect certain multi-tenant scenarios.

Other than that the swap is literally switching the script mappings. I recommend you comment out the old mappings and add the new ones - then it's simply a matter of commenting uncommenting parts of the config file to run either in .NET or ISAPI modes.

+++ Rick ---

Gravatar is a globally recognized avatar based on your email address. re: Switching from ISAPI to .NET
  Stein Goering
  Rick Strahl
  Feb 13, 2018 @ 09:36pm

A lot of our ISAPI sites have been around awhile and still pull config settings from the legacy wc.ini file. Is that going to be an issue when switching to .NET?

On my demo .NET installations (all done more recently) the settings are embedded in the web.config file...

--stein

Gravatar is a globally recognized avatar based on your email address. re: Switching from ISAPI to .NET
  Rick Strahl
  Stein Goering
  Feb 14, 2018 @ 10:57pm

Do you mean your application is pulling data out of the wc.ini file? I hope not 😃

But if you mean whether you have to migrate your wc.ini settings to web.config then the answer is yes - all settings have come out of web.config.

+++ Rick ---

Gravatar is a globally recognized avatar based on your email address. re: Switching from ISAPI to .NET
  Stein Goering
  Rick Strahl
  Feb 15, 2018 @ 06:29am

No app data - just the standard configuration for wc.dll.

Is there anything in the WC tool set that will migrate wc.ini settings to web.config? I'm just thinking about the fact that I have close to 100 sites to convert.

--stein

Gravatar is a globally recognized avatar based on your email address. re: Switching from ISAPI to .NET
  Rick Strahl
  Stein Goering
  Feb 15, 2018 @ 12:06pm

Well almost all of the settings probably stay at default except the COM server names and the paths (if using pre-6.x versions - post 6.x all paths are relative and pretty much all settings except the COM server can be run at default).

Even if that isn't the case I don't think you'd want to automate that process - who knows what settings are in those files.

The way to do it is provide what is a 'standard' version of a Web Config that works with your app and then either automate the process of setting the 2 or 3 values (easy with XMLDOM code) you need to set or document and let your customers do it with very specific instructions.

+++ Rick ---

© 1996-2024