RE: web parts and a database
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Wed, 27 Sep 2006 14:39:08 GMT
Hello igotyourdotnet,
Thanks for your reply.
Yes, if you're using the webpart through the default SQL
provider(AspNetSqlPersonalizationProvider class), you do have to provide a
sqlserver instance or SQLEXPRESS engine.
However, as I said, the ASP.NET 2.0's application servies are all designed
as provider based, it's flexible to create custom provider and use custom
provider to replace the default ones. I've found some web articles that
mentioned creating custom provider (file based for example) to avoid using
database:
#Webparts without SqlExpress or SqlServer
Categories
http://www.kowitz.net/2006/5/2/Webparts+without+SqlExpress+or+SqlServer.aspx
You can get more information about the provider model in ASP.NET 2.0 and
developing custom provider in the MSDN dev center:
#Provider Toolkit
http://msdn.microsoft.com/asp.net/downloads/providers/default.aspx
Hope this helps.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- RE: web parts and a database
- From: Steven Cheng[MSFT]
- RE: web parts and a database
- From: igotyourdotnet
- RE: web parts and a database
- Prev by Date: Microsoft Great Plains - Barcode
- Next by Date: A thumbnail conversion script
- Previous by thread: RE: web parts and a database
- Next by thread: RE: web parts and a database
- Index(es):
Relevant Pages
|