Hello Adam
Were you logged onto the machine as an administrator when you attempted to install the Development tools for .NET Framework 3.0 CTP? Runing this setup requires administrative privledges for some of its custom actions.
What operating system did this occur under?
Can you describe if this machine has had previous installs of the framework or the orcas extensions for VS or is this a clean machine that hasn't had anything installed?
Can you describe the order you installed your components?
Thanks
Anthony
1) Administrator - Yes
2) XP SP2, all updates applied according to Windows Update
3) This machine I beleive not. It was paved over before SIGGRAPH. Only 'old' things are VS 2003 and .NET 1.1.
3)Order - .NET 3.0, Windows SDK, Orcas
4) DMP file is on its way
This gets a little tricky without have a repro machine I can put in front of a Dev.
What sku of VS 2005 are you installing, Standard, Professional, Express? I assumed you installed VS 2005 before you installed the items listed in #3 above. The Orcas CTP Development Tools for NetFX 3.0 does not work with VS 2003. This CTP is an add on to VS 2005.
VS 2005 Professional from MSDN DVD's
VS 2005 had been/is still working fine on this machine. I can launch the IDE load a non-trivial application (World Wind) compile and debug just fine. .NET 3.0 seems to be working as well with the AvalonMontage sample app and Microsoft Max.
VS 2003 is also installed on the machine and was installed first. It too is working, I can load the 1.1 version of World Wind, compile and debug as well or create new projects.
Adam
You can use the command "msiexec /i vsextwfx.msi /lvx* install.log" to log the verbose setup log.
Would it also be possible to test this on the new VS 2005 SP1 beta released? The call stack of the dump file you sent me seems similar to some of the bugs we fixed in the VS 2005 SP1.
Anthony
Any clues or are you going to send me over to the SP1 forums now? :-)
Adam