Question
ASP.NET 2.0 with database on Shared hosting problems?
Problem:
I have created a very simple site to display a datagrid from an Access database using ASP.NET 2.0 on shared hosting server. It will not allow the "dataset" code for pages created with Dreamweaver 8 for SQL or Access 2003 databases to be run due to the standard "medium" security settings recommended by Microsoft. The security "Trust" level would have to be high or full to allow this code to run. I have also tried to use a SQL database for the same purpose and get the same errors. Does anyone know if Dreamweaver is working on a fix for this so that the code can run on Medium trust servers (which most shared hosting is running now)? Most hosting providers are not recommending allowing "Full" trust so there is only a couple solutions I have found:
Solutions:
1. Move the hosting of the pages to a ASP.NET 1.1 Shared Hosting servers as they do not have the trust component.
2. Move the hosting of the pages to a hosting provider that allows "Full" trust (many won't do this because of the security risks).
3. ??? Ideas? What does everyone esle do?
I am hoping that there is a fix that I can do... or that Dreamweaver is working on a fix so their code can run in ASP.NET 2.0 under Medium trust.
Let me know...
I have created a very simple site to display a datagrid from an Access database using ASP.NET 2.0 on shared hosting server. It will not allow the "dataset" code for pages created with Dreamweaver 8 for SQL or Access 2003 databases to be run due to the standard "medium" security settings recommended by Microsoft. The security "Trust" level would have to be high or full to allow this code to run. I have also tried to use a SQL database for the same purpose and get the same errors. Does anyone know if Dreamweaver is working on a fix for this so that the code can run on Medium trust servers (which most shared hosting is running now)? Most hosting providers are not recommending allowing "Full" trust so there is only a couple solutions I have found:
Solutions:
1. Move the hosting of the pages to a ASP.NET 1.1 Shared Hosting servers as they do not have the trust component.
2. Move the hosting of the pages to a hosting provider that allows "Full" trust (many won't do this because of the security risks).
3. ??? Ideas? What does everyone esle do?
I am hoping that there is a fix that I can do... or that Dreamweaver is working on a fix so their code can run in ASP.NET 2.0 under Medium trust.
Let me know...
