29 June, 2009

Microsoft CRM 4.x and WCF

Today I did an integration between an internal system and Microsoft CRM.

I started out thinking that a WCF Client would be the most “professional” solution for the job; but I came to a brick wall going down that road. Googling the matter, led me to some blogs describing the exact experiences I had with WCF and CRM. It does not work! There is some incompatibility between the way WCF communicates and the CRM WebService (std. ASP.NET asmx webservice). Actually it is pretty strange – as communication between WCF and a traditional asmx-webservice normally is no problem. But – not everything is as it seems.

So to communicate with Microsoft CRM 4.x webservices; you need to go down the old “road” and you will reach your destination. When in Visual Studio, you add a “Web Reference” as you normally do; but instead of just naming the reference and pressing “finish” you press the button on the lowest lefthand corner. This allows you to add a traditional webservice proxy instead of a WCF version.

25 June, 2009

The selected file is not a valid solution file.

Trying to open a solution file from Visual SourceSafe 2005 directly from Visual Studio 2008, I got the above error.

Installing the previously mentions (older post) about a CTP to VSS, failed to solve this. So Goggling again made me encounter the below solution. Which made the error disappear.

  1. Download and install the CTP: Visual SourceSafe 2005 CTP Update
  2. Open cmd-prompt (admin priv.) and enter: regsvr32 “%programfiles%\Microsoft Visual SourceSafe\tdnamespaceextension.dll”

You are good to go and Visual Studio and VSS is working together again.

UPDATE:
I’ve made this work by just “re-registering” the assembly using the regsvr32.exe utility as specified in step (2) above. VS and VSS works together after this.

08 June, 2009

MSI problem: The installer was interrupted before Application could be installed. You need to restart the installer to try again

MSI is a nice little thing to use when deploying and releasing a product. However – it is pretty f*** far from easy to troubleshoot when it decides to fail!

To gain insight into why an MSI-package decided to fail during an installation; you can perform an installation with the logging option enabled like this:

msiexec /i <msi-packagename.msi> /lv installLog.log

Example:
msiexec /i Helloworld.msi /lv installlog.log
This will install the application packed into “HelloWorld.msi” in the current directory and leave a verbose log with the name “installlog.log”. Be prepared for a pretty verbose log with a lot of information inside.

InRiver: Not loading your extensions?

(You really need to in the loop to appreciate the issue this post addresses). Man, I've been fighting this problem for hours before I ...