Arogl Darthu's Blog

MSBuild Exec task - IgnoreStandardErrorWarningFormat

nospam@example.com (Twan Jacobs) — Wed, 01 Jun 2011 12:27:00 +0000

If you are using MSBuild 4.0.30319 and try to set the property IgnoreStandardErrorWarningFormat on the Exec task you might run into the following message error:

error MSB4064: The "IgnoreStandardErrorWarningFormat" parameter is not supported by the "Exec" task.

The solution is very, very simple: be sure to add ToolsVersion="4.0" to the Project tag.

Upgrade test project from VS2005 to VS2010

nospam@example.com (Twan Jacobs) — Mon, 09 May 2011 13:06:49 +0000

The solution contains several projects, including test projects. All of which now target .Net Framework 2.0 (although some already reference .Net Framework 3.0 or 3.5 assemblies). We do not want to upgrade to .Net Framework 4.0 just yet. Goal of the upgrade is to have every project in the solution target .Net Framework 3.5.

After converting the solution to VS2010 most of the projects reference .Net Framework 2.0. Some of which do not build, because of references to assemblies targeted at a higher .Net Framework. Visual Studio 2010 does not allow cross-referencing to higher .Net Framework assemblies. Fixing this problem is quite simple: just re-target the project to .Net Framework 3.5.

All of the test projects have been set to .Net Framework 4.0. One could discuss if this is acceptable for test projects as these will not be released. But for now it was decided to keep every project targeted at .Net Framework 3.5. Fortunately most of the test projects were easily re-targeted to .Net Framework 3.5. Hint: if you run into problems here, make sure VS2010 SP1Rel is installed.

For one of the test projects the solution just would not load it if re-targeted at .Net Framework 3.5. Each time the project was re-targeted, the conversion wizard would just pop up and set it back to .Net Framework 4.0. Eventually we found a workaround by editing the project file by hand after the conversion.

Two manual fixes were needed:

Change reference of "Microsoft.QualityTools.UnitTestFramework" to
<Reference Include="Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=10.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" />
Remove contents of the tag <FileUpgradeFlags>0</FileUpgradeFlags>, which hints VS2010 to start the conversion wizard.

T-SQL: Import csv in temp table

nospam@example.com (Twan Jacobs) — Wed, 13 Apr 2011 09:55:34 +0000

Seems pretty simple to do... Just execute a query like this one:

SELECT * INTO #TESTCSV
FROM OPENROWSET (
        'Microsoft.Jet.OLEDB.4.0',
        'Text;Database=C:\;HDR=YES',
        'SELECT * FROM test.csv')
 

In my case I was getting the following error message, which got me baffled for quite some time:

Msg 492, Level 16, State 1, Line 1

Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name "test#csv.NoName" is a duplicate.

This really didn't make any sense to me. There were no duplicate column names in the csv file and surely there were no columns named 'NoName', nor did I forget to name a column...

Then it came to me: what if UNICODE isn't parsed correctly? Maybe that could cause empty columns headers? The file was exported by ReportViewer and I had not looked at the encoding of the resulting csv file. Guess what!? The encoding was UNICODE. So, after saving the file in ANSI encoding, the query executed like a charm.

Proxy's Dispose results in Exception

nospam@example.com (Twan Jacobs) — Tue, 27 Jan 2009 09:58:10 +0000

A while ago I grabbed a WCF Membership example from here. Now that I've been reading some more on WCF, I stumbled upon the following article: http://msdn.microsoft.com/en-us/library/aa355056.aspx

How do you see this? Have you ever had these 'errors from IDisposable' surface in production? Did you start rewriting every client call with try-catch-finally? Personally I'm a bit appalled by the idea... Using the using statement keeps the code clean.

So I started searching for a solution. This article (WCF Gotcha #1) seems to provide a nice solution, but it's not exactly what I was hoping for.

Ideas are very welcome!
Continue reading "Proxy's Dispose results in Exception"