pilotbob
| Forum | Thread | Replies | Latest activity |
|---|---|---|---|
| Coffeehouse | WinFS Beta 1 Released (video soon to come to Channel 9) | 29 | Aug 29, 2005 at 6:47 PM |
| Coffeehouse | Best video order missing? | 1 | Jan 15, 2005 at 9:24 AM |
| Forum | Thread | Replies | Latest activity |
|---|---|---|---|
| Coffeehouse | WinFS Beta 1 Released (video soon to come to Channel 9) | 29 | Aug 29, 2005 at 6:47 PM |
| Coffeehouse | Best video order missing? | 1 | Jan 15, 2005 at 9:24 AM |
Building Data-centric N-tier Applications with jQuery
Apr 15, 2011 at 10:38 AMCDC - Change Data Capture SQL Server 2008
Jan 04, 2008 at 7:19 PMWith triggers we would do this by getting the user_name from sql and we could insert it into the audit tables. This works well as long as you have a two tier application with each user having thier own connection.
With 3-Tier or web apps you are unable to use the user_name since you are probably using a single user id or connection pooling. So, what we would do is add a field or fields to each table that the application would populate on each insert/update. This way the audit data could capture who made the change. For delete I guess you would have to get creative like not allowing record deletes and just setting a delete flag... or you could update the record with all blank/null values prior to deleting it.
I would assume that you could do a similar thing with CDC?
BOb
LINQ to DataSet
Dec 12, 2007 at 8:34 AMBOb
Edit: Doh! I as able to download from the link in the description.
Refactoring in Visual Basic with Refactor!
Dec 12, 2007 at 6:59 AMSo, after you do a refactoring press the ESC key will bring you back to where you were.
BOb
(Member of the VFP Knitting Guild)
Pablo Castro, Britt Johnston, Michael Pizzo: ADO.NET Entity Framework - One Year Later
Oct 09, 2007 at 12:26 PMMS had a web cast on this... can't remember if it was on EntityFW or on LINQ to SQL... but the [main] differences as it explained them:
Linq to SQL
1. Only suports SQL Server
2. One to one mapping from Table to Object (although the Linq to SQL designer does seem to have inheritence stuff in it... so I'm not sure if this is 100% true.)
EnityFramework
1. Provider based data model to support multiple back ends.
2. An object (entity) can be mapped to multiple tables.
This tells me I need to be using the EntityFramework. Item 1 doesn't bother me since all of my projects are SQL server. But, I want to do DDD and it doesn't look like Linq to SQL is really designed for that.
So, I still don't understand why we (Microsoft) have both projects. I think the Linq to SQL should be dropped and all resources should be invested in the EntityFramework. It has better design goals and is a superset of Linq to SQL.
BOb
Pablo Castro, Britt Johnston, Michael Pizzo: ADO.NET Entity Framework - One Year Later
Sep 01, 2007 at 9:15 AMExcellent question. It seems like MS has been trying to give us an O/R Mapping type product/services since the Object Spaces annoucment. Since then it has been false start after false start. I remember that Italian guy doing a C9 demo on Object Spaces years ago... where did he go?
Now, it seems like you have two competing technologies that actually might ship.
Do these two teams know about each other? Why not merge the projects and come up with a single, consistent set of libraries to solve the problem of moving data from relational to object model.
Also, is there an Object first design paradim that you can do. I understand why all of these demos reverse engineer a db... but, can I create an object model first and then have in create my schema for me?
The LINQ to SQL objects also have partial method hooks that allow you to add business rules/validations to them. Is there anything like that in the Entities? Are the entities designed to also be the DTO's or are the entities just a way to tell link how to shape the objects that are returned from queries.
Confused,
BOb
Open XML SDK CTP Released - What is it?
Jun 08, 2007 at 2:36 PMBOb
Meet the Project Jasper Team
May 09, 2007 at 9:02 PMMixin' it up with Beth and Ray: MIX07 Under the Hood
Mar 31, 2007 at 7:25 PMWhat about the Heineken? MS must be more of a cool place to work than I thought originally.
BOb
: Continuous Integration with Team Build “Orcas”
Mar 18, 2007 at 8:54 AMLooks great... a few questions...
1. It looks like the build agent is actually a dummy/slave machine and it is actually the TFS that monitors checkins and when a build is needed it tells a build agent to run that build. Is this the case? If so, can you have a pool of build agents rather than specifiying a specific agent for a specific build?
2. The build status UI looked like it was passive... in other words you actually had to decide to look at the build status screen to see if one failed or whatever. Is there any type of notifications that just pop-up if a build fails... sort of like cctray? CCtray makes things so easy... you can basically ignore it but a quick glance without opening any UI dialog and you can tell the status via the Green-Yellow-Red indications.
3. Is there any labeling in source control that corresponds to a build? This could perhaps be used because a build is compiled as Debug for testing but then when we decide to release the build we want to actually rebuild from the same source to create a release/install package. Or, is this just part of the build project file itself? (Sorry we have worked with TFS build at all yet.)
4. How easy is it to add additional build steps like perhaps running FxCop or Simian or Fitnesse tests? Can the reports from those third party tools be integrated into the data warehouse?
Thanks.
BOb
See more comments…