VB: Problems with Visual Studio & Multiple Monitors

[specterunseen]

Error occurs during any installation attempted on Visual Studio, .NET framework (any version), Visual C#.
I HAVE to use these and Office 2007 during school, so I need VB to work for this.

Code: Select all

EventType : visualstudio8setup P1 : 10861 
P2 : 9.0.30729.01_orcas_x86_net P3 : msi P4 : inst P5 : f P6 : -
P7 : - P8 : 1601 P9 : - P10 : 



C:\DOCUME~1\Sheldon\LOCALS~1\Temp\WLFC.tmp
C:\DOCUME~1\Sheldon\LOCALS~1\Temp\SDBD.tmp
C:\DOCUME~1\Sheldon\LOCALS~1\Temp\VSW0\VSSWMSISumm ary.txt
C:\DOCUME~1\Sheldon\LOCALS~1\Temp\VSW0\VSSWMSIFail Info.txt
<NoFiles> 

Second problem involves using multiple monitors. Using seamless with multiple monitors is really important, or at least multiple screens if not in seamless. However when enabling VDRP, and attempting to login via RDP, it just shows a black screen. Multiple monitor support when using Visual studio is paramount to me being able to stick with Ubuntu while in school, as I have 3 monitors for programming and class material.

Any help on the multiple monitors? I've googled and worked on this to no avail. FYI, I'm a linux newb. Successfully did my first Xconf edit the other night so don't go above my head!

[Sasquatch]

For the multiple monitor setup, please see the manual for that.

As for the programs itself, it's possible that VB still doesn't like debuggers inside the VM. Or actually the other way around. I'm not sure about recent versions, but older ones had problems with some debuggers like C++.

[davemusic]

I had this problem also when installing VB.net (the one that I downloaded with studio)
it was related to the the C drive filesystem being FAT32 (I think). Anyway - I just made a quick spare vdi of about 6 gigs called it drive D and forced the install to a sub folder on that. - Worked.
As to the multi-monitor - sorry - can't help
Davel

[specterunseen]

Did research the manual and worked on this for hours... this is a two part problem. I appreciate the "check the manual" answer.. but I'm beyond that at this point. Any better pointer ?

I'll Google the VDI issue. This is new to me, any good links to point me to? Thanks!

[specterunseen]

BTW, just found that my drive inside VB is NTSF. So that's not the issue.

[specterunseen]

Code: Select all

You cannot change the location of the component or its subcomponents because the component has already been stored in a different location, or it has a dependency on a file already stored in a different location.

The following programs are causing vertical integration to occur:


{A4418082-E601-3954-805B-D56A2B50EC8B} 

To change the file path, you must uninstall the programs listed above and reinstall them in the location where you want to store the files shared with Visual Studio. 

Here is the core issue I believe. It won't let me choose an alternate install directly. I personally don't know how to mount a new VDI in the VB, but even so, it still comes down to this effecting it.

[davemusic]

Ok, some other thoughts;
I think the version of VS u are using is 8 ?
I was doing VS express version 9. The .NEt framework was 3.5 SP1 and my win guest was XP HOME SP2 and my VBOX is 2.1.2 .......so maybe we're just different.

But, I've just done another install (version 9) with an NTFS drive C and that was good. (I dislike spaces in folder names so I installed to C:\myvs9 - probably not relevant) I installed from an ISO image of the CD/DVD which I attached to the VBOX instance. I always take snapshot B4 an install - just so its easy to backout if I dont like whatever)

The bit about making another VDI drive to attach is done via the "virtual media manager" and create a NEW Dynamically Expanding diskimage....then in the gui with the VM in a "powered off" state - click on the hard disks section clcik the Add and attachment and choose the image u just created in the pulldown. Attach it as IDE (coz I guess that u haven't installed any sata drivers in your XP VM) and then when you start the VM and windoze boots you can go to control panel disk manglement and add in and format up your spare image. Useful later for porting large chunks between VM's (by detach and re-attach)

From what I read in your most recent errror message - I guess you need to either "back out" - by de-installing the lot. Or(probably better) set up a new VM, install XP (again) and try a fresh install. (you might wanna look at the manual regarding immutable images for being able to share - a VM boot drive - once you've got everything nicely configured -makes creating new test environments very easy..... or maybe u prefer nlite).

If you cant get any further then point me to an image/iso of version 8 (assuming i can trial/license it) and I will see if I can get any further.
Regards
Dave