Change the Default VS2010 Start Page “Language”

When you first run Visual Studio 2010 (VS2010), it asks you to select a profile (e.g. C#, C++).  This determines the Start Page displayed when VS2010 starts.  Once you pick this, there appears to be no easy way to change your selection (at least none that I’ve found).  To see which start pages are available to you, look in the following directory:

32-bit Windows: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\StartPages\en
64-bit Windows: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\StartPages\en

Note: you may also need to change your language directory from “en” to your local environment.

You will potentially see a number of files named “Links.<Version>.<VS2010-Language>.xml”.  The part we’re interested in is the <VS2010-Language>, e.g. CSharp, FSharp, VC.

To determine which page you current use, browse in Regedit.exe or use the following command:

reg query HKCU\Software\Microsoft\VisualStudio\10.0\StartPage\Default /v Links

You should see a result similar to the following:

Links    REG_SZ    CSharp

If you wish to change this to a different setting, pick another <VS2010-Language> from the list you saw in your StartPages directory, such as “VC”.  You can make this change in Regedit.exe or use the following command:

reg add HKCU\Software\Microsoft\VisualStudio\10.0\StartPage\Default /v Links /t REG_SZ /d VC /f

Now restart VS2010 and you will see your new Start Page.

Integrate the Windows SDK v7.1 with VS2010

Final Solution: I figured it out!  Open your project in VS2010, select the Project menu and choose Properties…, and click the dropdown next to Platform Toolset.  You can select between v100 (VS2010), v90 (VS2008), and Windows7.1SDK.  Select the 7.1 SDK and click OK.  Now you’re all set.  Note that you can use v90 to build apps that compile for older versions of Windows as long as you have VS2008 already installed on your machine.

Visual Studio 2010 Project Properties


The information below is just kept to remind me what I did.  It isn’t terribly important.


Update: I have found that the best way to utilize the V7.1 SDK is to launch VS2010 from a Windows V7.1 SDK Command Prompt.  If I find a better way, I will post it here.

So, I realized today that I’m still building against the v7.0A SDK that ships with Visual Studio 2010 (VS2010).  While not a crime, I wanted to make sure that I was building against the latest and greatest SDK.  To change the version of the current SDK in VS2010, follow these directions:

  1. In Visual Studio 2010, open a solution (.sln) file or create a solution.
  2. In Solution Explorer, right-click the solution node and then click Properties.
  3. In the Configuration list, select All Configurations.
  4. Under Configuration Properties, select General.
  5. As the Platform Toolset option, select Windows7.1SDK.
  6. Click OK.

(Copied from MSDN :

However, I found that this didn’t completely solve my problem.  I had converted this VS2008 project to VS2010 before setting the SDK version and some of the project settings still pointed to the SDK V7.0A directories!  How frustrating!

The following environment variable directories within VS2010 had been updated correctly or added:

  • $(ExcludePath)
  • $(ExecutablePath)
  • $(IncludePath) — mostly correct
  • $(LibraryPath)
  • $(PlatformToolset)
  • $(PlatformToolsetVersion)
  • $(WindowsSdkDir)
  • $(WindowsSdkMSBuildTools)
  • $(WindowsSdkNetFx35ToolsDir)
  • $(WindowsSdkNetFx40ToolsDir)
  • $(WindowsSDKVersionOverride)

But the following had not:

  • $(FrameworkSDKRoot)
  • $(SDK35ToolsPath)
  • $(SDK40ToolsPath)

I did find hard-coded references to the V7.0A directory in my solution’s .suo file, so I deleted it; this did not correct the problem.

I found the following entries in the registry that pointed to my V7.0A entries:


  • FrameworkSDKRoot (REG_SZ)
    • $(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A@InstallationFolder)
  • SDK35ToolsPath (REG_SZ)
    • $(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A\WinSDK-NetFx35Tools-x86@InstallationFolder)
  • SDK40ToolsPath (REG_SZ)
    • $(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A\WinSDK-NetFx40Tools-x86@InstallationFolder)

Howto make MySQL & Entity Framework work with your website when your hosting company does not have Connector/Net installed

I installed MySQL’s Connector/Net v6.2 on my dev machine and used the Entity Framework to query a MySQL server without any problems.  Then I uploaded the same code to my hosting company’s server and I kept getting errors telling me “Unable to find the requested .Net Framework Data Provider”.  In order to make it work, I had to do the following:

  1. Uploaded MySql.Data.dll to my bin directory
  2. Uploaded MySql.Data.Entity.dll to my bin directory
  3. Added the following lines to my web.config file:

<?xml version=”1.0″?>



<add name=”MySQL Data Provider” invariant=”MySql.Data.MySqlClient” description=”.Net Framework Data Provider for MySQL” type=”MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=, Culture=neutral, PublicKeyToken=c5687fc88969c44d” />




I hope this saves someone else some headaches!


Win7 on JFL92 / PowerNotebook PowerPro P 11:15

After installing Windows 7 x64 on my PowerPro P 11:15, I still had some devices in Device Manager without drivers.  Included in this list were the following:

Base System Device

  • Hardware ID: PCI\VEN_1180&DEV_0843&SUBSYS_002514C0&REV_12
  • This is actually a “Ricoh SD/MMC Host Controller”
  • Solution: Installed setup.exe from \08.CardReader\3.51.01(WHQL).zip

Base System Device

  • Hardware ID: PCI\VEN_1180&DEV_0592&SUBSYS_002514C0&REV_12
  • This is actually a “Ricoh Memory Stick Controller”
  • Solution: Installed setup.exe from \08.CardReader\3.51.01(WHQL).zip (solving the Ricoh SD/MMC Host Contoller above will solve this simultaneously)

PCI Memory Controller

  • Hardware ID: PCI\VEN_8086&DEV_444E&SUBSYS_444E8086&REV_01
  • This is actually the “Intel Turbo Memory Controller (Robson cache)
  • I still haven’t gotten this working.

Unknown Device

Unknown Device

Equivalent Notebook Models

PowerPro P 11:15

Compal JFL92

Similar to Sager NP2090/COMPAL IFL90/PowerPro J 10:15 — these are all the same model and are lower-end than the NP2092

According to Sager, the NP2090, NP2092, FL90, and JFL92 all use the same drivers


Load more