90 reputation
16
bio website
location
age
visits member for 2 years, 7 months
seen May 10 '12 at 6:26

May
10
comment Master page design (reloads on new page)
Yes, makes sense. Thanks for the answers :)
May
9
comment Master page design (reloads on new page)
Thanks for the answer :) I dont know if you can answer this question, but how do people "normally" design navigation? I mean, "master pages" arent outdated right? So if other people are using the same principle as me, they just arent concerned with the "entire page refresh"? I dont actually mind that the whole page is reloading but I just want to know if im doing this nagivation thing in a proper way or if I could be doing something better
May
9
comment Master page design (reloads on new page)
Hmm, maybe I just dont know enough about how to design a website that is easy to navigate. Can you maybe explain or give a link where I can get an idea of how to design a website using ajax in a proper way.
May
9
comment Master page design (reloads on new page)
Okay, i thought so :) But what about the solution to use some sort of control/iframe that shows the contentpages so that the master page does not have to reload all the time? Do people that sort of thing or is that just really bad practice vs. flickering
May
9
comment Master page design (reloads on new page)
I have been working with updatepanel before but im not sure how to implement it in this situation. I mean, if I have a link to Page2.aspx and click it, the entire page as well as the master page would still need to be reloaded. If I however were just navigating Page1.aspx only, I would ofcourse use the updatepanel to avoid the entire page to reload. But again, how do other people use the master page, do they just live with the "flickering" between page reloads and thats it, or is there some other smart way :)
Jan
13
comment UserControl inside Placeholder good/bad? + Postback problem
Hi. Well im more or less just trying to find the best way to navigate through pages without having to do full postbacks all the time. This i tried to solve by having the updatepanel with a placeholder which contains usercontrols. This makes no sense perhaps?
Dec
22
comment Entity Framework and “ViewModel”
Hm, im not sure I understand. Lets say you show a list of "PersonAddress" and you want to update row no. 2. How do you know which Person to update in the db if you only have information like name and age in the ViewModel? I might need an example of some sort hehe
Dec
22
comment Entity Framework and layer separation
@Boris might be an obvious question but lets say you want to update a Person from the Web app. Web app would then call a method on the Core? But how do we go from the Core to BLL to DAL to persist to DB since Core is not dependant on any other solution
Dec
22
comment Entity Framework and “ViewModel”
Okay, thanks for the answers. About the 3rd one. What would my "PersonAddress" object look like? Im asking because i havent created one yet. I assume it would contain the properties I want to show along with the PersonId and AddressId for select/update/delete things. Then after ive selected and updated Person and Address with the new information, I can use the "EntityState" for whatever I like. Is this the right way to do it?
Dec
21
comment Entity Framework and layer separation
But what if I dont have to combine two object but I just want to show a list of all Persons. Would I then create a "ViewModel" which (more or less, without the EF specific stuff) is exactly the same? I guess so? but wouldnt I, in time, have made all the generated objects from EF as my own view models? Sorry for all the question, im just trying to learn here :)
Dec
21
comment Entity Framework and layer separation
Yes. What I do now is to have for example an IPersonRepository interface and then have PersonRepository and PersonTestRepository which implements the interface. The "Test" Repository then returns "dummy data" so I dont interact with the database. So here I would make my unit tests in my BLL using the view models?
Dec
21
comment Entity Framework and layer separation
Can you please explain the difference and how unit testing becomes more easy? My guess on what a "ViewModel" is would be something like: If I have 2 object of which I want to show a subset of data, I combine these two objects into a new object which would be my viewmodel to show on the UI?
Dec
21
comment Entity Framework and layer separation
Ah, good point about the recompile/redistribute :)
Dec
21
comment Entity Framework and layer separation
Normally, without EF i create my own Person class in a "Model" layer, so I have UI, BLL, DAL and Model where: UI knows BLL and Model. BLL knows DAL and Model. DLL knows Model. Do you create your own "view models" aswell and why dont you just use the ones EF generates? (i know this goes against the layered architecture, but how many times do you actually switch out the way you get data?)
Dec
21
comment Entity Framework and layer separation
So if im not foressing any changes from EF to another approach, my code above would be okay? I would then only have UI and BLL (where the EDMX is in the BLL)?