Friday, November 12, 2010

Things I learn new this week

1. Never ever use WCF.

here is why
1. IIS 7 doesn't support .svc file format by default. So you need to install some extension files. so it's lot of work for a new product.

2. I found it very hard to configure security settings. when i tried to configure for the first time it threw all kind of errors.

3. After installing WCF in IIS, sometimes it's trowing an exception that refers to the temp directory. To solve this problem you have to re compile the application and re-distribute

and a lot more...

2. Deploying digitalpersona for Window 7 64bit.

this can be easy but tricky, here is why.

if you are trying to install digitalpersona dlls to a fresh Windows 7 64-Bit PC you should include
DpCore.msm module because this module contains the core files like dphost.exe. surprisingly they have not included those files in DpCore_x64.msm. Dphost to this day remains 32 bit, which is why you need to install both modules. The 64bit module contains some dlls necessary for your 64bit application to communicate with dphost.

3. install location for prerequisites has not been set to 'component vendor's web site' and the file 'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' in item 'SQL Server 2008 Express' can not be located on disk. See Help for more information.

do solve this , you need to download sqlexpr32_x86_enu.exe and place it in
C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\SqlExpress2008\en

4. most of the time when we want to do something small, we write a function. I found this nice piece of code to support kind of inline function

Action d = (bool x) =>
var win = MainWindow as MainWindow;
if (win == null) return;

Dispatcher.Invoke(d, true);

// or


1 comment:

Anonymous said...

It's really not WCF's fault that IIS sucks as a app host. For production-grade WCF, I would **always** recommend using self-hosting - that skips all the IIS messyness, gives you full control over your service config and your endpoints and everything. Try it!