I luckily work in a small office and am on my own most of the time, so I listen to mostly 70's, 80's rock, jazz, video game music. I do the odd .net rocks podcast from time to time.
darkliahos
Posts
-
Music , Podcasts or Silence? -
Tony Blackburn Sacked [UKain News]Sensational!
-
Do You Think ASP.NET has a Future?I have been in the Microsoft development game for a few years now. I personally think it does have a future, with Microsoft investing in the next version of ASP.net (VNext) and making strides in allowing for the deployment of ASP.Net applications to different types of containers via Katana and OWIN, the fact I can run an MVC application within a threaded process without the use off IIS is a big win and as a result of this I think we will see ASP.Net for a long time. But as Frank said it is important that you spend time in learning a multitude of technologies as it will serve you well in the future.
-
Opinions on dividing up a single entity framework layer in source controlThanks for clearing that up for me, in that case I shall have multiple DbContexts referring to the same table but only sections I need for different applications. Thanks again,
-
Opinions on dividing up a single entity framework layer in source controlThis is probably the first question I have asked on CP, so please be gentle :), also my terminology might be a bit all over the place. I admit I am pretty much a beginner as far as entity framework and architecture are concerned. I am in a bit of quagmire, I have inherited several applications that rely on one database and that database has one datacontext project which all these applications plug into. Currently we are using TFS and each of these .Net applications have a project reference to this data context project, which is fine if you do not need to branch out and if it is a single programmer outfit. Now I want to implement a better release strategy after a few D-Days and issues with half finished code (not caused by me). I want to go with the Gitflow strategy where I have three types of branches, a release (golden) branch, a trunk development branch and a day to day development branch. Now with several projects all tied together by a single datacontext project it is painful creating new branches, merging up, as it is huge and we lose track of changes. I agree there is very tight coupling and this needs to be reduced, I want to come up with a sane way of splitting the context and the applications into single entities. I agree what ever I do it will be time consuming but I would love a few opinions and experiences on people who have battled with this issue. Thanks for reading,
-
What is wrong with indian boyz?I think there are a lot of countries with the problem of gang rape and rape in general, Its just some rapes get publisised and others are just hidden away as if they never occurred. Rape in general is wrong and there should be tougher sentences to deter would be rapists!
-
I HATE INFRAGISTICS!!I feel your pain!!