Skip to main content

Setting up S#arp Architecture 1.6 for VS 2008

The latest S#arp architecure is 1.9 something, rapidly heading towards 2.0, and all targeted at VS2010.

But if you're using VS 2008, you'll have to use S#arp Architecture v1.6, which was the last version targeting VS 2008. But its best to use Templify to setup your solution, which is something they built especially for S#arp 2.0 but now has a retrofitted template for 1.6.

(NB: setup instructions for the latest S#arp seem to be in their wiki, here)

So, here's the steps to get S#arp 1.6 working from a vanilla Visual Studio 2008 install:

  • Install MVC 2

  • Install .NET Framework 4 (not needed for S#arp 1.6, but is needed for Templify)

  • Install T4Toolbox

  • Install Templify

  • Download from the S#arp github site

  • Unzip the package and run copy-package.cmd to copy the Templify template to the right place

  • Make a folder somewhere

  • Right click on the folder and select 'Templify Here'

  • Select the "SharpArchitecure VS 2008 MVC 2" template

  • Enter your project name

  • Press Deploy Template
... and voila, you have a VS 2008 S#arp 1.6 solution.

To get the initial test running, you also need to create a blank database and edit (project).Web/NHibernate.config.xml to point to that db.

Most of the templify stuff, and generation of code using the CrudScaffolding is covered by the S#arp documentation for VS 2010


kdelmonte said…
Hey, I noticed that you have knowledge on how to solve a problem that I have... Please, visit

Popular posts from this blog

Copying data to Salesforce Sandboxes using TalenD

A common problem with Salesforce Developer Sandboxes is that they are blank. Really you're going to want some data in there, so there are various strategies for copying data from your live instance to the Sandbox. There are some paid-for solutions - SFXOrgData , Salesforce Partial Data Sandboxes - but if you've got a decent ETL tool you can build your own. There are a bunch of free ETL tools for Salesforce: JitterBit Data Loader is good for quick ad-hoc tasks but the free version makes it difficult to manage specific ETL projects or share projects with other users Pentaho Community Edition - an open source edition of the enterprise version Apatar was a free open source Salesforce ETL which still works but development seems to have stopped since 2011 TalenD Open Studio is an open source ETL tool For the task of copying data from live to a Sandbox, either Pentaho or TalenD Open Studio could be used, depending on preference. Here's a good comparison of the dif

SSRS multi-value parameters with less fail

SSRS supports multi-value parameters, which is nice, but there are a few issues with them. This is how I deal with them. Two of the problems with SSRS multi-value parameters are: You have to jump through a few hoops to get them to work with stored procedures The (Select All) option, as shown above The reason the (Select All) option is a problem is that it is a really inelegant way of saying 'this parameter does not matter to me'. If you have a list with hundreds of values, passing all of them as a default option just seems wrong. Also, if your report shows the user which items they selected, printing the whole list when they choose (Select All) is excessive. So in this post I'm going to show my particular way of: Jumping through the hoops to get Multi-Value params in a stored procedure Adding a single '--All--' value that the report interprets as meaning all the options. Getting Multi-Value params to work with Stored Procedures This is

Remote Desktop on High DPI screens

Scott Hanselman wrote a nice blog post back in January about some of the issues you might face running Windows on a High DPI screen like that of a Surface Pro or Lenova Yoga. I'm kindof mystified that he didn't mention Remote Desktop though because thats been the number one problem for me on High DPI screens. That said, if you remote into very recent Server OS's like Windows Server 2012 R2, then apparently Remote Desktop will sort out the DPI scaling automatically. Perhaps Scott hadn't noticed the Remote Desktop issue because he only remotes into Server 2012 R2. Certainly if I was Scott, I wouldn't remote into anything less than that. But, in practice, I regularly have to remote into Server 2008 machines and yes even Server 2003. If you do that from a high DPI screen, the remote desktop is rendered at regular pixel size, which makes everything tiny. Its hard to show screenshots of High DPI screens that correctly convey the pixel size, so I've photoshoppe