Databases
StackOverflow2013
Postsdbo
POWPF + SQL Server Compact Debug and Deploy
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWPF + SQL Server Compact Debug and Deploy
    primarykey
    data
    text
    <p>I have a WPF project set up to use a local SQL Server Compact database through an ADO.NET Entity Data Model in Visual Studio Express 2012 for Desktop. The project works great, on first run I can load all of the data, manipulate it as I please and come back later with the changed data still in place. </p> <p>I noticed while doing a little restructuring to the schema that the data visible to VS was only the very first bits of data that I entered manually when creating the database and the next time I compiled all of the data I had added since was gone!</p> <p>After some digging, I came to the conclusion that the compiled version of the app was using the SDF file sent to the bin/Debug folder by the file's Content:Copy If Newer build action. This means that there could be as many as 4 different copies of the database to be worried about: project folder, debug folder, release folder, and the deployed copy on the end user's PC.</p> <p>I would like to have a single copy of the database on my dev machine that is accessed by both debug and release compiled versions and the database explorer in VS that is installed on the end user's PC by ClickOnce. I suppose I could change the connection string to an absolute path during development and hope I can remember to change it back to relative before I publish for deployment.</p> <p>Finally, I foresee the need to release updates for this application as well and am worried that such an update would erase the end user's data if improperly done. If possible, I would like to be able to only update the schema of the end user's database without touching the data itself whenever I release an update. If this is not possible that is acceptable and I'll just have to make sure I put every structure I can think of into the database before my first deploy.</p> <p>In summary my questions are the following:</p> <ol> <li><p>How to share a single sql compact database between VS, debug, and release?</p></li> <li><p>How to handle local database during application deployment and updates, with the optional ability to update the database schema without erasing the data?</p></li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USCuddleBunny
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWPF + SQL Server Compact Debug and Deploy
      1. USBehzad Ashrafian
      1. VTFavorite
    1. COYou can also create the database programatically to be in total control.
      singulars
      1. POWPF + SQL Server Compact Debug and Deploy
      1. USErikEJ
    2. COThat could work. Is there an example of this somewhere? I would like to maintain the use of EF for classes and DataSources for binding if possible.
      singulars
      1. POWPF + SQL Server Compact Debug and Deploy
      1. USCuddleBunny
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload