Tip: System.Data.Entity and ClickOnce Deployment Issue

gugonzar — Wed, 20 Aug 2008 19:59:29 GMT

I was developing a Windows forms application in .net framework 3.5, and I needed to include ClickOnce Deployment in my solution project. Recently I downloaded and installed the last Service Pack (SP1) for Microsoft Visual Studio 2008 and .net framework 3.5, so far, everything was normal. The only application setup prerequisite was .net framework 3.5.

I published my application in a web server normally, and when I click the Install button to start the install process, I received the next error message from the ClickOnce Installer:

The funny thing is that I didn't have any reference to System.Data.Entity in my solution, so? what's wrong? Why was ClickOnce requesting this assembly?

Well, after a quick search in Google, I found and read this Post from Mat Steeples, and I understood why ClickOnce was referencing System.Data.Entity assembly, simple!, I included a new feature (Create a Desktop Icon) and that functionality requires the mentioned assembly.

Thanks to Mat Steeples for sharing it.

Tip: DataSet.HasChanges and Windows Form Close Button Strange Behavior

gugonzar — Tue, 22 Jan 2008 14:12:00 GMT

I had to write a simple Windows Forms application that haves a form. This form contains a DataGridView control that is binded with a DataSet; this DataSet is filled with data from an XML file. This Windows Forms contains two buttons: "Accept Changes" and "Cancel Changes".

The "Accept Changes" and "Cancel Changes" buttons works greatly, the first one writes the content of the DataGridView control in a XML DataSet, and the second one simply cancel the data insertion, delete or modifying operation and shows a message indicating to the user if wants to discard or save all changes made to the DataGridView control. Both the "Cancel Changes" and the standard window close button executes the following method:

1: private void CloseWindow()

2: {

3:  dvProviders = dgvProviders.DataSource as DataView;

4:  DataSet dsProviders = dvProviders.Table.DataSet;

5:

6:  if (dsProviders.HasChanges())

7:  {

8:   DialogResult saveChanges = MessageBox.Show("¿Save Changes?",

9:   "Save", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation);

10:

11:   if saveChanges == DialogResult.Yes)

12:   {

13:    //Save the changes from the DataSet to an XML file

14:    this.SaveChanges();

15:   }

16:  }

17: }

But what happens if the user close the window using the standard window's close button and the DataGridView's DataSource (a DataSet) have pending changes?
It is expected that the button execute the CloseWindow method and detect if the DataSet has changes, but in a rare way when the code ask for the result of the DataSet's HasChanges method, it returns a false value and all the changes made in the DataGridView control are lost when the window close.

Well, Fortunately with the help of a coworker that told me that it was a "Bug" or better called "Windows Form's rare behavior". He told me that I need to move the focus of the DataGridView control to other control in the form (for example the Accept Changes button) before asking for the DataSet's HasChanges method, this way the DataGridView control apply the changes to the DataSet and the HasChanges return true (if any change is made to the DataGridView control) and the method's execution continues normally.

  5:     // Set the focus to other control

  6:      btnAcceptChanges.Focus();

7:

  8:      if (dsProviders.HasChanges())

  9:      {

 10:      ...

Thanks to Alberto Puyana for help me find the answer to this windows close button strange behavior.

Guillermo G. Blog : Windows Forms

Tip: System.Data.Entity and ClickOnce Deployment Issue

Tip: DataSet.HasChanges and Windows Form Close Button Strange Behavior