<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Use PowerShell to Work with the .NET Framework Service Classes</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2010/11/10/use-powershell-to-work-with-the-net-framework-service-classes.aspx</link><description>Summary: Learn how to use Windows PowerShell to work with the .NET Framework service controller classes. 
 
 Hey, Scripting Guy! I am curious about the .NET Framework. I tried to use a .NET Framework class in a Windows PowerShell script recently, and</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Use PowerShell to Work with the .NET Framework Service Classes</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2010/11/10/use-powershell-to-work-with-the-net-framework-service-classes.aspx#3495617</link><pubDate>Wed, 02 May 2012 09:52:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3495617</guid><dc:creator>SConstantine</dc:creator><description>&lt;p&gt;Ditto to Brian&amp;#39;s comment: &amp;nbsp;Many thanks for the explanation behind the Add-Type prerequisite for assemblies, helped me with much head scratching.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3495617" width="1" height="1"&gt;</description></item><item><title>re: Use PowerShell to Work with the .NET Framework Service Classes</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2010/11/10/use-powershell-to-work-with-the-net-framework-service-classes.aspx#3373034</link><pubDate>Fri, 03 Dec 2010 23:01:07 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3373034</guid><dc:creator>ScriptingGuy1</dc:creator><description>&lt;p&gt;Loadwithpartialname has been deprecated for several years and therefore is now listed as obsolete. The problem in Windows PowerShell V1 (when loadwithpartial name was deprecated) is that there was not an easy alternative. The nice thing is in Windows PowerShell V2 is that add-type is even easier to use than loadwithpartialname.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3373034" width="1" height="1"&gt;</description></item><item><title>re: Use PowerShell to Work with the .NET Framework Service Classes</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2010/11/10/use-powershell-to-work-with-the-net-framework-service-classes.aspx#3372970</link><pubDate>Fri, 03 Dec 2010 17:14:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3372970</guid><dc:creator>Brian T. Jackett</dc:creator><description>&lt;p&gt;Thanks for the tip about using Add-Type as the preferred V2 method of loading assemblies. &amp;nbsp;I wasn&amp;#39;t aware LoadWithPartialName was obsolete as I have been using it since V1 and into V2 now. &amp;nbsp;Looks like I have some refactoring to do on my current scripts.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3372970" width="1" height="1"&gt;</description></item></channel></rss>