Hot answers tagged

10

My observation is that WebForms is on the decline. There is a good reason for that. Having used WebForms extensively in the past, it's difficult to do something outside the box. In addition to the learning aspx controls and their proper usage, there is a lot of technical minutiae to learn about the page life cycle when going beyond basics. And in the end, ...


1

Usually, your only real option is a gradual update to new tech as you implement new stories from your backlog. That way, you continue to provide business value over time. A rewrite is a hard sell. You provide little business value during it. And then at the end the product does roughly the same thing (near-zero business value). And for a while afterward, ...


1

How much work is it to derive the data to display? If it's a fairly simple query, than re-doing it every time may be little more work than doing it once, saving the results somewhere else in the DB, and then drawing from there. Do all users see the same data? I mean, are there any parameters on this screen, or is the display the same for everyone? If there ...


1

...can you please tell me if I'm doing it right or wrong? Unfortunately, most here would probably disagree that this the right way to structure things. There is a number of issues that I can see: You have no layering to the application, your controller populates the view with result that it, itself, pulls out of the database. Split the logic into layers,...


1

first of all you can move your db context to a separate class and preferably project as well. this class would be your data layer, it should have all the queries in it. You would call them as functions like this (which sould be better named to say what they are getting) model.A = getStrQueryData(EmpId) model.X = getRtsQueryData(EmpId) model.C = ...



Only top voted, non community-wiki answers of a minimum length are eligible