Hello,

I am using the Cassini dist. package for ASP 1.1 but the problem also occurs with 2.0. After my application is finished installing, and the custom action fires to have cassini register the app, I get a FileNotFoundException. (Could not load file or assembly ...) I have isolated the problem to being with the AppLocation parameter. When the AppLocation parameter is something other than "[TARGETDIR]\" I get the error. However, I do not have a choice in the matter as our application is an integration of three web applications. Each of these applications are already installed on the machine under separate directories. Therefor, after the installation of our application, we need to register each of the other 3 with cassini, none of which will actually be located in [TARGETDIR]. I've tried the following paths:

C:\
C:\company\LongNoSpaceProductName\
C:\company\LongNo~1\

Like I said, each of these paths result in the Exception while using [TARGETDIR]\ works fine (although there is no application actually in that directory).

If there is no fix for this, I assume I can simply put the registration of the applications in a batch file and have that get fired after installation, correct?

Thanks

Well, we figured it out. Path that is passed to an MSI custom action should not contain trailing backslashes - it is a limitation of the Microsoft Installer. This means that instead of "C:\company\LongNoSpaceProductName\" path you should be passing "C:\company\LongNoSpaceProductName". Trailing backslash is reserved for use as the marker for built-in MSI properties that carry paths in them, like [TARGETDIR]\, which is always trailed by "\". We also found that if you do need your parameter to have the trailing backslash, then you can escape it by doubling it like "something\\".

Please let us know if this solved the problem.

All the best,
UltiDev Team.