A picture is worth a thousand words.
Same text acceleration technologies didn’t pan out so well in WPF. Hitting IE9 Compatibility View button fixes things, but is that a solution or a workaround? ![]()
smart? mobile? managed? Random thoughts by Dario Fruk
A picture is worth a thousand words.
Same text acceleration technologies didn’t pan out so well in WPF. Hitting IE9 Compatibility View button fixes things, but is that a solution or a workaround? ![]()

Find PPTX slides and VS2010 demo sources for my KulenDayz 2010 session here:
Read more about my thoughts and observations on Rx Framework here in coming weeks… ![]()
If you don’t like default Visual Studio 2010’s default UI colors:
…download Visual Studio Color Theme Editor (http://visualstudiogallery.msdn.microsoft.com/en-us/20cd93a2-c435-4d00-a797-499f16402378)
Try some built-in themes, or configure you’re own…

If you’re running Outlook 2007 with Dynamics CRM 4.0 Outlook Client, you’re probably wondering if the CRM client will continue to work…
Short answer is: YES!!! ![]()
The trouble is installation process: works only on 32-bit Office, cannot be installed on Outlook 2010 (installer will complain that supported Outlook is not installed) – you have to upgrade Outlook 2007 with already installed CRM client.
After upgrade you’ll have to reenable CRM add-in by visiting “Add-ins” in “Outlook Options”: Office Button > Options.
UPDATE 12/3/2009:
Outlook 2010 Beta and CRM Client Update Rollup 7 work and play like a charm! Just install from a link on a CRM page. No more upgrades from Office 2007 needed, but 32-bit Outlook is still a requirement.
Annoyances like pop-up warnings with IE8 are still “in-the-box!”…
But terrible startup when CRM server not available is SOLVED!!!! In mere seconds Outlook will report that CRM server is not available and continue loading without blocking… WOHOO!
![]()
There seems to be a recurring issue with MOSS deployments where DCOM security is not properly configured. You’ve maybe seen this one:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
and APPID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user <domain>\<user> SID (S-1-5…) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
You’ll find a workaround here: http://www.itexperience.net/2008/03/29/event-10016-the-application-specific-permission-settings-do-not-grant-local-launch-permission-for-the-com-server-application/, but if you’re running Windows Server 2008 R2 then you’ll also need this one: http://www.wictorwilen.se/Post/Fix-the-SharePoint-DCOM-10016-error-on-Windows-Server-2008-R2.aspx.
Finally a full fidelity interface in a browser of your choice… Did you notice in picture that IE8 is the only one that is not loading favicon? :)
ISA and TMG both support customizing default logon page for OWA publishing and can be found here: Customizing HTML Forms in ISA Server 2006. Although procedure is equal for TMG, folders are a bit different… For ISA 2006 folders with web files are located in <ISA Server Installation Directory>\CookieAuthTemplates\ but for TMG (Beta) they are at <ISA Server Installation Directory>\Templates\CookieAuthTemplates.
Starting from today our OWA logon page sports a brand new and modern look:
Technorati Tags: TMG,OWA,Exchange,HTML,Server,CookieAuthTemplates,Beta,Templates,logon page