How to configure configure a WAMP server to support Firebird SQL

Adding Firebird support to your WAMP installation is an straightforward step by step process.
I have found an excelent post at Lorenzo’s Alberton blog. This article really helped me to go directly to the point, even seven years after being published.
Just as a litle contribution, I’d like to mention php.ini file is located into the Apache’s bin folder.
In my installation, this folder is C:\wamp\bin\apache\apache2.2.22\bin

After uncommenting the line


and restarting apache, it just worked!
Let´s see the Wamp server dashboard to check the newly loaded module.

You can also check your phpinfo script to see your PHP installation is now Interbase (Firebird) compliant.

phpinfo script

Improving software development process using BDD

Let’s look at this post about Behavioural Driven Development I have writen for Belatrix’s Blog. It’s the first of a series of posts I’ll write to highlight the benefits of implementing BDD as development process.

Here’s the link Using Behavior-Driven Development (BDD) to improve software development

Creating a sitemap for search engine optimization

A sitemap is a list, used to enumerate pages of your site and make them easier to be crawled by search engines.

By using a sitemap, you help crawlers to find pages into your site that couldn’t be indexed automatically. Pages with dynamic content, broken links, etc are good samples.

Mayor Search Engines, like Google, Yahoo and MSN have adopted and supported the ‘s protocol, which defines the XML structure a sitemap file must have.

If you are a WordPress user, there’s a plugin you can use to create your sitemap automagically through the administration section.

Once your sitemap file is created, you can inform search engines let’s start crawling using it. There are three basic procedures to do that,

  • Using search engine submission tool
  • Referencing your sitemap file in robots.txt
  • Making an HTTP Request

Unit Test Adapter threw exception: Type is not resolved for member ‘FluentNHibernate.Cfg.FluentConfigurationException,FluentNHibernate

I’ve seen this error while running my test project from Visual Studio.

Type Is Not Resolved Exception

Although, I tried several solution alternatives, I couldn´t find a good one. These are some posts I followed,

I finally found the solution by catching the real exception as follows.

  • Fisrtly, I added a try catch block in the line where the exception was being raised. After all, the Type Is Not Resolved exception didn’t give enough information to infer what was wrong.
  • In second place, I debugged setting a break point just after the catch statement


Type Is Not Resolved Exception Detail

  • The I could find the real exception, which said,

The following types may not be used as proxies: SolutionName.Core.ClassName: method InitializeMembers should be ‘public/protected virtual’ or ‘protected internal virtual’

One of my Core classes (one of the classes mapped by NHibertane to the database)  was calling a method named InitializeMembers in the constructor and this method’s signature was public void.

  • I finally fixed it by changing the method’s signature as shown in the image bellow

Reduce the scope of initialization method to private or protected internal

WCF – Error 500.21 Handler svc-Integrated has a bad module ManagedPipelineHandler in its module list

If you have received this error while trying to launch a WCF service on a new server installation.
It’s produced by a missing module registration. To fix it, simply registering aspnet modules again.

1) Open a command prompt window (It could be a Visual Studio Command Prompt)
2) Run aspnet_regiis -i
aspnet_regiis command

That’s it.

Try to launch your service again. It should be working.

Configuration binding extension ‘system.serviceModel/bindings/webHttpBinding ‘ could not be found. Verify that this binding extension is properly registered in system.serviceModel/extensions/bindingExtensions and that it is spelled correctly.

I found this error while trying to get the service wsdl.

Configuration binding extension ‘system.serviceModel/bindings/webHttpBinding ‘ could not be found. Verify that this binding extension is properly registered in system.serviceModel/extensions/bindingExtensions and that it is spelled correctly.

Please, notice that there’s a blank space at the end of webHttpBinding

To fix this issue, simply remove that from the configuration file =)

Translate »