|
Written by Alex T. Silverstein
|
|
Here's a tip for understanding how to deal with multiple versions of assemblies loaded from the GAC. If you have two versions of the same assembly in the GAC, and the SpecificVersion property (on the assembly reference) is set to False (the default), then the ASP.NET runtime will choose the later one from the GAC to load into your application. We had this happen last week, when my colleague had a reference to System.Web.Extensions, with SpecificVersion false. Now, System.Web.Extensions comes in FX 3.5 but also the preview version 1.0.6014 (or something). He built the project against the 1.X version, but ASP.NET tried to load 3.5, which of course threw a runtime error since the implementation had changed. |
|
|
Written by Alex T. Silverstein
|
Example code from our XSLT presentation at Tech Valley Code Camp: |
|
|
Written by Alex T. Silverstein
|
|
The more code I write, the more I learn that even the slightest inconsistency in my code -- usually in terms of a naming convention or naming similarly-purposed variables or methods -- will come back to haunt me, especially as the system grows in complexity. I really try to put this axiom into practice whenever I sit down to code, because, although boring at times, it really is hugely important. Consistant naming leads to fewer classes, less repetition, more interfaces, and easier debugging. There really is no downside to this practice. |
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 Next > End >>
|
|
Page 4 of 7 |
