Hi all,

Besides the "SQL Server Compact is not intended for ASP.NET development"
exception (which can be worked around as suggested
here<http://gbuchoa2.blogspot.com/2009/10/sql-server-compact-is-not-intended-for.html>),
is there any reason not to use SQLCE in a small ASP.NET project?

I'm a total ASP.NET / IIS noob and I have to do a bit of customisation to a
pre-built .NET 2.0 asmx web service.  The service currently uses an MS
Access .mdb (which seems odd - I thought SQLCE was meant to replace Access
for these kinds of applications).

My customisations need to do some data access (not a lot though) and I'd
like to use LINQ to SQL for this if possible.  Obviously I'm not storing a
lot of data, and I'm only looking at Compact Edition since the hosting
provider isn't keen on full SQL Server / Express...

Is SQLCE a bad way to go?  Is LINQ to SQL not a good idea?  Should I try to
convince the hosting provider to give me SQL Express?

Thanks all.

Reply via email to