I have been a huge fan of jQuery ever since I started working on IdeaPipe about 10 months ago. Mostly because of its simplistic DOM access using standard CSS syntax that we all have to learn anyways in the modern Web 2.0 world. In addition to the ease of finding elements on your page, it also works very nicely with other frameworks, I have used it in combination with Microsoft AJAX, Google’s GData JavaScript, and TinyMCE.

Personally I found this to be amazing news, because Microsoft is shipping an Open Source project, licensed under MIT License, with its flag ship developer tool, Visual Studio.  Maybe if we play our cards right, we can start seeing other projects like NUnit and Moq start to ship with Visual Studio.  I have my fingers crossed.

John Resig the developer of jQuery had this to say on his blog:

Microsoft is looking to make jQuery part of their official development platform. Their JavaScript offering today includes the ASP.NET Ajax Framework and they’re looking to expand it with the use of jQuery. This means that jQuery will be distributed with Visual Studio (which will include jQuery intellisense, snippets, examples, and documentation).

And according to Scott Guthrie, Microsoft is also extending the standard product support to jQuery:

We will also extend Microsoft product support to jQuery beginning later this year, which will enable developers and enterprises to call and open jQuery support cases 24×7 with Microsoft PSS.

This is probably some of the most exciting, because it means that jQuery will be a supported stack in some of the more rigid enterprise development environments that won’t install anything that isn’t supported by Microsoft.  I also beleive this is great news for MVC, because jQuery makes MVC just that much more useful for the average developer.

Visual Studio 2008 SP1

• Improved WPF designers
• SQL Server 2008 support
• ADO.NET Entity Designer
• Visual Basic and Visual C++ components and tools (including an MFC-based Office 2007 style ‘Ribbon’)
• Visual Studio Team System Team Foundation Server (TFS) addresses customer feedback on version control usability and performance, email integration with work item tracking and full support for hosting on SQL Server 2008
• Richer JavaScript support, enhanced AJAX and data tools, and Web site deployment improvements

The .NET Framework 3.5 SP1

• Performance increases between 20-45% for WPF-based applications – without having to change any code
• WCF improvements that give developers more control over the way they access data and services
• Streamlined installation experience for client applications
• Improvements in the area of data platform, such as the ADO.NET Entity Framework, ADO.NET Data Services and support for SQL Server 2008’s new features

Team Foundation Server 2008 SP1

A number of improvements have been made to Visual Studio Team System 2008 Team Foundation including:

Version Control

• Simplified the user experience through cleaner “Add to Source Control” dialogs, drag and drop support to the Source Control Explorer and a much easier to use “Workspace” dialog for working folder mappings.
• Version control now automatically supports non-solution controlled files.
• Various changes to the Source Control Explorer such as a new checkin date/time display column, local path hyperlink support and en editable source location field.

Work Item Tracking

• Microsoft Office 2007 integration is now done using the standard Office “Ribbon” delivering a cleaner and easier to use integration to the different Microsoft Office 2007 products.
• Email integration for work items and links for Team system Web Access to make it easier to use email as part of the development lifecycle.

Visual SourceSafe migration tool

• The migration tool has been dramatically improved through many performance and reliability improvements. SP1 provides support for the elimination of namespace conflicts, automatic solution rebinding, improves timestamp coherency and increases the amount of migration logging information available.

Additional Features

• Support for using SQL Server 2008 with Team Foundation Server.
• Team System Web Access provides “live” links to work items and checkin emails. This improves the customer experience for users who do not use Team Explorer.
• Scripting support for the creation of Team Projects.

Performance and scalability

• With SP1 a large part of the focus was to improve the performance and scalability of Team Foundation Server through changes such as faster synchronization with Active Directory, improved checkin concurrency, a faster way to create source tree branches, online index rebuilding for less maintenance downtime and better support for very large checkin sets.
• Improvements in the number of projects a server can support that make not only the scalability of the server better but also the client experience when connecting to a server with a large number of projects on it.

During the install, of TFS 2008 SP1, I received the error: Failed to call WMI on the RS server.  I did some searching on Google and found a post that I did back in November on the same problem.  I followed my exact same steps and it fixed the issue.  I don’t know why this DNS issue continues to cause Microsoft problems, but I really wish they would fix this bug.

I decided to be one of those early installers that brave the RTM and hope everything has been programed correctly, so my current system doesn’t get blown away in the upgrade process. I have a small in home Team Foundation Server that I use for my home based business and personal coding. So an upgrade is pretty risky, in that I risk loosing everything. Knowing all the risks I decided to move forward and everything was going smoothly with installing Visual Studio 2008 Team Foundation Server, until I ran in to the follow problem.

