Re: Problem with updating MDF Data file as opposed to updating a running SQL Server DB
- From: multiformity@xxxxxxxxx
- Date: 11 May 2006 06:36:37 -0700
I don't know if you guys know what I am doing.
In Visual C# Express, I created a windows application, then "Added" a
"Database File". Doing this created an MDF file in my project folder,
and added in a connection string into my "App.config" file for me. This
connection string specifically pointed to data file, and added the
database into my database explorer window in the IDE. From there I
could create a new Data Access Layer (xsd) with a simple drag and drop
and viola, I had a typed dataset for the table in the DB. I have
watched some Atlas tutorials that microsoft provides where they have
done exactly this, but through VWD Express, and not VC# Express.
It would seem with this option, then one could use a SQL Server MDF
file and NOT have to have SQL Server running on the target machine. It
would seem that MS is trying to give people the option to use SQL
Server MDF files instead of MS Access MDB files from the get go on
their development project, with the option to host the MDF files in an
actual instance of SQL Server later down the line.
I am actually going to just use the "SaveXML" and "ReadXML" methods off
of the typed dataset that the IDE created for me, but it is still kinda
ghetto that Microsoft gives you the option to use an MDF file, but it
doesn't work fully....
AB
.
- Follow-Ups:
- References:
- Prev by Date: GenerateDirectDBMethods issue with VS2005 DataSet wizard
- Next by Date: Re: Problem with updating MDF Data file as opposed to updating a running SQL Server DB
- Previous by thread: Re: Problem with updating MDF Data file as opposed to updating a running SQL Server DB
- Next by thread: Re: Problem with updating MDF Data file as opposed to updating a running SQL Server DB
- Index(es):
Relevant Pages
|
