Entity Framework Code First Migrations Beta 1 released
Got the news that the migration tool has been updated 5 days ago by the ADO.NET team.
You can get the package from NuGet using the command Install-Package EntityFramework.Migrations or Update-Package EntityFramework.Migrations if you have Alpha 3 installed. Going forward the migration tool will be RTM’ed as part of Entity Framework 4.3.
For someone coming from Alpha, I see a few changes
1. Settings.cs inside Migration folder has been replaced with Configuration.cs. You have to delete the old Settings.ca file
2. ChangeColumn API is now called AlterColumn
Procedure or function expects parameter ‘@something’, which was not supplied.
Where in actually fact I have already insert the parameter into my SQLCommand object. In the end I realize, the problem is not caused by the parameter but the SQLCommand.CommandType; which I had left out. Caused me 1 hour of unproductive time to look for this.
Other common cause which I found online is the use of null value for paramters (especially OUTPUT parameters), you should actually use DBNull.Value.
Cryptic WCF service not found error
When your WCF service returns you the error “The type ‘MyNamespace.MyService’, provided as the Service attribute value in the ServiceHost directive, or provided in the configuration element system.serviceModel/serviceHostingEnvironment/serviceActivations could not be found.” The common culprit will inside the .svc file, you just double check the Code behind file or DLL are deployed in the bin folder. But one rarely known cause is that your WCF service can’t be activated due to missing dependency, which in my case today I realize I didn’t deploy the Sync Framework. So beware, WCF errors can be quite cryptic sometimes.
3rd Party DLL references missing after rebuild?
In Visual Studio 2010, target framework for console, Windows services, and WinForm app is .NET Framework 4.0 Client Profile. When you try to add DLLs such as the famous log4net, you will find VS complains about missing references where you have already added log4net.dll. The problem lies with DLL such as log4net requires the full .NET Framework. So solve this just change the target framework.
