Totzkeeeeee's Blog

Just because I can...

  Home  |   Contact  |   Syndication    |   Login
  216 Posts | 4 Stories | 345 Comments | 321 Trackbacks

News


My blog is worth $14,678.04.
How much is your blog worth?

Tag Cloud


Archives

Post Categories

Blog Roll

Cool Sites

**NOTICE**  What Whidbey meant to say was that it did install but that ABSOLUTELY NOTHING WILL FRICKIN' WORK!! 

We now return to our regularly scheduled program.  Time for bed.

Success at last! While not as tedious as the March install it was still a big PITA. See my previous post for the blow-by-blow commentary.

[UPDATE 2004-06-14]

The final key to a successful install for me was to burn the ISO image to a DVD and then use that in the VPC.  I was trying to install from a network share within the VPC and that may have been causing all of the CRC errors that caused the first “successful“ install to fail.  Everything seems to be working fine and dandy now.

Here's the rundown:

  1. Install XP inside a VPC.
  2. Apply all the patches and reccommended updates from Windows Update.  That's my baseline.
  3. Enable undo disk support so if it bombs you just abandon the changes instead of having to format and start again.
  4. The .NET 2.0 Runtime and the J# redist. stuff installed just fine thank-you very much.
  5. I deselected the following items in the setup program:
    • C++ - I don't use it and it takes up a tonne of space
    • J# - again, I don't use it so why bother to install it
    • Under Visual Basic.NET and C# deselect the VSTO stuff. One error I got was related to Microsoft.Trinity.SmartDocs.dll
    • Under Enterprise Tools, deselect Visual Source Safe.  Gets rid of the error related to Microsoft.VisualStudio.SourceSafe.Interop.dll
    • The problem with CppCodeProvider.dll just seemed to go away although I did replace the file in \VisualStudio\Program Files\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies\GAC with the one in the directory above it.  That may have fixed the problem but I have no way to be sure. NOTE** During the install from the DVD I burned from the image, this error did not occur.
    • Let 'er rip!
    • Reboot a couple of times. Just for laughs.

Dave
Just because I can...(I knew that I could)

 

posted on Tuesday, June 8, 2004 8:15 PM

Feedback

# re: Installing the May Community Preview of Whidbey 6/14/2004 1:13 PM Robz
Anyone else having issues with the May Release not being able to add the any of the items under %Install Root%\Web\WebProjWizards\Common\Items\ to a project while running VS2005? I found that I can't add a Web.config file. This occurs because each of the default.js 's under the main folder do not seem to have anything in them. Of course I ran the ISO buster against the Joliet format. I didn't have the professional to run it against the UDF format.

A quick fix for this I found was to just import them from the March release. That seems to have solved the problem for now.

Comments have been closed on this topic.