csUnit - unit testing for .NET

Tracker: Bugs

5 Install fails - Closed ID: 2056397 - ID: 2815572

Last Update: Comment added ( malange )

Details:

Sorry about the slow response - I was away from the office.

I tried to enable the trace as requested in Manfred Lange on 2009-06-24
18:14 with no effect, i.e. there was no trace file generated. Note that
MyDocuments is on the same UNC root as VisualStudio Addins, i.e.
\\mulga\homes$\bfh\My Documents\Visual Studio 2005\Addins.

The error message generated does have a double slash if that helps, i.e.

Could not access network location \\mulga\homes$\bfh\My Documents\\Visual
Studio 2005\Addins

Submitted:

Higgisson ( higgisson ) - 2009-07-02 04:44

Priority:

Status:

Closed

Resolution:

Fixed

Assigned:

Manfred Lange

Category:

Visual Studio Integration (csUnit4VS)

Group:

Version 2.6

Visibility:

Public

Comments ( 8 )

Date: 2009-10-10 21:23 Sender: malange This is fixed in trunk. The fix will be included in the next release. I simply removed the entries from the CustomAction table since they are no longer required anyways. Kind regards, Manfred. --- Manfred Lange. csUnit team member http://www.csunit.org
Date: 2009-10-10 21:23 Sender: malange Fixed in trunk. Fix will also be included in next release.
Date: 2009-10-09 22:39 Sender: snicker7 Okay I just installed Orca and successfully changed the MSI so that I could install. In Orca follow these steps: 1. Open the MSI 2. Go to the "CustomAction" table 3. From the "DIRCA_VS2008ADDINFOLDER" and "DIRCA_VS2005ADDINFOLDER" actions, remove the "\" following the "[PersonalFolder]" 4. Save the MSI and exit Orca. You should be able to install now.
Date: 2009-10-05 23:47 Sender: higgisson Further to Ole Eriksen's comment. The MSI file does indeed have the additional backslash. There is an interesting MicroSoft article that suggests that you can edit the MSI file using the Orca database editor, see http://support.microsoft.com/kb/255905 I haven't had a chance to try this yet.
Date: 2009-09-30 06:14 Sender: oleeriksen I have discovered the same problem, and might have found what causes the probem. I look into the msi file, and I saw a "funny" statement there: something like PersonalFolder = [PersonalFolder]\. It means that the personalfolder (as a string) ends with a backslash. Elsewhere in the msi file I found how to identify the home folder for VSTO2005: ... = PersonalFolder\Visual Studio 2005. And this is not correct, if the personalfolder ends with a \. I do not have the tools to fix it, netiher do I know if I introduce other errors. Hope this will help!
Date: 2009-08-16 23:03 Sender: higgisson A further comment - in the short term I would apprciate being able turn off the integration with VisStudio if this would enable the installation od the csUnitRunner and DLL. Thanks
Date: 2009-08-13 00:24 Sender: higgisson Yes we are using roaming profiles and yes we use active directory. Thanks
Date: 2009-08-12 10:39 Sender: malange Hi, I'm not so sure why the tracing didn't work as expected... Are you using a roaming profile in a domain (active directory)? Kind regards, Manfred. --- Manfred Lange. csUnit developer http://www.csunit.org

Attached File

Changes ( 9 )

Field	Old Value	Date	By
close_date	-	2009-10-10 21:23	malange
assigned_to	nobody	2009-10-10 21:23	malange
artifact_group_id	None	2009-10-10 21:23	malange
resolution_id	None	2009-10-10 21:23	malange
status_id	Open	2009-10-10 21:23	malange
close_date	2009-08-12 10:39	2009-08-13 00:24	higgisson
status_id	Pending	2009-08-13 00:24	higgisson
close_date	-	2009-08-12 10:39	malange
status_id	Open	2009-08-12 10:39	malange

csUnit - unit testing for .NET

Tracker: Bugs

Comments ( 8 )

Attached File

No Files Currently Attached

Changes ( 9 )

About SourceForge

Find Software

Develop Software

Community

Help