Hi,

It sounds like you are unnecessarily running it in the VS debugger, if you mean you are using F5 or the play button in VS after every change. Only use the debugger if you need to step through the code, once you have first built the entire solution just right click the Web/Default.aspx page and choose view in browser, it will load the VS web server but without launching the debugger which is a much slower process. Then when you make a change in your custom feature just build your feature (not the whole solution), then refresh the web page. If something isn't working right then you can set break point sin the code and use the debugger to step through the code, but other than that I would stay out of the debugger.

Of course VS is a resource hog and a faster machine makes all the difference in the world.

Hope that helps,

Joe

It is not possible to run your feature independent of mojoPortal.

There is a setting you can make on the <compilation element in Web.config that may help speed things up a little. I have it in comments in the Web.config file, in my testing it does work but it occasionally can cause problems or unexpected results, others have also reported good success in making development faster but because there are issues sometimes I don't use it myself since I have a fast machine. But you may find it helpful.

Best,

Joe