Want to reduce build, compile and deployment time in visual studio 2008 or vs2005 windows mobile development? one thing that frustrates .netcf developers is building/ compiling application takes hell lot of a time this is due to platform verification but fortunately there is a hack which can speedup build and compile time several times faster just follow below steps if you are also facing the same issue

--> first of all close your visual studio

--> go to this path C:\WINDOWS\Microsoft.NET\Framework\v3.5\

--> Find Microsoft.CompactFramework.Common.targets file and make sure to back up it

-->Now open Microsoft.CompactFramework.Common.targets file in text editor and look for below statements

Name="PlatformVerificationTask">
PlatformFamilyName="$(PlatformFamilyName)"
PlatformID="$(PlatformID)"
SourceAssembly="@(IntermediateAssembly)"
ReferencePath="@(ReferencePath)"
TreatWarningsAsErrors="$(TreatWarningsAsErrors)"
PlatformVersion="$(TargetFrameworkVersion)"/>

Now modify the Name="PlatformVerificationtask" line by adding this code"Condition="'$(SkipPlatformVerification)' == 'true'"" as below

Name="PlatformVerificationTask" Condition="'$(SkipPlatformVerification)' == 'true'">
PlatformFamilyName="$(PlatformFamilyName)"
PlatformID="$(PlatformID)"
SourceAssembly="@(IntermediateAssembly)"
ReferencePath="@(ReferencePath)"
TreatWarningsAsErrors="$(TreatWarningsAsErrors)"
PlatformVersion="$(TargetFrameworkVersion)"/>

Now open your project and compile it i am damn sure it works 5x faster

latest open source .net project binaries

There is a lot of discussion on ETags. For those who don't know, read:

• http://en.wikipedia.org/wiki/HTTP_ETag
• http://developer.yahoo.com/performance/rules.html#etags

However, ETags can become a problem when you run a cluster/farm, so each request to unique server returns a different ETag. Some of this has been fixed in IIS 7. Also, it seems, if you are using the Expiry (a better practice), having ETags results in a worse YSlow rating.

Our YSlow Rating was 68. We added Expire Header info, and the score went to 85. However, upon turning off ETags, we jumped further to 88.

Unfortunately, there didnt seem to be any good way to disable ETags on IIS 6. Most posts and articles referenced working the IIS Metabase, and still there was a MS Hotfix for those where the MetaBase edit would not stick. Ugh.

I wasn't sure I wanted to do all that just for 3 point in YSlow, until I came across this site. See: http://blogs.iis.net/chrisad/archive/2006/12/18/iis7-deployments-calls-for-etag-usage-review-if-using.aspx. The site itself covers IIS 7, and was useless to me, until I saw the last comment.

"Remove ETags from the Http Response by setting a blank ETag header. In IIS Manager, right click Web Site (or any folder), click Properties, select HttpHeaders tab, add Custom Http Header called ETag but leave the value blank."

Although this would still return an ETag in the HTTP Header, I tried this an voila, it worked. So simple, it was stupid! And now we're getting an "A" in the ETags area in YSlow, and a better overall score.

Enjoy!

useful