<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Jack @ ASP.NET &#187; Programming</title>
	<atom:link href="http://jack-fx.com/net/category/programming/feed/" rel="self" type="application/rss+xml" />
	<link>http://jack-fx.com/net</link>
	<description>As a software developer, I still Focus on .NET, internet, asp.net, C# and so on. I</description>
	<lastBuildDate>Thu, 24 May 2012 14:08:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>logging in Django</title>
		<link>http://jack-fx.com/net/2012/05/24/logging-in-django/</link>
		<comments>http://jack-fx.com/net/2012/05/24/logging-in-django/#comments</comments>
		<pubDate>Thu, 24 May 2012 14:08:00 +0000</pubDate>
		<dc:creator>Jack</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[apache log]]></category>
		<category><![CDATA[django]]></category>
		<category><![CDATA[logging feature]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[tmp]]></category>

		<guid isPermaLink="false">http://jack-fx.com/net/?p=304</guid>
		<description><![CDATA[Logging to console 1. Use Print e.g. def index(req): &#160;&#160;&#160; print “hello!” and you will see the &#8216;hello!’ on your console. (or apache log if running on linux) 2. Use Python logging feature # in settings.py import logging logging.basicConfig( &#160;&#160;&#160; level = logging.DEBUG, &#160;&#160;&#160; format = ‘%(asctime)s %(levelname)s %(message)s’ ) # write log import logging [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/net/2012/05/24/logging-in-django/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PyDev &#8211; an Eclipse plugin for Python(Django)</title>
		<link>http://jack-fx.com/net/2012/03/21/pydev-an-eclipse-plugin-for-pythondjango/</link>
		<comments>http://jack-fx.com/net/2012/03/21/pydev-an-eclipse-plugin-for-pythondjango/#comments</comments>
		<pubDate>Wed, 21 Mar 2012 14:00:00 +0000</pubDate>
		<dc:creator>Jack</dc:creator>
				<category><![CDATA[Others]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[code completion]]></category>
		<category><![CDATA[code coverage]]></category>
		<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[eclipse plugin]]></category>
		<category><![CDATA[location]]></category>
		<category><![CDATA[Project]]></category>
		<category><![CDATA[PyDev]]></category>
		<category><![CDATA[python ide]]></category>
		<category><![CDATA[string substitution]]></category>

		<guid isPermaLink="false">http://jack-fx.com/net/?p=282</guid>
		<description><![CDATA[PyDev is a Python IDE for Eclipse, which may be used in Python, Jython and IronPython development. It comes with many goodies such as: &#160;&#160;&#160; Django integration &#160;&#160;&#160; Code completion &#160;&#160;&#160; Code completion with auto import &#160;&#160;&#160; Syntax highlighting &#160;&#160;&#160; Code analysis &#160;&#160;&#160; Remote debugger &#160;&#160;&#160; Tokens browser &#160;&#160;&#160; Interactive console &#160;&#160;&#160; Unittest integration &#160;&#160;&#160; [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/net/2012/03/21/pydev-an-eclipse-plugin-for-pythondjango/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Duplicate Code</title>
		<link>http://jack-fx.com/net/2011/12/19/duplicate-code/</link>
		<comments>http://jack-fx.com/net/2011/12/19/duplicate-code/#comments</comments>
		<pubDate>Mon, 19 Dec 2011 12:54:00 +0000</pubDate>
		<dc:creator>Jack</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[clone]]></category>
		<category><![CDATA[clones]]></category>
		<category><![CDATA[code blocks]]></category>
		<category><![CDATA[Duplicate]]></category>
		<category><![CDATA[equivalent]]></category>
		<category><![CDATA[high risk]]></category>
		<category><![CDATA[ramp]]></category>
		<category><![CDATA[time copy]]></category>

		<guid isPermaLink="false">http://jack-fx.com/net/2011/12/19/duplicate-code/</guid>
		<description><![CDATA[Duplicate code, sometimes referred to as clones, is a cluster of code blocks that are functionally equivalent (or nearly equivalent) spanning across two or more locations within a solution. Duplicate code is expensive to maintain because: Multiplied bugs. A bug in one clone means there’s a bug in all the copies. This can lead to [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/net/2011/12/19/duplicate-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pipeline in PowerShell</title>
		<link>http://jack-fx.com/net/2011/04/20/pipeline-in-powershell/</link>
		<comments>http://jack-fx.com/net/2011/04/20/pipeline-in-powershell/#comments</comments>
		<pubDate>Wed, 20 Apr 2011 16:18:28 +0000</pubDate>
		<dc:creator>Jack</dc:creator>
				<category><![CDATA[Others]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[ETS]]></category>
		<category><![CDATA[heuristic method]]></category>
		<category><![CDATA[mode command]]></category>
		<category><![CDATA[Pipeline]]></category>
		<category><![CDATA[readable text]]></category>
		<category><![CDATA[text]]></category>
		<category><![CDATA[xml format]]></category>

		<guid isPermaLink="false">http://jack-fx.com/net/2011/02/21/pipeline-in-powershell/</guid>
		<description><![CDATA[PowerShell uses a pipeline for all command entries, which feeds the results of the preceding command directly into the subsequent command. The pipeline is active even when you enter only a single command because PowerShell always automatically adds the Out-Default cmdlet at the pipeline&#8217;s end so that it always results in a two-member instruction chain. [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/net/2011/04/20/pipeline-in-powershell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interactive PowerShell</title>
		<link>http://jack-fx.com/net/2011/02/14/interactive-powershell/</link>
		<comments>http://jack-fx.com/net/2011/02/14/interactive-powershell/#comments</comments>
		<pubDate>Mon, 14 Feb 2011 07:33:00 +0000</pubDate>
		<dc:creator>Jack</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[absolute path name]]></category>
		<category><![CDATA[environment variables]]></category>
		<category><![CDATA[path environment]]></category>
		<category><![CDATA[powershell scripts]]></category>
		<category><![CDATA[priority function]]></category>

		<guid isPermaLink="false">http://jack-fx.com/net/2011/02/14/interactive-powershell/</guid>
		<description><![CDATA[The PowerShell console runs all kinds of commands interactively: you enter a command, and the console will more or less immediately return the results. If you enter a command and execute it by pressing (Enter), PowerShell looks for the command in this order: Alias: It will first look to see if your command corresponds to [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/net/2011/02/14/interactive-powershell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Versioning and optional parameters</title>
		<link>http://jack-fx.com/net/2011/01/26/versioning-and-optional-parameters/</link>
		<comments>http://jack-fx.com/net/2011/01/26/versioning-and-optional-parameters/#comments</comments>
		<pubDate>Wed, 26 Jan 2011 03:40:31 +0000</pubDate>
		<dc:creator>Jack</dc:creator>
				<category><![CDATA[.Net]]></category>
		<category><![CDATA[C#]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Application]]></category>
		<category><![CDATA[application application]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[execution time]]></category>
		<category><![CDATA[library public]]></category>
		<category><![CDATA[MyDemo]]></category>
		<category><![CDATA[optional parameters]]></category>
		<category><![CDATA[public static void]]></category>
		<category><![CDATA[time]]></category>

		<guid isPermaLink="false">http://jack-fx.com/net/2011/01/26/versioning-and-optional-parameters/</guid>
		<description><![CDATA[The restrictions on default values for optional parameters may remind you of the restrictions on const fields or attribute values, and they behave very similarly. In both cases, when the compiler references the value, it copies it directly into the output. The generated IL acts exactly as if your original source code had contained the [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/net/2011/01/26/versioning-and-optional-parameters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Call SQLCMD to run SQL script via C#</title>
		<link>http://jack-fx.com/net/2011/01/05/call-sqlcmd-to-run-sql-script-via-c/</link>
		<comments>http://jack-fx.com/net/2011/01/05/call-sqlcmd-to-run-sql-script-via-c/#comments</comments>
		<pubDate>Wed, 05 Jan 2011 02:19:07 +0000</pubDate>
		<dc:creator>Jack</dc:creator>
				<category><![CDATA[.Net]]></category>
		<category><![CDATA[C#]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[argument]]></category>
		<category><![CDATA[argument string]]></category>
		<category><![CDATA[osql]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[sql scripts]]></category>
		<category><![CDATA[string argument]]></category>
		<category><![CDATA[string format]]></category>
		<category><![CDATA[Studio]]></category>

		<guid isPermaLink="false">http://jack-fx.com/net/2011/01/05/call-sqlcmd-to-run-sql-script-via-c/</guid>
		<description><![CDATA[Usually, we need to call some sql script to update our database in our application(C#), and it is a good way to call SQLCMD to execute the sql scripts. One important reason is that our scripts always contains the GO statement which is is not a Transact-SQL statement; it is a command recognized by the [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/net/2011/01/05/call-sqlcmd-to-run-sql-script-via-c/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Incorrect Syntax near &#8216;GO&#8217; while using SqlCommand.ExecuteNonQuery()</title>
		<link>http://jack-fx.com/net/2010/11/29/incorrect-syntax-near-go-while-using-sqlcommand-executenonquery/</link>
		<comments>http://jack-fx.com/net/2010/11/29/incorrect-syntax-near-go-while-using-sqlcommand-executenonquery/#comments</comments>
		<pubDate>Mon, 29 Nov 2010 02:57:05 +0000</pubDate>
		<dc:creator>Jack</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[execution plan]]></category>
		<category><![CDATA[incorrect syntax]]></category>
		<category><![CDATA[server utilities]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[sql command]]></category>
		<category><![CDATA[SqlCommand]]></category>
		<category><![CDATA[statement]]></category>
		<category><![CDATA[tableA]]></category>

		<guid isPermaLink="false">http://jack-fx.com/net/?p=150</guid>
		<description><![CDATA[GO is not a Transact-SQL statement; it is often used in T-SQL code. Go causes all statements from the beginning of the script or the last GO statement (whichever is closer) to be compiled into one execution plan and sent to the server independent of any other batches. SQL Server utilities interpret GO as a [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/net/2010/11/29/incorrect-syntax-near-go-while-using-sqlcommand-executenonquery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

