Experimenting with Amazon AWS micro - MVC project returns error [Solved - kind of]
-
So I'm experimenting trying to get a deployment of asp.net MVC running on an Amazon AWS micro instance. (The free for a year thing) Except I'm hitting a wall that I'm not sure what's wrong.
The Setup:
- Create a new ASP.NET MVC project - Select 'No Authentication' module
- Follow the server setup guide located here: http://martinbuberl.com/blog/deploy-aspnet-mvc-on-amazon-ec2-with-web-deploy/
- After following all the steps in the guide (installing web publishing, IIS 4.5) and publishing the application using web deploy, I access the URL here: http://ec2-54-68-194-158.us-west-2.compute.amazonaws.com/
- I get this error:
So what idiot newbie mistake did I forget when publishing?
Localhost seems to suggest that Debug is enabled for compilation, but I don't see that setting anywhere, and I'm publishing using release mode.
Appear to have found the answer:
< trust level="Full" />
But uh, I don't think I want to run this at trust level full, do I? What is requiring full trust? Am I just fundamentally misunderstanding what full trust means in this context?
-
Full trust was an old security thing in .net that is no longer relevant
-
The fact that it doesn't work without full trust suggests you're not making an accurate statement.
-
A recent asp.net vid about stuff you should use they said that medium trust doesn't improve app security. It only used by shitty discount hosting.
What is Medium Trust in Asp.net?
What is Medium Trust in Asp.net? When should we use Medium Trust in Asp.net?
I have to find the vid but Scott hanselman pretty much said it was a waste of time ... But here is the knowledge base page.
Basically says you should be using application pools for application isolation rather than partial trust.
-
That's more useful, thanks.
ASP.NET Partial Trust does not guarantee application isolation - Microsoft Support