Hans Rasmussen » Visual Studio

Encoding in your Visual Studio project

Hans Rasmussen — Fri, 19 Feb 2010 23:47:26 +0000

Have you experienced problems in your Visual Studio projects that no matter which encoding you try to use in your pages for XML or but still you have problems solving swedish characters such as å, å and ö when posting information to external webservice etc.

Try and configure your application’s web.config file and add encoding to your globalization element and now things are working way better.

fileEncoding=”iso-8859-1″

requestEncoding=”iso-8859-1″

responseEncoding=”iso-8859-1″

This behavior to determine encoding is probably the reason why a WebForm intitially contains no information about encoding at all.

<%@ Page Language=”C#” AutoEventWireup=”true” CodeBehind=”WebForm1.aspx.cs” Inherits=”WebForm1″ %>

http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd“>

http://www.w3.org/1999/xhtml” >

Untitled Page

More information can be found on Microsoft Website regarding Globalization

Adding references to Silverlight toolkit in Visual Studio 2008 and Blend 3

Hans Rasmussen — Fri, 19 Feb 2010 23:43:48 +0000

If you want to learn and develop some Silverlight components (which I do recommend you start learning how to);

Download Microsoft® Silverlight™ 3 Tools for Visual Studio 2008 http://www.microsoft.com/downloads/details.aspx?familyid=9442b0f2-7465-417a-88f3-5e7b5409e9dd&displaylang=en

Download Silverlight Control Toolkit from CodePlex http://www.codeplex.com/Silverlight

Add references to Silverlight Control Toolkit in Visual Studio 2008 and Blend 3, so you can start using it http://blog.enginefour.com/blog/post/Adding-Silverlight-Toolkit-Controls-to-the-Visual-Studio-and-Blend-Toolbox.aspx

CRM Web reference vs CRM SDK

Hans Rasmussen — Fri, 19 Feb 2010 23:21:11 +0000

While working in a project where we integrate with CRM, I noticed how important it is not to mix the ways you can integrate with.

Either you create a reference to the CRM Web service in your Visual Studio project and the proxy classes are generated.

Or you can reference microsoft.crm.sdk.dll and microsoft.crm.sdktypeproxy.dll that exists in the CRM SDK.

You will soon notice that if you create a Request object, or maybe a BusinessEntity, DynamicEntity they are not compatible with eachother, and furthermore they might not even have the same methods and properties.

My recommendation is to use the CRM SDK only and never create a Web reference from within Visual Studio. The CRM SDK objects have more friendly properties and methods.