Hi there,

I'm not sure if this is how things should be done, but it works for me and since theres no better answer yet, this is better than nothing! ;)

The way I have things set up is as follows (quite a lengthy guide, but its easy once you get the hang of it):

• Create a new blank solution for my entire website:
  C:\Source\MyNewWebsite\
• Right click the solution and 'Add New Web Site' - choose 'ASP.NET Empty Web Site'.
  I usually rename the path to something like this (C:\Source\MyNewWebsite\Website)
• The next thing you need to do is right click the Web Project - select Property Pages.
• In the 'Start Action' dropdown, select 'Build Page' - this ensures that the whole web project will not be built, which is what is causing you trouble.
• Also while in here - remove the checkmark from 'Build Web site as part of solution', to ensure it won't try to build if you select build solution.
• One last thing to configure is the path (and port) of the dev webserver. Click the Website project and go to the properties pane in VS.
  Virtual Path should be set to: /
  If you want to use a specific port to host the website, deselect 'Use dynamic ports' and set the port number manually.
  (This might come in handy if you code some webservices hosted in Umbraco, so you are sure which port the site can be reached at, at any time)
• What you would do next is download the newest stable Umbraco release from codeplex and unzip the contents into your \Website\ folder
  Path to masterpages folder should be 'C:\Source\MyNewWebsite\Website\masterpages', if you did it correct ;)
• Now this is just info for others since you said you didn't really need this! - if you need to have some custom handlers, you would create a new class library project next to the website project, add the handlers here, create a build action for that project that copies the .dll file into the \bin\ folder of your website and you're good to go.

What I do next, is right click the web project and select 'View in browser'. I prefer to only use debugging when I really need to, as it slows down a bit.

From here you just install Umbraco as you would usually do (remember to create a database on your SQL server) and go nuts :)

A few tips:

• Masterpages needs to be created from inside Umbraco, to have them show up in the CMS. However, masterpages created from Umbraco does not have the 2-file-split (.aspx / .aspx.cs) which I find rather annoying. To work around this, I usually go in VS, create a new masterpage and leave it open. Then I go to Umbraco and create a new masterpage with the same name and save it. Umbraco will then overwrite your masterpage. When done, go back in VS and you will be noticed that the file has been changed outside your environment and it asks you to reload. Instead of reloading, press 'No' and save YOUR masterpage again, overwriting what Umbraco just wrote and you will have the two file split, AND the masterpage registred in the CMS! :)
• Custom classes you create should reside in \App_Code\ - it will suggest you to move it there if you try to place it elsewhere.
• UserControls should be put in \usercontrols\ and can then be added to Umbraco by adding a new Macro from the developer section. Public properties exposed on a usercontrol can be added as parameters to be set on the Macro when adding it in the CMS.

Hope this will help you - and maybe some others on the way.

If anyone who knows more about this wants to correct me on anything - please do so. It's always nice to learn new stuff and I'm in no way sure I am doing this the right way ;)

-Claus

(edited - formatting was broken)