Avian Waves : Blog
Topic: All
Search Blog
 
Recent Comments
Bulk Local Administrator Password Management Tool (15)
rcmichelle: Last time I forgot my password and tried...

Easy Way to Change Permissions on the Windows Server Scheduled Tasks Folder (C:\Windows\Tasks) (22)
4Fingus: Thank you so much. You have saved me alot of...

Mystery of the Missing msnmsn.inf on XP SP3 (24)
jo w: Thanx m8, it's even brilliant for those who are...

Delegating "Power Options" Management to Limited Users in XP (6)
Alessandro Stillitano: Hi :)I can report that on a Lenovo T410i the...
Last 15 Posts
Archives
Posted By Timothy • Topic: Tech
Oct 25, 2009 11:08 PM EDT

A colleague of mine found a great article with a tip to significantly speed up the compilation time of large .Net Compact Framework projects.  I was just living it with, thinking there was nothing I could do.  I'm so glad he found that article!  It is helping speed up development of my mobile hobby projects significantly.  The slowness is due to a verification step that ensures that your application complies with its target.  Obviously during debugging, this step does not need to be executed every single time you build!  The article suggests creating a new environment variables, but I think a better approach is to use the $(ConfigurationName) variable.  When I compile for release, I want this check.  For debug, I don't.  So go read the article!  Then, if you like, take my suggestion and change the condition to...

Condition="'$(ConfigurationName)' != 'Debug'"

Trackbacks :
Send trackbacks to this URL:
http://www.avianwaves.com/Blog/track.aspx?id=168
In your blog post, you must link back to my post using this URL:
http://www.avianwaves.com/Blog/default.aspx?id=168
Add Comment :
Name :
Email :
URL (Optional) :
       
Comments :
Allowed BBCode Tags : LINK (URL), BOLD, ITALIC, UNDERLINE, QUOTE


By posting a comment to this blog, I agree to the blog rules.

This Avian Waves blog is powered by a modified version of Presstopia Blog




Avian Waves Logo