Skip to main content

Installing VS2008 / .NET Framework 3.5 SP1 BETA1

I've been awaiting an improved Entity Framework EDM designer tool since the CTP released in December. Well, with an Entity Framework presentation looming (May 22nd), the Redmond gods responded: VS2008 and .NET Framework SP1 BETA1.

I uninstalled all sorts of CTPs and now am the proud owner of a laptop with VS2008 and .NET 3.5 SP1 BETA1.

Below find the steps I followed. Please heed the warnings and directions within the readme (.NET 3.5 Framework SP1 BETA1, VS2008 SP1 BETA1) explicitly. Also, this is BETA software...expect minor issues and don't install on production equipment.

Scott Gu Braindump
Brian Harry Post

Uninstalled:
Microsoft ASP.NET 3.5 Extensions CTP
Microsoft ASP.NET Futures (July 2007)
ADO.NET Entity Framework Beta3
ADO.NET Entity Framework Tools CTP
Silverlight Tools Beta for Visual Studio 2008
KB949325

Did *not* uninstall:
Microsoft ASP.NET MVC Preview 2
Microsoft Silverlight

Installed:
.NET 3.5 Framework SP1 BETA1
VS2008 SP1 BETA1

Of note:
  • After the .NET 3.5 Framework SP1 BETA1 download completed, I kept being prompted to close the installation before proceeding. Huh? Finally, I simply clicked on Ignore and the installation completed successfully.
  • I had to reboot after the .NET 3.5 Framework SP1 BETA1 installation completed.
  • I needed to locate the vssetup.msi and original Visual Studio installation media to proceed with the VS2008 SP1 BETA1 installation.

Comments

Anonymous said…
Thanks for posting this, Jeff. It's good to know that you got it to work but it's even better to see the specifics of what you did.
Jeff Hunsaker said…
@twwilliams Hey, thanks to you all for delivering this!

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)]

I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent!

I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around.

Thanks in advance!

Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario...
I'm workin…

Shrinking WSS (Sharepoint) SQL Server Log Files

Yesterday, while migrating a source repository from StarTeam to TFS, I received the following error:
"TF30042: The database is full. Contact your Team Foundation Server administrator."Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file.

Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve:

Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here.
Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. The Auto_…