Just over a year ago I blogged about the problems I was having installing Umbraco via Visual Studio. At the time, I couldn’t get Visual Studio 2013 to install correctly, and Visual Studio 2012 only worked correctly when Resharper was turned off. I created quite a few sites in this manner. The original problem was that something was screwing up and preventing Visual Studio from understanding it was a MVC project so the scaffolding options on the menus were missing.
Since then, I have used VS2013 and also 2015 to some extent. I am pleased to report that the latest version of Umbraco installs correctly and is somewhat simpler (I still disable ReSharper and avoid IE though for the install itself).
In summary, the steps are:
- Start Visual Studio
- Ensure ReSharper Disabled
- Create a new empty web application with the MVC references
- Install Umbraco via the nuget package using “Manage Nuget Packages for Solution”
- Ensure IE is not the default browser
- Create an empty SQL database on your dev machine
- Run the Visual Studio project
- Choose Custom Install and specify the correct database settings. I normally use a SQL server user for each database on my dev machine, so this will need setting up beforehand.
- Don’t forget your admin username and password because its more difficult to reset with later versions of Umbraco (I’ll blog about this the next time I have to do it because it can be done).
When I was doing the latest install on Visual Studio 2015, I found this post interesting (although I don’t use Visual Studio Online): http://maffrigby.com/how-to-deploy-umbraco-7-to-an-azure-website-using-visual-studio-online/
The basic procedure is:
- Set up your usual publish settings
- Ensure media folder is included in the project along with other files (not App_Data/cache)
- Ensure App_Data/umbraco.config is not included in the publish as this is a cache file for the content.
- Execute the Publish
When publishing to Windows Azure, if any transform errors appear with web.config, or web.config files not found, then change the web.config Build Action to “None”. This is likely to apply not to the main web.config, but some of the others in the solution such as the one in Umbraco/xslt.