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

Notification

Icon
Error
The reproduce of CassiniMetabase.xml bug.
Options
Previous Topic Next Topic
Royhwa
#1 Posted : Thursday, June 29, 2006 8:38:12 PM(UTC)
Groups: Member
Joined: 6/29/2006(UTC)
Posts: 10
Location: China
It appears like this.




How to reproduce this?
1. I am a programmer. According to http://ultidev.com/Produ...Guide.htm#SetupProject, I build my setup project named calweb.msi.
In this guide, CassiniExplorerMergeModule.msm is not asked to include. But if not, http://localhost:7756/GoToApplication.aspx?AppID=**** will not work. Beacause GoToApplication.aspx is in CassiniExplorerMergeModule.msm. If i set /AppPort="802" or some other port. GoToApplication.aspx is not needed any more. So there are two choices. If to use GoToApplication.aspx, CassiniExplorerMergeModule.msm must be included in setup project. Or set /AppPort in install operation.
Any way, after read this guide, i build calweb.msi at port 801 without CassiniExplorerMergeModule.msm.

2. Send this msi file to client whose computer is a cassini clean system. I mean there is no Cassini1ServerRC1.exe and any other setup projects which created in VS2003 with cassini. And there does not exist this file C:\Documents and Settings\All Users\Application Data\UltiDev\Cassini\CassiniMetabase.xml.
The client run calweb.msi.
If you want to test in the same computer with step 2, you have to uninstall Cassini1ServerRC1.exe and other cassini setup projects from control panel. And delete C:\Documents and Settings\All Users\Application Data\UltiDev\Cassini\CassiniMetabase.xml.

3. In a cassini clean system, i run calweb.msi. Everything is OK.

4. Some code in my project changes. So a newer msi file released. Client uninstalls calweb.msi from control panel. But error comes!!!



Look at CassiniMetabase.xml. If there is only one <Application>, after uninstall from control panel, it is like this.
<?xml version="1.0" encoding="utf-8"?>
<CassiningMetabase xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />

I think that if there is no <Application> in this xml, CassiniMetabase.xml should be delete. In step 4, if i delete CassiniMetabase.xml, newer msi can be install.
And in step 2, the CassiniDevGuide.htm should declare clearly that CassiniExplorerMergeModule.msm must be included in setup project.
Back to top
WWW
 |  Edit by user
Ultidev Team
#2 Posted : Friday, June 30, 2006 3:37:39 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, Royhwa!

Thank you for using UltiDev Cassini Web Server. The merge module with the Cassini Explorer should be automatically added to the Detected Dependencies bin of your setup project by the Visual Studio after you added Cassini Server merge module, like on the picture below (this is the picture from the developer's guide):


Sometimes Visual Studio will have Detected Dependencies bin all wrong. In our experience this happens when you try to build a setup project of the product that is already installed on your box. For this reason we always follow these steps when building a setup project on development machines if we believe Detected Dependencies are messed up:
- Uninstall the product we are going to build.
- Right-click Detected Dependencies and select Refresh Dependencies - after this Detected Dependencies bin should get all its items back in order. In this case you should see the presence of Cassini Explorer merge module.
- Build the setup project.

We outlined the problem with Visual Studio messing up Detected Dependecies in the very last pargraph of the Developer's Guide.

Please let us know if this helped.
Best Regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Back to top
WWW
Royhwa
#3 Posted : Friday, June 30, 2006 4:28:31 AM(UTC)
Groups: Member
Joined: 6/29/2006(UTC)
Posts: 10
Location: China
In vs2003, the CassiniExplorerMergeModule.msm was not added automatically. I added it manually.

And Cassini1ServerRC1.exe seems to have some problem when dealing with empty xml file. I have to ask my clients to delete that xml file manually.
<?xml version="1.0" encoding="utf-8"?>
<CassiningMetabase xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />

My latest setup project includes CassiniExplorerMergeModule.msm, it work smartly.

Thanks ultidev.
Back to top
WWW
Ultidev Team
#4 Posted : Friday, June 30, 2006 6:44:59 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)
If Visual Studio failed to add the Cassini Explorer merge module automatically, then you did the right thing by adding it to your project manually. We are happy you have found a workaround.

All the best,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Back to top
WWW
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