Reputation
642
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
3 17
Newest
 Yearling
Impact
~36k people reached

  • 0 posts edited
  • 1 helpful flag
  • 29 votes cast
Jun
4
comment What are my options for exposing customization settings to the admin user?
I have written a few corporate apps in ASP.NET 3/4/5 and they all required some kind of configuration. Having an admin page updating database stored settings, which are then used across the site where required is the best option. You have backups of the database etc and can access your config options as entities in the application.
Jun
4
awarded  Yearling
Apr
6
awarded  Popular Question
Apr
1
comment TFS Branching an incomplete version
I will read up on feature flags, thanks for the tip.
Mar
31
asked TFS Branching an incomplete version
Mar
25
awarded  Nice Answer
Feb
20
awarded  Popular Question
Jan
20
awarded  Popular Question
Nov
4
awarded  Popular Question
Sep
24
awarded  Autobiographer
Aug
20
accepted Generic Repositories with DI & Data Intensive Controllers
Aug
20
comment Generic Repositories with DI & Data Intensive Controllers
This is a very good point, there could be a service layer in between my COntrollers and Repositories to try reduce this problem.
Aug
20
comment Generic Repositories with DI & Data Intensive Controllers
I really like this approach. I will play with it when I have time and see if i like it when its implemented. Could be a good alternative to repositories.
Aug
19
answered Data Access Objects old fashioned?
Aug
19
asked Generic Repositories with DI & Data Intensive Controllers
Aug
18
accepted Is table inheritance the wrong approach
Aug
15
comment Is table inheritance the wrong approach
Exactly the issues I want to avoid. Although I was considering that having the additional class with the 0.1:1 relationship could have its own issues.
Aug
15
asked Is table inheritance the wrong approach
Jul
31
comment How far can I drift from my original domain model and still have the benefits of an ORM?
The FK can be left out and just have a navigation property or leave both out. The FK still gets created on db but you won't be able to assign users by id using entities. You will need to select out a user to assign it. Also you should use 'virtual icollection' as it's a navigation property. All depends on relationship you are trying to make.
Jul
2
awarded  Curious