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

Notification

Icon
Error
FileNotFound Exception during Install
Options
Previous Topic Next Topic
sparky
#1 Posted : Wednesday, November 8, 2006 11:11:28 AM(UTC)
Groups: Member
Joined: 11/8/2006(UTC)
Posts: 2
Location: UK, Nottingham
Hi,
Firstly Ulti Cassini looks like it could be the answer to my prayers.... thanks.

I am using Cassini for VS 2005 and an ASP 2 Web Application (Ported from VS 2003).

I have followed your example tutorial and created an installer for my Web Application. The Installer does install Cassini as a prerequiste without problem,
however i get the following error message (Installer is at 100%, all files have been copied at this point):

Exception Occured while initialising the application.
System.io.filenotfound exception, could not load file or assembly
file://c:\windows\system32\TestCo\TestApp\Bin\UltiDevCassiniServerConfiguration.dll

If i look in in c:\program files\TestCo\TestApp\Bin, UltiDevCassiniServerConfiguration.dll exists.

Does anyone have any ideas what could be causing the problem?

Thanks for your help.
Back to top
Ultidev Team
#2 Posted : Wednesday, November 8, 2006 11:53:24 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 didn't see this one before. Obviously, installer thinks your application is getting installed into System32 folder instead of Program Files. Please double-check the folders in the File System view of the setup project. Please be sure you have added UltiDevCassiniServerConfiguration.dll under the Application Folder/Bin:

Also please try to remove custom actions to see whether the problem happens during custom actions execution or before.

Best regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Back to top
WWW
sparky
#3 Posted : Wednesday, November 8, 2006 12:25:20 PM(UTC)
Groups: Member
Joined: 11/8/2006(UTC)
Posts: 2
Location: UK, Nottingham
Thanks for the quick response.

Yes the DLL is under Application Folder\bin.

The file is copied to c:\program files\TestCo\TestApp\Bin\UltiDevCassiniServerConfiguration.dll during installation.

I dont't know if this is relevent but the error appears twice during installation, then the installation is aborted (And undone).

I have removed the custom Actions and afterward the installation runs fine (Other than the web app is no longer registered with Cassini)

I was running the custom install action on Install, Rollback and Uninstall.

Thanks again.
Back to top
Ultidev Team
#4 Posted : Wednesday, November 8, 2006 12:36:49 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)
Hi again!

We are sorry you are going through this, but in our experience VS setup projects have quite a lot of quirks. Our Cassini itself is not much of a trouble, but getting to know VS Setup can be unpleasant in the beginning.

It seems you may have another instance of UltiDevCassiniServerConfiguration.dll inadvertently included in the setup project. Please see if you have two of those and remove one that does NOT point to the correct installation location. Then re-add custom actions again. If you are positive that you have only one instance of UltiDevCassiniServerConfiguration.dll, please consider creating a test setup project from scratch - something seems off with the project as custom actions engine thinks UltiDevCassiniServerConfiguration.dll is installed into sub-folder of System32.

Regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Back to top
WWW
 |  Edit by user
Sumi
#5 Posted : Tuesday, December 12, 2006 9:18:44 AM(UTC)
Groups: Member
Joined: 12/12/2006(UTC)
Posts: 1
Location: Hungary
I also experienced this problem and I could solve this exception only if I didn't change the directory in /AppLocation parameter. If I change it from "[TARGETDIR]\" to anything else, I always had this exception.
Back to top
Ultidev Team
#6 Posted : Tuesday, December 12, 2006 10:04:07 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)
FYI: Changing paremeter value from "[TARGETDIR]\" to something else can actually be done, but path values need to follow some pretty convoluted MSI conventions. Your custom path should not end with single '\' - trailing '\' is a special character reserved for built-in MSI parameters carrying file path values. You could have a path like "c:\folder1", but not "c:\folder1\". If you have to have trailing backslash, you need to double it, like "c:\folder1\\". Similarly, you could have "[TARGETDIR]\SubFolder" or "[TARGETDIR]\SubFolder\\". Again, this is not our invention, it's one of the scary sides of huge, weird beast called MSI API.

Please let us know if this information helped you resolve the problem.

Regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Back to top
WWW
 |  Edit by user
Rss Feed  Atom Feed
Users browsing this topic
Guest
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.

Powered by YAF 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET