Project Designer's Properties Pages Are Inoperable Many Orcas March 2007 CTP testers have reported that the Project Designer's Properties pages don't work. A red ball with an X appears and you receive this error for any page you select:
An error occurred trying to load the page. Microsoft.VisualStudio.Shell.WindowPane.OnCreate()
Update 4/25/2007: This fix does not apply to Orcas Beta 1, which doesn't exhibit the preceding problems. See SQL Server Compact Edition FAILS to connect in Server Explorer with Beta 1 in the ADO.NET Orcas forum.
I experienced the same problem with the Self-Extracting Install on Windows Server 2003 R2 and Vista, as well as the VirtualPC Image on Windows Server 2003 SP1, as the guest OS running on Virtual Server 2005 R2. The Visual Studio Code Name “Orcas” Release Notes accessible from the download pages for the Self-Extracting Install and VirtualPC Image (not the Readme that opens when you click the View Readme button of the VS Orcas setup splash screen) states:
19. Working with Project Designer (Project Properties) is unsupported when the CTP is installed on the same machine as VS 2005 or SQL Server 2005.
Project Designer is the feature responsible for configuring application settings, handling application events, managing settings, managing resources, and working with other properties of the project. This feature currently is not supported in the March CTP if the CTP is installed on the same machine (side-by-side) with VS 2005 or SQL Server 2005. This limitation is caused by a known issue in the setup authoring of this component.
To resolve this issue, it is recommended to either:
- Use the March CTP from a VPC image
- Install March CTP to a different machine without VS 2005 or SQL Server 2005
This defect was known to Microsoft prior to release of the installation bits, so testers should have been warned about the issue in the download pages and ReadMe file that the setup splash screen's View ReadMe button opens.
The VirtualPC Image includes SQL Server 2005 to support Team Foundation Server; removing the SQL Server components doesn't restore Properties pages operability. You must perform a custom install of the Self-Extracting Install version and clear the SQL Server 2005 Express check box to obtain operable Properties pages.
(SQL Server 2005 Compact Edition components don't cause this problem. Rafik Robeal's four Sync Services projects build and run without issues in Orcas March 2007 under Windows Server 2003 R2 and Vista.)
Note: See Feedback: Project properties Panes not created on Orcas CTP Mars for a similar issue under Vista and Forum: Microsoft.VisualStudio.Shell.WindowPane.OnCreate() for several users experiencing the problem. Side Effects of Not Installing SQL Server 2005 [Express]
1. SQL Server Native Client (Sqlncli) for OLE DB and ODBC connections to SQL Server 2000 and 2005 isn't installed.
You can install the X86, X64, or IA64 Package from links on the Feature Pack for Microsoft SQL Server 2005 - February 2007 page or the X86 package (Sqlncli.msi) directly. 2. You can't persist an SQL Server data connection in the Orcas March Server Explorer when running under Windows Vista.
Update 2/7/2007: This problem has been solved by an anonymous commenter. An extra
The Choose Data Source dialog behaves as expected, and selecting Microsoft SQL Server as the Data Source and either .NET Framework Data Provider for SQL Server or OLE DB opens the Add Connection dialog. You can choose a networked instance of SQL Server [Express] in the Server Name list, but the Select or Enter a Database Name list isn't populated with database names. Clicking Test displays the expected (but bogus) message:
If you type a known good database name in the list and then click OK you receive this error message:
Clicking Advanced displays this defective Advanced Properties dialog:
Here's what the Advanced Properties dialog looks like when Orcas March 2007 CTP runs under Windows 2003 Server SP1 or Windows XP SP2:
The same problem occurs when using the dialog to build a connection string from the Properties/Settings page. Typing the approprate connection string in the Settings grid's Values cell doesn't add the required providerName="System.Data.SqlClient" attribute/value pair to the app.config file's <connectionStrings> element. As noted in my earlier Orcas March CTP Available from MSDN post, Windows Vista isn't a supported OS for the Self-Extracting Install version. This problem might explain why. (Vista is a supported OS for the VirtualPC Image version.)
Note: See Feedback: Unable to create data connections in server explorer for another tester with the same problem.
Build Warning about .NET Framework 2.0 update
Building a simple VB project reports in the following warning message:
vbc : warning BC42323: .NET Framework 2.0 update not found. The win32manifest will not be embedded.
The system is using the current version as indicated by this build instruction:
Others have reported similar warnings when building C# projects. So far, I haven't found any problems that I can attribute to an outdated .NET Framework 2.0 version.
Note: See Feedback: C# solution upgrade creates error CS1928 for a similar issue and the Properties pages problem.