Welcome!
I am a .Net developer by day; a PHP developer, Linux systems administrator and small business owner by night and a husband and father 24/7/365!
This is my blog about technology and my life in general!
On December 23, 2008 in ASP.Net, ASP.Net MVC, C#, S#arp Architecture, VB.Net, Visual Studio
During the conversion of the S#arp Architecture template project from C# to VB.Net I inadvertently broke (at least) one thing: the ability to add ASP.Net MVC items directly to the SharpArch.Web project directly from the “Add New Items…” dialog. This led to my first question asked on StackOverflow.com (which I ended up answering myself, 38 minutes later).
Turns out Visual Studio project files can have an element called <ProjectTypeGuids> which contains one or more guids identifying what type of project the file describes. ASP.Net MVC projects have a particular guid specified: {603c0e0b-db56-11dc-be95-000d561079b0}.
So I added this guid to both my SharpArch.Web project file and my SharpArch.Controllers project file, and now I can add new MVC template items directly from the “Add New Item…” dialog. Cool!
On October 25, 2008 in AnkhSVN, Subversion, VS2005, VS2008
What is AnkhSVN? It’s a Subversion source control provider for Visual Studio. It allows you to use Subversion for version control in Visual Studio rather than something like Visual SourceSafe. It’s also open-source and free.
I can just hear some people saying “I’ve tried AnkhSVN. It sucks. VisualSVN is the closest you can get to working Subversion / Visual Studio integration”. I can even hear a few people saying “They both suck. Who needs IDE integration anyway. TortoiseSVN from Windows Explorer is just fine”.
I have shared both of these views at various points in the last few years. But today I discovered and tried AnkhSVN 2.0! Huge difference! The new version is a nearly complete rewrite. It’s no longer an add-in, it’s own a proper SCC provider.
Do yourself a favour and give it a try before you drop any money on VisualSVN.
On October 23, 2008 in .Net, VS2005, VS2008
Last night I was reading through some FxCop documentation, specifically through the FxCop Design Warnings (yeah, that’s what I do in my spare time) and I came across the “Do not expose generic lists” warning which states:
System.Collections.ObjectModel? That namespace was new to me, so today I did a little digging.
On October 16, 2008 in Quick Links, VS2005, VS2008, Visual Studio
Here is a neat tip (#210) from Sara Ford.