The value for the property "Settings Property Name" is not valid for the current language.

ASP.NET, Linq, Visual Studio 4 Comments »

You might also get a related error when building your ASP.NET project with a Linq to SQL class:

Build failed due to validation errors in myfile.dbml.  Open the file and resolve the issues in the Error List, then try rebuilding the project.

This issue can be resolved by removing all dots from the connection string key in web.config, see here, so

<connectionStrings>
        <add name=”MyApp.Properties.Settings.MyConnectionString” connectionString=”blah”/>
    </connectionStrings>

becomes

      <connectionStrings>
      
 <add name=”MyConnectionString” connectionString=”blah”/>
    </connectionStrings>

Then the build should succeed. If you then reset the connection string key to the one with dots and it will still build but you’ll get this message

The connection property in the web.config file is missing or incorrect. The connection string from the .dbml file has been used in its place.

upon opening the dbml file and the “dotless” connection string will be added to your web.config.

So Linq to SQL doesn’t like the dotted connection string key for some reason.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

The Dark Side Revisited – Darkish Color Themes for Visual Studio

Programming, Visual Studio 8 Comments »

Developers have been experimenting with darker color schemes for Visual Studio, aiming to port their beloved Textmate or Vim environment to other IDEs including VS.

The Textmate Vibrant Ink theme was ported for Visual Studio and recently improved. Zenburn was ported from Vim to Visual Studio.

Collections of other dark color themes can be found here, here, and here. Some like them, some don’t.

I was in the latter group until recently. That was when I came across the Aloha scheme for Netbeans 6, which is based on the work of Carmelyne Thompson inspired by the RubyRobot scheme for Textmate.

I find the colors very enchanting so I went ahead and created an approximation of the Aloha theme for Visual Studio. I made the following changes:

  • Changed the font to Consolas 10 from Monaco 12. You can download the “original” Monaco font for Windows here.
  • Changed the green (102,153,51) strings to a light blue (191,191,255).

Please note that this a just and approximation and not an exact port for every language. Then again, why should it be? You can tweak the settings yourself quite easily in Options>Environment>Fonts and Colors.

Here’s a screen shot:

image

You can download the vssettings file and import it in Tools>Import and Export Settings…

In Visual Studio 2005 you will get a message similar to this:

The file x.vssettings was created with an unsupported version of this application and cannot be added to the settings file list.

Simply open the file in Notepad and replace

<ApplicationIdentity version=”9.0″/>

with

<ApplicationIdentity version=”8.0″/>

and it should import just fine.

One more thing: When you export the font and color settings, deselect all settings first and then just select Options>Environment>Fonts and Colors, so that the Export dialog looks like so:

image

Enjoy!

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Internet Explorer Script Error / Library not registered with Visual Studio 2005

Programming, Visual Studio No Comments »

If you get an error like the above using MSDN help in Visual Studio (or in any other situation) you might try the following:

Go to “Add/Remove Programs”, locate “Microsoft Document Explorer 2005″ and repair it. You will have to restart your computer. Kudos to Steven Cheng for this info posted here.

The issue might be due to a failed or removed Orcas (Visual Studio 2008) Beta installation which corrupted the Document Explorer component on your machine. It’s still advisable to install Orcas Betas on virtual machines only.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

"Unable to find the requested .NET Framework Data provider" with MySQL Connector/Net and Orcas

Programming, Visual Studio No Comments »

If you have MySQL Connector/Net installed and then install Orcas (Visual Studio 2008) Beta 2 (and probably earlier versions), your machine.config file will be changed so that it does not include the MySQL Connector/Net data provider information anymore. This can lead to problems with the DataSet designer, first complaining about the MySQL Connector/Net and then with the message quoted in title of this post. The simple solution is to reinstall the MySQL Connector/Net which will put the necessary provider information back in the <system.data><DbProviderFactories> section of your machine.config and your designers should start working normally again. Hope it helps.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]