<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Workaround for Add-Member on plain .Net objects</title><link>http://blogs.msdn.com/b/powershell/archive/2009/11/03/workaround-for-add-member-on-plain-net-objects.aspx</link><description>Introduction While I was fixing bugs, I came across an interesting bug ( https://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=382818 ) that seemed to have a very simple fix upon first glance. However, after doing some more research</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Workaround for Add-Member on plain .Net objects</title><link>http://blogs.msdn.com/b/powershell/archive/2009/11/03/workaround-for-add-member-on-plain-net-objects.aspx#9920016</link><pubDate>Tue, 10 Nov 2009 07:42:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9920016</guid><dc:creator>Andrew</dc:creator><description>&lt;p&gt;I complained about this exact issue on microsoft.public.windows.powershell roughly two years ago. It's nice to know that some one on the team finally has looked at it. Thank you! =)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9920016" width="1" height="1"&gt;</description></item><item><title>re: Workaround for Add-Member on plain .Net objects</title><link>http://blogs.msdn.com/b/powershell/archive/2009/11/03/workaround-for-add-member-on-plain-net-objects.aspx#9917376</link><pubDate>Wed, 04 Nov 2009 16:23:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9917376</guid><dc:creator>Cash Foley</dc:creator><description>&lt;p&gt;HA! &amp;nbsp;I've had that problem but solved it a different way.&lt;/p&gt;
&lt;p&gt;$table = @{ key1=&amp;quot;val1&amp;quot;; key2=&amp;quot;val2&amp;quot; } &lt;/p&gt;
&lt;p&gt;$table.psobject.members.Add((new-object management.automation.PSNoteProperty &amp;quot;Test&amp;quot;,&amp;quot;TestVal&amp;quot;))&lt;/p&gt;
&lt;p&gt;-PassThru would be easier and I may have stumbled onto it but didn't pickup the pattern.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9917376" width="1" height="1"&gt;</description></item><item><title>re: Workaround for Add-Member on plain .Net objects</title><link>http://blogs.msdn.com/b/powershell/archive/2009/11/03/workaround-for-add-member-on-plain-net-objects.aspx#9917218</link><pubDate>Wed, 04 Nov 2009 09:19:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9917218</guid><dc:creator>Blake</dc:creator><description>&lt;p&gt;This is definitely not the only bug related to bare-objects and psobjects being treated differently. &amp;nbsp; Your blog post prompted me to get around to reporting two other such bugs. &amp;nbsp;Here they are:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="https://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=508091"&gt;https://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=508091&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;and &lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="https://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=508100"&gt;https://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=508100&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9917218" width="1" height="1"&gt;</description></item></channel></rss>