<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>Contacts Work Item Rss Feed</title><link>http://www.codeplex.com/WorkItem/List.aspx?ProjectName=Contacts</link><description>Contacts Work Item Rss Description</description><item><title>Created Feature: Add property on UserTile to do auto-scaling or cropping on set operations</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=19190</link><description>Usually it&amp;#39;s appropriate to scale down images stored inline in the contact.  It&amp;#39;s better if the library can do this work automatically so client apps don&amp;#39;t have to.&lt;br /&gt;Should add a static boolean property to UserTile or Contact to automatically do the scaling.  Might limit it to Photos that have the UserTile label.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Mon, 27 Oct 2008 00:53:14 GMT</pubDate><guid isPermaLink="false">Created Feature: Add property on UserTile to do auto-scaling or cropping on set operations 20081027125314A</guid></item><item><title>Created Feature: Add support for label combinations in a single string</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=19189</link><description>Should add support for a single string that contains multiple labels, e.g. &amp;#34;Business&amp;#38;Voice&amp;#34;, along with aliases for these in the PropertyLabels class.  It&amp;#39;s not obvious that people need multiple labels for common phone scenarios.  It&amp;#39;s good if I can get intellisense to help with this.  This syntax also potentially opens up the ability to do &amp;#34;or&amp;#34; combinations of labels like &amp;#34;Personal&amp;#124;Business&amp;#34;.  Though probably not going to expose that immediately as part of this feature.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Mon, 27 Oct 2008 00:39:37 GMT</pubDate><guid isPermaLink="false">Created Feature: Add support for label combinations in a single string 20081027123937A</guid></item><item><title>Closed Feature: Need a column chooser in the address book UI</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=8154</link><description>Need a column chooser in the address book.  Needs to persist columns and widths across sessions.&lt;br /&gt;Comments: Will move this item to Conmigo</description><author>JoeCastro</author><pubDate>Mon, 27 Oct 2008 00:36:05 GMT</pubDate><guid isPermaLink="false">Closed Feature: Need a column chooser in the address book UI 20081027123605A</guid></item><item><title>Closed Feature: Include PeoplePicker widget UI</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=12119</link><description>Should have a stock way of selecting contacts from a contact manager.&lt;br /&gt;Comments: Will move this item to Conmigo</description><author>JoeCastro</author><pubDate>Mon, 27 Oct 2008 00:35:44 GMT</pubDate><guid isPermaLink="false">Closed Feature: Include PeoplePicker widget UI 20081027123544A</guid></item><item><title>Closed Feature: Include Group Picker UI</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=12117</link><description>Need a group picker in the Address Book UI.&lt;br /&gt;Comments: Will move this item to Conmigo</description><author>JoeCastro</author><pubDate>Mon, 27 Oct 2008 00:35:28 GMT</pubDate><guid isPermaLink="false">Closed Feature: Include Group Picker UI 20081027123528A</guid></item><item><title>Closed Feature: Include "Me area" UI</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=12118</link><description>Should have easy access to the &amp;#34;Me&amp;#34; contact within the AddressBook UI.&lt;br /&gt;Comments: Will move this item to Conmigo</description><author>JoeCastro</author><pubDate>Mon, 27 Oct 2008 00:35:13 GMT</pubDate><guid isPermaLink="false">Closed Feature: Include "Me area" UI 20081027123513A</guid></item><item><title>Closed Issue: Public static methods on Contact are not thread safe</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=18308</link><description>Contact.GetTypeFromExtension and Contact.GetExtensionFromType are not thread safe and have potential to throw ArgumentExceptions when Contacts are used from multiple threads.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Thu, 04 Sep 2008 00:10:15 GMT</pubDate><guid isPermaLink="false">Closed Issue: Public static methods on Contact are not thread safe 20080904121015A</guid></item><item><title>Created Issue: Public static methods on Contact are not thread safe</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=18308</link><description>Contact.GetTypeFromExtension and Contact.GetExtensionFromType are not thread safe and have potential to throw ArgumentExceptions when Contacts are used from multiple threads.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Thu, 04 Sep 2008 00:02:45 GMT</pubDate><guid isPermaLink="false">Created Issue: Public static methods on Contact are not thread safe 20080904120245A</guid></item><item><title>Closed Feature: Implement managed writeable IContactProperties</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=13311</link><description>Remove the dependency on the Vista IContact APIs.  Utilize the DOM parser to modify the .Contact XML streams.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Fri, 01 Aug 2008 23:15:19 GMT</pubDate><guid isPermaLink="false">Closed Feature: Implement managed writeable IContactProperties 20080801111519P</guid></item><item><title>Closed Issue: Remove assumptions about Xml Namespace prefixes</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=17003</link><description>Parts of the code assume that the XML namespace http&amp;#58;&amp;#47;&amp;#47;schemas.microsoft.com&amp;#47;Contact has the prefix &amp;#34;c&amp;#34;.  When Contacts.Net creates contacts it&amp;#39;s with that prefix.  The Windows version of contacts strictly requires it.  But really there&amp;#39;s no reason to require it for modifications, and right now there&amp;#39;s code that assumes it which may lead to strange, inconsistent results.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Wed, 02 Jul 2008 00:11:22 GMT</pubDate><guid isPermaLink="false">Closed Issue: Remove assumptions about Xml Namespace prefixes 20080702121122A</guid></item><item><title>Closed Feature: Remove Vista-only P/Invoke calls</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=13312</link><description>Remove, or at least provide fallback values, for functions that only exist on Vista.  E.g., finding the location of the Contacts folder.&lt;br /&gt;This in conjunction with the managed IContactProperties reader&amp;#47;writer should allow the API to work on XP.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Wed, 11 Jun 2008 23:50:31 GMT</pubDate><guid isPermaLink="false">Closed Feature: Remove Vista-only P/Invoke calls 20080611115031P</guid></item><item><title>Created Issue: Remove assumptions about Xml Namespace prefixes</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=17003</link><description>Parts of the code assume that the XML namespace http&amp;#58;&amp;#47;&amp;#47;schemas.microsoft.com&amp;#47;Contact has the prefix &amp;#34;c&amp;#34;.  When Contacts.Net creates contacts it&amp;#39;s with that prefix.  The Windows version of contacts strictly requires it.  But really there&amp;#39;s no reason to require it for modifications, and right now there&amp;#39;s code that assumes it which may lead to strange, inconsistent results.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Wed, 11 Jun 2008 22:54:47 GMT</pubDate><guid isPermaLink="false">Created Issue: Remove assumptions about Xml Namespace prefixes 20080611105447P</guid></item><item><title>CLOSED FEATURE: Need ability to query ContactProperty data by name</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=15873</link><description>Clients can only query property metadata by doing an enumeration over a contact.  For some scenarios need the ability to query the ContactProperty metadata by property name.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Mon, 31 Mar 2008 02:11:11 GMT</pubDate><guid isPermaLink="false">CLOSED FEATURE: Need ability to query ContactProperty data by name 20080331021111A</guid></item><item><title>CREATED FEATURE: Need ability to query ContactProperty data by name</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=15873</link><description>Clients can only query property metadata by doing an enumeration over a contact.  For some scenarios need the ability to query the ContactProperty metadata by property name.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Sun, 30 Mar 2008 23:53:39 GMT</pubDate><guid isPermaLink="false">CREATED FEATURE: Need ability to query ContactProperty data by name 20080330115339P</guid></item><item><title>CREATED ISSUE: Windows Bug: WAB UI may update incorrect properties.  Leads to data corruption.</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=15872</link><description>For multi-node values such as Name, PhoneNumber, and EmailAddress, the MAPI UI may read and write to different nodes if a node other than the first contains the &amp;#34;Preferred&amp;#34; label.&lt;br /&gt;E.g.&lt;br /&gt;NameCollection&amp;#47;Name&amp;#91;1&amp;#93; - FormattedName &amp;#61; &amp;#34;First Name&amp;#34; and the node has no labels&lt;br /&gt;NameCollection&amp;#47;Name&amp;#91;2&amp;#93; - FormattedName &amp;#61; &amp;#34;Preferred Name&amp;#34; and the node has the &amp;#34;Preferred&amp;#34; label.&lt;br /&gt;&lt;br /&gt;If you open this contact with the MAPI UI it properly displays &amp;#34;Preferred Name&amp;#34; as the contact&amp;#39;s name.&lt;br /&gt;If you modify the FormattedName in the UI and save it, it incorrectly modifies the node NameCollection&amp;#47;Name&amp;#91;1&amp;#93;.  From the user&amp;#39;s perspective the property cannot be changed.&lt;br /&gt;&lt;br /&gt;This can happen with any multi-node property.  For the home phone number, the labels must look like&amp;#58;&lt;br /&gt;PhoneNumberCollection&amp;#47;PhoneNumber&amp;#91;1&amp;#93; - labels of &amp;#34;Personal&amp;#34;, &amp;#34;Voice&amp;#34;&lt;br /&gt;PhoneNumberCollection&amp;#47;PhoneNumber&amp;#91;2&amp;#93; - labels of &amp;#34;Personal, &amp;#34;Voice&amp;#34;, &amp;#34;Preferred&amp;#34;&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Sun, 30 Mar 2008 23:43:24 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Windows Bug: WAB UI may update incorrect properties.  Leads to data corruption. 20080330114324P</guid></item><item><title>COMMENTED ISSUE: Windows Vista Bug: prevHost.exe crashes when reading windows contact</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=14898</link><description>I am experiencing a bug that causes windows explorer to hang whilst viewing contacts created with Contacts.Net.&lt;br /&gt;&lt;br /&gt;How to reproduce&amp;#58;&lt;br /&gt; 1&amp;#41; Create a contact with an email that has more then one custom label&lt;br /&gt; 2&amp;#41; Open Windows Contacts folder&lt;br /&gt; 3&amp;#41; Select a the contact &amp;#40;only single click to trigger the prevHost to generate a preview&amp;#41;&lt;br /&gt;&lt;br /&gt;If you kill prevHost.exe you will notice that windows contacts continues to function with out the preview windows and the contact is completely valid and can be view or edited. &lt;br /&gt;&lt;br /&gt;I believe that either Contact.NET is producing an invalid contact that the prevHost cant handle or prevHost has a bug that cant handle the contacts with emails with more then one label. Either way I thought this is an issue that needs to be considered for Contacts.NET.&lt;br /&gt;&lt;br /&gt;I have attached an test example that causes this error. If anyone could suggest a work round that would allow me to embed unique id tags to email address that can be read through contacts.net please let me know&lt;br /&gt;Comments: ** Comment from web user: JoeCastro ** &lt;p&gt;Changing some tags to indicate that this is a problem with Windows rather than Contacts.Net&lt;/p&gt;</description><author>JoeCastro</author><pubDate>Fri, 25 Jan 2008 19:41:26 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: Windows Vista Bug: prevHost.exe crashes when reading windows contact 20080125074126P</guid></item><item><title>COMMENTED ISSUE: Windows Vista Bug: prevHost.exe crashes when reading windows contact</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=14898</link><description>I am experiencing a bug that causes windows explorer to hang whilst viewing contacts created with Contacts.Net.&lt;br /&gt;&lt;br /&gt;How to reproduce&amp;#58;&lt;br /&gt; 1&amp;#41; Create a contact with an email that has more then one custom label&lt;br /&gt; 2&amp;#41; Open Windows Contacts folder&lt;br /&gt; 3&amp;#41; Select a the contact &amp;#40;only single click to trigger the prevHost to generate a preview&amp;#41;&lt;br /&gt;&lt;br /&gt;If you kill prevHost.exe you will notice that windows contacts continues to function with out the preview windows and the contact is completely valid and can be view or edited. &lt;br /&gt;&lt;br /&gt;I believe that either Contact.NET is producing an invalid contact that the prevHost cant handle or prevHost has a bug that cant handle the contacts with emails with more then one label. Either way I thought this is an issue that needs to be considered for Contacts.NET.&lt;br /&gt;&lt;br /&gt;I have attached an test example that causes this error. If anyone could suggest a work round that would allow me to embed unique id tags to email address that can be read through contacts.net please let me know&lt;br /&gt;Comments: ** Comment from web user: JoeCastro ** &lt;p&gt;Thanks for reporting this.&lt;br /&gt;It&amp;#39;s a bug in the previewer.  Not actually prevhost, but the previewer that it loads for displaying Contacts.&lt;/p&gt;&lt;p&gt;There is a workaround.  It&amp;#39;s less than ideal, I&amp;#39;ll think more about whether there&amp;#39;s an appropriate way I can hide callers from it...&lt;br /&gt;I should probably caveat it up-front that this isn&amp;#39;t official Microsoft support, and what I&amp;#39;m about to suggest relies on undocumented behavior and shouldn&amp;#39;t be relied upon in future versions of Windows.&lt;/p&gt;&lt;p&gt;The previewer pulls all its details from the registry.  It&amp;#39;s looking for how to display the labels but since the mapping is missing it&amp;#39;s returning an error code out to prevhost.  You can add a string value under &amp;#34;HKCU&amp;#92;Software&amp;#92;Microsoft&amp;#92;WAB&amp;#92;Resources&amp;#92;Labels&amp;#34; where the value name is your label, and the value is however you want it to display in the previewer.  If you want it to be hidden then just leave the value blank.&lt;br /&gt;If you need a reference sample of what this looks like, there&amp;#39;s a similar set of values under &amp;#34;HKLM&amp;#92;Software&amp;#92;Microsoft&amp;#92;WAB&amp;#92;Resources&amp;#92;Labels&amp;#34; for pre-defined labels.  The HKLM key is using indirect resource strings for localization, but you can just put string literals and it will work.&lt;/p&gt;&lt;p&gt;What&amp;#39;s happening is the previewer is bugging out because it doesn&amp;#39;t find the value for the label and it&amp;#39;s incorrectly returning an error code to prevhost.  Not sure why prevhost is responding that way to the error.&lt;/p&gt;&lt;p&gt;Better solutions are I can re-implement the preview pane without this bug in Contacts.Net and include it in the installer, which I wanted to do anyways to add support for groups and businesses, but if you send this contact to someone who doesn&amp;#39;t have the updated preview handler then they&amp;#39;ll still get this behavior.&lt;/p&gt;</description><author>JoeCastro</author><pubDate>Fri, 25 Jan 2008 19:00:20 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: Windows Vista Bug: prevHost.exe crashes when reading windows contact 20080125070020P</guid></item><item><title>CREATED ISSUE: Windows Vista Bug: prevHost.exe crashes when reading windows contact</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=14898</link><description>I am experiencing a bug that causes windows explorer to hang whilst viewing contacts created with Contacts.Net.&lt;br /&gt;&lt;br /&gt;How to reproduce&amp;#58;&lt;br /&gt; 1&amp;#41; Create a contact with an email that has more then one custom label&lt;br /&gt; 2&amp;#41; Open Windows Contacts folder&lt;br /&gt; 3&amp;#41; Select a the contact &amp;#40;only single click to trigger the prevHost to generate a preview&amp;#41;&lt;br /&gt;&lt;br /&gt;If you kill prevHost.exe you will notice that windows contacts continues to function with out the preview windows and the contact is completely valid and can be view or edited. &lt;br /&gt;&lt;br /&gt;I believe that either Contact.NET is producing an invalid contact that the prevHost cant handle or prevHost has a bug that cant handle the contacts with emails with more then one label. Either way I thought this is an issue that needs to be considered for Contacts.NET.&lt;br /&gt;&lt;br /&gt;I have attached an test example that causes this error. If anyone could suggest a work round that would allow me to embed unique id tags to email address that can be read through contacts.net please let me know&lt;br /&gt;</description><author>rnazarian</author><pubDate>Thu, 24 Jan 2008 13:09:10 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Windows Vista Bug: prevHost.exe crashes when reading windows contact 20080124010910P</guid></item><item><title>CLOSED TASK: Migrate IntPtr usage to SafeHandles</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=4522</link><description>SafeHandles are a .Net 2.0 construct that guard against memory leaks in the presence of rude appdomain unload.  The places in the interop layer that use unmanaged buffers referenced by IntPtrs should be moved to SafeHandles.&lt;br /&gt;Comments: This task becomes moot when the interop layer goes away.  Might be worth backporting this to the ContactBridge release if it still needs to exist post 1.0.</description><author>JoeCastro</author><pubDate>Wed, 24 Oct 2007 21:06:26 GMT</pubDate><guid isPermaLink="false">CLOSED TASK: Migrate IntPtr usage to SafeHandles 20071024090626P</guid></item><item><title>CLOSED ISSUE: XML datetime interpretations make incorrect assumptions about time zones</title><link>http://www.codeplex.com/Contacts/WorkItem/View.aspx?WorkItemId=13424</link><description>We&amp;#39;re not explicitly putting &amp;#34;Z&amp;#34; at the end of the serialized datetimes.  When reading I&amp;#39;m assuming it&amp;#39;s there, which isn&amp;#39;t correct as it&amp;#39;s supposed to be read as the date in the current timezone.  Probably best to still keep everything returned viewed as a UTC DateTime, but need to be very explicit when writing.&lt;br /&gt;</description><author>JoeCastro</author><pubDate>Mon, 22 Oct 2007 06:10:21 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: XML datetime interpretations make incorrect assumptions about time zones 20071022061021A</guid></item></channel></rss>