Skip to main content
Participant
October 23, 2006
Question

ASP.NET 2.0 with database on Shared hosting problems?

  • October 23, 2006
  • 1 reply
  • 256 views
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...
This topic has been closed for replies.

1 reply

Inspiring
October 23, 2006
I'd suggest that you use the new DataSource controls that are built into
ASP.NET v2. You can then easily bind these to grid views.

--
Jules
http://www.charon.co.uk/charoncart
Charon Cart 3
Shopping Cart Extension for Dreamweaver MX/MX 2004





Participant
October 25, 2006
Are these new DataSource controls for ASP.NET 2.0 available in Dreamweaver 8? How would these be used instead of the other connections when setting up the database connection?

Also, as a followup... I moved the site I was referring to in the original post to a 1.1 server... and everything works great! Amazing the hours of frustration and all it took was the change to a 1.1 server. I am pretty new to database development using Dreamweaver but I am sure others are having this problem too.