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

TFS Error | The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.

Posting this one for the search engines. If you ever receive the exception "The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.", more than likely, your drive space is at 0 on your TFS application tier box.

I encountered this at a client recently. The root cause was that IIS logs had filled up the OS drive (C:\). I switched IIS logging to the applications drive (D:\) which cleaned up the OS drive and resolved the issue.

Detailed message:


TF53010: The following error has occurred in a Team Foundation component or extension:


Date (UTC): 6/7/2011 4:18:53 PM

Machine: TFSATBOX

Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129519118182628600

Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Service Host: 7ecfbd77-b386-4d75-b038-b05474782696 (DefaultCollection)

Process Details:

Process Name: w3wp

Process Id: 3676

Thread Id: 5752

Ac…

Verified by Visa: Everything We Tell Folks to Avoid

Phishing is defined by F-Secure as: "Fraudulent e-mail or website claiming to be legitimate seeking indentifiable information. Phishing is an attempt to steal your personal data."When I recently attempted an online purchase from WalMart using my VISA card, being a security wanta-be, I immediately thought phishing when redirected to verifiedbyvisa.com and saw this dialog:

Seriously, these folks have to be kidding. You're asking for my personal data during a transaction and claim that's its a service "...at no additional cost." Wow! Thanks...but absolutely not, you jokers. As a malicious thief, I can go a long way with this data.

This is exactly the type of experience which aids malfeasance and the folks trying to steal personal data / identities. How long have we been working to educate folks to avoid providing this type of data under these type of circumstances? Years. And we're just now starting to turn the corner.

VISA, get rid of this! When folks submi…

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_…