This project is read-only.

RazorGenerator and deployment to Azure

Dec 5, 2013 at 4:41 PM
I have my views set to BuildAction=None and CustomTool=RazorGenerator. Everything works great on my dev box but when I Publish to an Azure website none of my view changes are deployed. It's like it can't "see" the compiled cs view file that RazorGenerator creates and since the cshtml files are missing it can't show the view.

If I change BuildAction to "Content" then everything works as expected and my changes are successfully published to Azure.

My question is, why is this happening? Isn't asp.net supposed to use the compiled view cs file and not the cshtml file? I would like to be able to leave the BuildAction set to None and deploy to Azure without deploying the cshtml files. Is this possible?
Dec 5, 2013 at 5:34 PM
Do you think you could perhaps share a repro app for this and specify what you're using to deploy to Azure (using the Publishing option \ continous deployment etc)? Your scenario should work fine in theory - my guess is that some config is setup incorrectly.