- Published April 3, 2009 at
1:17 AM
- by
Jeremy Jameson
-
Yesterday I introduced the concept of linked files in Visual Studio solutions with a follow-up on my recommendation for configuring a custom dictionary to eliminate CA1704 code analysis warnings.
Another practical application of linked files is what...
- Published April 2, 2009 at
10:59 PM
- by
Jeremy Jameson
-
Whenever a new .NET assembly project is created in Visual Studio, a file named AssemblyInfo is created that contains attributes used to define the version of the assembly during compilation.
Using assembly versions effectively enables various team...
- Published April 2, 2009 at
3:16 AM
- by
Jeremy Jameson
-
In my previous post , I introduced the concept of linking files in Visual Studio solutions.
A good use of this feature is specifying a custom dictionary for your solution.
Once you enable Code Analysis on your projects, you are likely to encounter...
- Published April 2, 2009 at
2:20 AM
- by
Jeremy Jameson
-
A couple of years ago, I wrote a post introducing my system for structuring Visual Studio solutions . However, I apparently forgot to post a follow-up providing additional details, such as configuring assembly versioning and what I like to call "shared...
- Published April 1, 2009 at
1:41 AM
- by
Jeremy Jameson
-
Here is a bug in Microsoft Office SharePoint Server (MOSS) 2007 that I've stumbled across at least twice in the last couple of years...I'm hoping that if I take the time to blog about it, I won't forget it again.
If you don't include Path in the SelectColumns...
- Published April 1, 2009 at
1:14 AM
- by
Jeremy Jameson
-
Yesterday afternoon, I discovered that there were 64,725 items (consuming 2.41 GB) in the C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root folder of my development VM for Microsoft Office SharePoint Server (MOSS) 2007. Apparently...