—————————
Microsoft Visual Studio 2008 Team Foundation Server Setup
—————————
TF220064: An error occurred while the Setup program was querying the settings from the server that is running SQL Server Reporting Services. This error is most likely caused by your account not having the required administrative permissions on the server that is running Reporting Services. Click Next to try again. For more information about this error, see the installation logs. For more information about the installation logs, see “Troubleshooting Installation for Team Foundation” in the Team Foundation Installation Guide.
—————————
OK
—————————

The document above told me to reference this file Drive:\Documents and Settings\SetupAccount\Local Settings\Temp \dd_install_vstf_tfc_90.txt. I found the following reference at the bottom of the log file.

[11/19/07,21:01:32] TFSUI: getcurrenttfsproperties.exe: — STATUS: TfsIntegration..tbl_service_interface has at least one row in it
[11/19/07,21:01:32] TFSUI: getcurrenttfsproperties.exe: — STATUS: Found Reports.ReportsService=http://team.coderjournal.com/ReportServer/ReportService.asmx
[11/19/07,21:01:32] TFSUI: getcurrenttfsproperties.exe: — STATUS: Writing VSTF_RS_SERVER=team.coderjournal.com into C:\Documents and Settings\nick\Local Settings\Temp\SIT41264.tmp\TfsCurrConfig.ini section Config
[11/19/07,21:01:32] Setup.exe: AddGlobalCustomProperty
[11/19/07,21:01:32] TFSUI: ***ERRORLOG EVENT*** : getcurrenttfsproperties.exe: *** ERROR: Failed to call WMI on the RS server. The most likely cause is that the setup user does not have the required permissions: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))
[11/19/07,21:01:32] Setup.exe: AddGlobalCustomProperty
[11/19/07,21:01:32] TFSUI: ***ERRORLOG EVENT*** : getcurrenttfsproperties.exe: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
[11/19/07,21:01:32] Setup.exe: AddGlobalCustomProperty
[11/19/07,21:01:32] TFSUI: ***ERRORLOG EVENT*** : getcurrenttfsproperties.exe: at System.Management.ManagementScope.InitializeGuts(Object o)
[11/19/07,21:01:32] Setup.exe: AddGlobalCustomProperty
[11/19/07,21:01:32] TFSUI: ***ERRORLOG EVENT*** : getcurrenttfsproperties.exe: at System.Management.ManagementScope.Initialize()
[11/19/07,21:01:32] Setup.exe: AddGlobalCustomProperty
[11/19/07,21:01:32] TFSUI: ***ERRORLOG EVENT*** : getcurrenttfsproperties.exe: at System.Management.ManagementScope.Connect()
[11/19/07,21:01:32] Setup.exe: AddGlobalCustomProperty
[11/19/07,21:01:32] TFSUI: ***ERRORLOG EVENT*** : getcurrenttfsproperties.exe: at GetCurrentTfsProperties.WmiHelper.FindAllInstancesOfClass(String wmiNamespace, String wmiClass)
[11/19/07,21:01:32] Setup.exe: AddGlobalCustomProperty
[11/19/07,21:01:32] TFSUI: ***ERRORLOG EVENT*** : getcurrenttfsproperties.exe: at GetCurrentTfsProperties.WmiHelper.FindSqlRsInstance(String reportServerHostname, String databaseInstanceName, String dataSourceString)
[11/19/07,21:01:32] TFSUI: getcurrenttfsproperties.exe: Process exited with exit code: 15[11/19/07,21:01:32] TFSUI: Done calling CheckExistingTfsInstallation in GetTfsPropertiesFromDt
[11/19/07,21:01:32] vs70uimgr: Entering DisplayMessage() method.
[11/19/07,21:01:32] vs70uimgr: DisplayMessage_START:TF220064: An error occurred while the Setup program was querying the settings from the server that is running SQL Server Reporting Services. This error is most likely caused by your account not having the required administrative permissions on the server that is running Reporting Services. Click Next to try again. For more information about this error, see the installation logs. For more information about the installation logs, see “Troubleshooting Installation for Team Foundation” in the Team Foundation Installation Guide.
[11/19/07,21:01:33] vs70uimgr: DisplayMessage_END:TF220064: An error occurred while the Setup program was querying the settings from the server that is running SQL Server Reporting Services. This error is most likely caused by your account not having the required administrative permissions on the server that is running Reporting Services. Click Next to try again. For more information about this error, see the installation logs. For more information about the installation logs, see “Troubleshooting Installation for Team Foundation” in the Team Foundation Installation Guide.

From what I could tell the problem was in the database TfsIntegration..tbl_service_interface and had something to do with the follow record.

3 ReportsService http://team.coderjournal.com/ReportServer/ReportService.asmx

So on a hunch I just changed the above to. (TEAM-SERVER is the name of my server)

3 ReportsService http://TEAM-SERVER/ReportServer/ReportService.asmx

Then I continued with the installation and everything proceeded as Microsoft envisioned.