Back to Top
What is the difference? In my session I have commit because it commits all changes done by all the repositories that use that session: public partial class Context : ISession public void Save() { SaveChanges(); } And I also have Rollback do discard the changes. I used Commit and Rollback because the code I found online of
3 days ago from the
Google Reader
of
mnuniez
Space gained from the column that had the asp:commandfield in it is gone. The ID column is already there which is now replaced with an asp:buttonfield. I did the replacing and so far the gridview is still functioning, with one less column. The gridview is not inside an updatepanel. Tried that some
3 days ago from the
Google Reader
of
mnuniez
There are no need for it. XDocument only contains some data structures in managed memory. And that can be GC'ed - so no need for any Close/Dispose call. Arne
3 days ago from the
Google Reader
of
mnuniez
Ah, right - understood. Hmm - well, you're going to need the update panel in order to use the modal popup - no way round that... Not why you're trying to get the row to highlight, but I'd imagine you'd need to set its background colour at the top of the SelectedIndexChanging method...
3 days ago from the
Google Reader
of
mnuniez
Hello, I am loading a few XDocuments to read, write, etc. After using the XDocument can't I dispose it? I think I should or not? I was looking for it and XDocument does not have a Dispose method. Thanks, Miguel
3 days ago from the
Google Reader
of
mnuniez
Update is fine. Remove or Delete are both fine. You Add something existing to something existing but you have something existing Create something new. FindAll and FindByXxx fine. If Save is really a Commit, then I think you should call it Commit. Arne
3 days ago from the
Google Reader
of
mnuniez
Why? If the methods have the semantics of Commit and Rollback, then use the names that gives the readers the correct associations. Arne
3 days ago from the
Google Reader
of
mnuniez
In fact when using Entity Framework I have: public partial class Context : ISession { public void Commit() { SaveChanges(); } // Commit public void Rollback() { Dispose(); } // Rollback But probably I should simple use Save instead of Commit and Dispose instead of Rollback ...
3 days ago from the
Google Reader
of
mnuniez
The thing that makes the IEnumerable different is something called "Deferred execution". This means it won't actually execute the linq query until you use it in a foreach statement. If you use it again in another for each statement then it will execute it again. This gives the advantage that you
3 days ago from the
Google Reader
of
mnuniez
Bringing more items...
You are very groso!!
You have viewed them all man. Come back tomorrow.