Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Registering Application During Post-Install with Packaged Cassini
posaune
#1 Posted : Thursday, July 27, 2006 5:56:28 AM(UTC)
Groups: Member
Joined: 7/19/2006(UTC)
Posts: 5
Location: Canton, OH

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
Ultidev Team
#2 Posted : Thursday, July 27, 2006 6:33:28 AM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,253

Thanks: 28 times
Was thanked: 60 time(s) in 59 post(s)
Hi there!

We too have recently come accross the problem where anything but "[TARGETDIR]\" passed causes the problem. We have checked our code, but the part that might be failing is very trivial - just getting parameter values out of the collection - and looks alright. Debugging that part is a bit tricky. But we will look into this problem anyway and report back.

Meanwhile, as a workaround, please either do registration out of band - in the BAT file as your suggested, or you could implement your own custom action handlers from which you could call registration methods of Cassini Configuration API. You can pass all the parameters to your own Installer class the same way as you pass them to the Installer implemented in the Cassini Configuration assembly.

Best regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Ultidev Team
#3 Posted : Thursday, July 27, 2006 12:58:12 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,253

Thanks: 28 times
Was thanked: 60 time(s) in 59 post(s)
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.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Guest
#4 Posted : Tuesday, March 8, 2016 2:55:31 AM(UTC)
Groups:

Message was deleted by a Moderator.
Rss Feed  Atom Feed
Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You can vote in polls in this forum.